API tokens
An API token is what an automation platform or a script presents to Kadmo's API. Every member creates their own, in Settings → Assistant → API tokens. A token acts as the member who created it, with their role, on their account. It works only for the API.
| Looks like | kadmo_api_ followed by a secret |
| Who can create one | Every member, admin or not |
| Shown | Once, when it is created |
| Lifetime | Until it is revoked |
| How many | Up to 50 live API tokens per member, counted apart from their MCP and Kadmo Git tokens |
| Opens | The API at https://app.kadmo.ai/api/v1, and nothing else |
An API token is not a personal MCP token. A personal MCP token (kadmo_pat_) connects an MCP client and is refused by the API. An API token is refused by the MCP server.
Create a token
- Go to Settings → Assistant and scroll to API tokens, under the Connect an MCP client card.
- Enter a Token name: the platform or script it is for, such as
n8n, up to 80 characters. - Press Create token.
- Press Copy. Copy the token now — it is not shown again. Kadmo keeps only a fingerprint of it, so it cannot show you the token later.
- Paste it where the platform keeps credentials, or put it in an environment variable for a script. Never put it in a page that a browser loads.
Check it with the call the card shows:
curl https://app.kadmo.ai/api/v1/me \
-H "Authorization: Bearer $KADMO_API_TOKEN"A 200 names you, your account, your role and the token's name. A 401 means the token was not sent whole: see Troubleshooting.
Your tokens
Your tokens lists your live API tokens, newest first: each one's name, its first characters, when it was created and when it was last used (never used until its first call). The last use is updated at most once a minute.
Revoke a token
Press Revoke next to the token. Its next call is refused with 401. A platform that used it needs a new token. The webhook subscriptions the token made are yours, not the token's, and stay: delete them on the Integrations page if the platform is gone.
An admin also sees Members' tokens: every other member's live API token, with its owner. An admin can revoke any of them there; only the member who created a token can see its secret, and only once.
A member's API tokens are also revoked when the member is removed from the account (Change a role or remove a member). When the trial has ended, a member can still revoke a token but cannot create one (The trial).
Keep it safe
- Create one token per platform or script, named after it, so that revoking one stops only that one.
- A token acts as you: the jobs, tasks and runs it starts show in the app as yours, and a run's activity names the token (via API token n8n).
- If a token may have leaked, revoke it, then create a new one.