Document360 API Authentication

How to authenticate Document360 API requests: one Bearer API key plus a connectionId. MindCloud stores your API key securely — set it once, never resend it.

Every Document360 API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Document360 account. This page covers both, plus exactly how to send them, so you do not need to visit any other page to get authenticated.

Steps to authenticate

Create a MindCloud account at app.mindcloud.co if you do not already have one.
Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
Create a Document360 connection in Connections. Document360 uses an API key. You generate the key in your Document360 account, then paste it in when you create the connection — MindCloud stores it securely and never returns it in a response.
Copy the connection’s connectionId — you will send it on every request alongside your MindCloud API Key.

How requests are authenticated

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Document360 account that should run the action. MindCloud stores and refreshes the Document360 credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions.

For example, calling List Project Versions with an Document360 connection looks like this:

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/document360/actions/list-project-versions/run" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "arguments": {}
}'

The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which Document360 account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect Document360 with an API token

You need a Document360 account with permission to create API tokens for the knowledge base.

Open the API tokens page
In Document360, go to Settings > Knowledge base portal > API tokens.
Settings → Knowledge base portal → API tokens
Create a new API token
Click Create API token, enter a name, choose the permission level or allowed methods your workflow needs, and create the token.
Copy the token into MindCloud
Copy the token value and paste it into your Document360 connection in MindCloud as the API key.

Keep your key safe

Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs. Anyone with the key can call the Universal API as your MindCloud account, across every connection you have created.