Creating API keys
How team admins create, scope, and rotate API keys for programmatic access.
Team owners and admins can create API keys from Team → Settings → API keys.
Before you create a key
- Decide which endpoints your integration needs — each route requires specific API key scopes.
- Prefer the minimum scopes required. You can always create a new key with broader access later. Public API routes are scoped to the team that owns the key.
Create the key
- Open Team → Settings → API keys.
- Choose Create key.
- Name the key for the integration (for example
CI deployorBilling sync). - Select the scopes your app needs.
- Copy the secret immediately — it is shown only once.
Keys use the gsk_live_ prefix in production. Send them as Authorization: Bearer … or X-API-Key: … on every request.
Rotate or revoke
If a secret is exposed, revoke the key from Team settings and issue a replacement. Update your integration before deleting the old key to avoid downtime.
For scope details and team role permissions, see the Knowledge base.