Userback API Authentication

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

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

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

Connect your Userback workspace

You need a Userback workspace with REST API access enabled. Userback documents REST API access on Business Plus or via an approved partner code.

Sign in to Userback
Open your Userback workspace and sign in with the account that can manage workspace settings.
Userback App
Open the API Token settings
Go to Workspace Settings, then open the API Token section.
Workspace Settings → API Token
Create an API token
Click Create API Token, give it a memorable name, and copy the token value when Userback shows it.
Paste the token into the MindCloud connection
In the MindCloud connection form for Userback, paste the copied token into the API Key field.

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.