TMetric API Authentication

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

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

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

Set up your TMetric API token

You need access to the TMetric workspace and profile that should power this connection.

Open your TMetric profile settings
Sign in to TMetric and open Profile Settings for the account that owns the API token.
Generate or copy your API token
Use Get new API token in TMetric Profile Settings. TMetric warns that generating a new token invalidates the previous one, so reuse the existing token when possible.
Paste the token into MindCloud
Paste the TMetric API token into this connection's 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.