Docs

Kommo API Authentication

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

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

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

Connect a Kommo public integration

You need a Kommo technical account and a public integration before you connect this app.

  1. Create or confirm a Kommo technical account

    Public integrations require a Kommo technical account. If you do not already have one, contact Kommo support and request the technical-account flow.

    Technical account
  2. Create a public integration

    In the technical account, create a Public integration and complete the required review metadata for the app.

    Create a Public integration
  3. Set the redirect URI and copy the keys

    Open the Keys and Scopes tab, set the Redirect URI to MindCloud, then copy the Integration ID and Secret key into this connection.

    OAuth 2.0
  4. Enter the customer subdomain

    Use the customer account subdomain from the Kommo URL, for example acme from https://acme.kommo.com. MindCloud uses it for the OAuth token endpoint and API base URL.

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.