Skip to main content
An API token is the credential to use for anything unattended: CI, a deploy script, a cron job. It starts with ipk_, doesn’t expire unless you give it an expiry, and is bound to the team that was active when you created it - so it keeps acting on the same team no matter what you switch to later. Send it as a bearer token:
The CLI takes one too - see Authentication.

List Tokens

Response: 200 OK
Metadata only. The token value itself is stored hashed and is never returned again after creation, so there is no endpoint that can show it to you. prefix is the first 12 characters, which is how you match a row in this list against a token you have somewhere. last_used_at is the cheapest way to find a token nothing uses any more.

Create a Token

Response: 201 Created
token appears in this response and nowhere else, ever. Copy it now. If you lose it, revoke the token and create another - there is no way to recover the value.
A connector session cannot mint an API token. The OAuth exchange issues a full-power 30-day session, so allowing it would let a stolen connector token be traded for a credential that outlives revoking the session. No MCP client needs to create one. Sign in to the dashboard, or use the CLI (instapods login), which is unaffected.

Revoke a Token

Response: 200 OK
Effective immediately: the next request using that token gets a 401. You can only revoke your own tokens (403 otherwise). Revoking an API token does not touch your browser or CLI sessions - those are separate, and are listed and revoked from Account Settings.