Docs

Deputy API Authentication

How to authenticate Deputy API requests: one Bearer API key plus a connectionId. MindCloud runs the OAuth flow and refreshes Deputy tokens for you.

Every Deputy API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Deputy 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

  1. Create a MindCloud account at app.mindcloud.co if you do not already have one.
  2. Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
  3. Create a Deputy connection in Connections. Deputy uses OAuth. When you create the connection, you are redirected to sign in to Deputy and approve access — MindCloud stores the resulting tokens and refreshes them automatically, so your integration never has to.
  4. 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 Deputy account that should run the action. MindCloud stores and refreshes the Deputy 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 Employees with an Deputy connection looks like this:

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

Connect Deputy with OAuth 2.0

You need a Deputy OAuth app, its client ID and client secret, and your Deputy endpoint prefix. Enter only the part before .deputy.com, for example acme or 93929518050048.na.

  1. Register a Deputy OAuth app

    In Deputy's developer setup, create or open an OAuth 2.0 app and keep the client ID and client secret ready for MindCloud.

  2. Find your Deputy endpoint prefix

    Use only the part before .deputy.com when MindCloud asks for the endpoint. For example, if your Deputy URL is https://93929518050048.na.deputy.com, enter 93929518050048.na.

  3. Finish the OAuth approval

    After you enter your client credentials and endpoint prefix in MindCloud, continue the OAuth flow and approve access in Deputy.

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.