Docs

Cryptlex API Authentication

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

Every Cryptlex API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Cryptlex 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 Cryptlex connection in Connections. Cryptlex uses an API key. You generate the key in your Cryptlex account, then paste it in when you create the connection — MindCloud stores it securely and never returns it in a response.
  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 Cryptlex account that should run the action. MindCloud stores and refreshes the Cryptlex 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 Products with an Cryptlex connection looks like this:

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

Set up a Cryptlex personal access token

You need access to the Cryptlex admin portal and permission to create developer access tokens with the scopes your automation needs.

  1. Open the Cryptlex admin portal

    Sign in to your Cryptlex account and open the admin portal for the account you want this connection to use.

    Cryptlex Admin Portal
  2. Create a personal access token

    Go to Developer -> Access Tokens, click Create, name the token, and set an expiration if you want one.

    Cryptlex Docs → Web Integrations → Personal Access Tokens
  3. Assign the right scopes

    Grant read or write access for the Cryptlex modules this app will call, such as Licenses, Products, Activations, Releases, Users, and Webhooks.

  4. Copy the token into this connection

    Copy the token when Cryptlex shows it and paste it into this app connection as the API key credential. Cryptlex only shows the full token once.

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.