1Shot API Authentication

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

Every 1Shot API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your 1Shot 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 1Shot connection in Connections. 1Shot uses OAuth. When you create the connection, you are redirected to sign in to 1Shot 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 1Shot account that should run the action. MindCloud stores and refreshes the 1Shot 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 Chains with an 1Shot connection looks like this:

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

Connect 1Shot API

You need a 1Shot API account and a business in the 1Shot console.

Sign in to the 1Shot API console
Open the 1Shot API console and sign in or create a free account.
Create a business if this is your first sign-in
The official onboarding docs say you will be prompted to create a business on your first sign-in. Complete that setup before creating API credentials.
Create an API key
In the 1Shot API console, click the "API Keys" tab in the left-hand navigation, click "Create New Key", and give it a name.
Copy the client credentials into this connection
Use the new API key value as the Client ID and the new secret value as the Client Secret in the MindCloud connection form.

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.