Attio API Authentication
How to authenticate Attio API requests: one Bearer API key plus a connectionId. MindCloud runs the OAuth flow and refreshes Attio tokens for you.
Every Attio API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Attio 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 Attio connection in Connections. Attio uses OAuth. When you create the connection, you are redirected to sign in to Attio and approve access — MindCloud stores the resulting tokens and refreshes them automatically, so your integration never has to.
- 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 Attio account that should run the action. MindCloud stores and refreshes the Attio 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 Objects with an Attio connection looks like this:
curl --request POST \
--url "https://connect.mindcloud.co/v2/universal/apps/attio/actions/list-objects/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 Attio account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.
Set up Attio OAuth
You need access to Attio's developer dashboard for the workspace that owns this OAuth app.
- Open the Attio developer dashboard
Go to Attio's developer dashboard to manage the OAuth app used by MindCloud.
Developer dashboard - Create or open your Attio app
Create a new app if one does not exist yet, or open the existing app you want MindCloud to use for OAuth.
- Enable OAuth 2.0
Open the OAuth tab in the app's settings and turn on OAuth 2.0.
- Add MindCloud's redirect URL
Add this redirect URL to the app's allowed redirect URIs.
- Enable the required scopes
Open the Scopes tab and enable the Attio scopes required by MindCloud for records, object configuration, lists, comments, notes, tasks, meetings, call recordings, webhooks, files, and workspace members.
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.