Cloud 66 API Authentication
How to authenticate Cloud 66 API requests: one Bearer API key plus a connectionId. MindCloud stores your API key securely — set it once, never resend it.
Every Cloud 66 API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Cloud 66 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 Cloud 66 connection in Connections. Cloud 66 uses an API key. You generate the key in your Cloud 66 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 Cloud 66 account that should run the action. MindCloud stores and refreshes the Cloud 66 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 Get Authenticated User with an Cloud 66 connection looks like this:
curl --request POST \
--url "https://connect.mindcloud.co/v2/universal/apps/cloud66/actions/get-authenticated-user/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 Cloud 66 account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.
Connect your Cloud 66 account
You need access to the Cloud 66 account you want to connect and permission to create or view API access tokens in the account Apps area.
- Open the Apps area under your Cloud 66 account
Sign in to Cloud 66 and open the Apps section under your account. The official Cloud 66 authentication docs say this is where you generate an OAuth token for API access.
- Copy a valid OAuth access token
Generate or copy the Cloud 66 OAuth access token you want MindCloud to use for API calls.
- Paste the token into the MindCloud connection
Open the Cloud 66 connection in MindCloud and paste the OAuth access token into the API Key field. MindCloud sends this value as a bearer token.
- Save and retest Get Authenticated User
Save the connection, then run Get Authenticated User again. A valid token should return the current user and account details.
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.