Reach360 API Authentication

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

Every Reach360 API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Reach360 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 Reach360 connection in Connections. Reach360 uses an API key. You generate the key in your Reach360 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 Reach360 account that should run the action. MindCloud stores and refreshes the Reach360 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 Users with an Reach360 connection looks like this:

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/reach360/actions/list-users/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 Reach360 account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect Reach360 with an API key

You must be a Reach 360 admin. Generate a dedicated key for each integration and copy it immediately because Reach 360 shows the key only once.

Open Reach 360 settings
In Reach 360, go to Manage > Settings.
Manage → Settings
Open API key management
Click Manage API Keys.
Generate a new API key
Click Generate New Key, enter a recognizable name such as MindCloud Reach360, and click Generate Key.
Copy and save the key securely
Copy the generated API key immediately and store it in a secure password manager or secret store. If you leave the page before copying it, you must revoke the key and generate a new one.
Paste the key into MindCloud
Use the saved value as the Reach360 API Key credential in MindCloud.

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.