respond.io API Authentication

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

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

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

Connect respond.io API token

You need a respond.io workspace and permission to create an Access Token.

Create an API Access Token in respond.io
In respond.io, open Settings and generate an Access Token for API access.
Paste the token in MindCloud
In the MindCloud connection form, paste the token into the API Key field and save the connection.
Test the connection
Run a test request with the List Users action to verify the token works.

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.