Twenty API Authentication

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

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

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

Create a Twenty API key

You need access to your Twenty workspace settings. If your workspace uses roles, make sure the API key is assigned to a role that can read or modify the objects you plan to use.

Open APIs & Webhooks
In Twenty, go to Settings -> APIs & Webhooks.
Settings → APIs & Webhooks
Create the key
Click + Create key. Enter a descriptive name and choose an expiration date if needed, then save.
Copy the API key
Copy the API key immediately and store it somewhere safe. Twenty only shows the full key once.
Assign the key to a role if needed
If your workspace uses role-based permissions, go to Settings -> Roles, open the target role, open the Assignment tab, click + Assign to API key under API Keys, and select the new key.
Settings → Roles → Assignment
Paste the key into MindCloud
In MindCloud, create or edit the Twenty connection and paste the copied API key into the 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.