Minting a key
API keys are created from the app, in Team settings, and only from a signed-in browser session. A key cannot mint another key. The token is shown once, at creation. It is stored as a SHA-256 hash, so nobody, including us, can recover it later. Lose it and you revoke it and mint a new one. Keys can be given an expiry, and can be revoked at any time.Sending it
An HTTP Bearer token on theAuthorization header:
tst_live_. There is no custom header. The
Authorization header is the only one read, and it accepts either an API key
or a browser session token.
In CI
Store the key as a secret and pass it through the environment. Never commit it.What a key can reach
A key is bound to one person and one workspace, and inherits that person’s role there.Checking a key
200 tells you who the key belongs to and which workspace it is pinned to.
401 means the key is wrong, revoked, expired, or its owner has left.
Good hygiene
- One key per pipeline, so revoking one does not break the others.
- Set an expiry on anything short-lived.
- Revoke rather than rotating in place, because revocation is immediate.
- Never put a key in a base URL, a query string or a log line.

