Sign inGet started
Docs
Get started

Qntrl API Authentication

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

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

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

Connect Qntrl with OAuth 2.0

You need a Zoho OAuth client registered for Qntrl and its redirect URL must exactly match MindCloud's callback URL.

  1. Confirm the authorized redirect URL

    In Zoho Developer Console, make sure the OAuth client uses this exact redirect URL: https://api.mindcloud.co/v1/oauth/qntrl/callback.

  2. Keep your Qntrl scopes ready

    Qntrl's API docs list the grantable scopes. This app requests broad documented Qntrl scopes so you can authenticate once and finish buildout.

  3. Authenticate the connection in MindCloud

    When you open the test connection, MindCloud will redirect you through Zoho OAuth and store the resulting Qntrl access token and refresh token.

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.