Joonto API Authentication

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

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

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

Connect your Joonto API token

You need an existing API token from your Joonto dashboard before this connection can run.

Open the API token page in Joonto
Sign in to your Joonto dashboard and go to Dashboard > Integrations > Market Place > API Tokens.
Copy an existing token or create a new one
Use the existing in-app API token when possible. Only create a new token if you do not already have one for this connection.
Paste the token into MindCloud
In the Joonto connection form, paste the token into the API Token field and save the connection.

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.