Skip to main content
API keys authenticate requests from your applications and services. Each key is scoped to your organization — all API calls made with a key create and access resources within that organization.
MethodEndpointQuick Link
POST/user/api-keysCreate an API key
GET/user/api-keysList API keys
DELETE/user/api-keys/{api_key_id}Archive an API key
PUT/user/api-keys/{api_key_id}/reactivateReactivate an API key

​
Best practices

  • Use one key per environment — separate keys for development, staging, and production make rotation easy and limit blast radius if a key is compromised.
  • Use one key per service — this allows you to revoke a single service’s access without affecting others.
  • Rotate keys regularly — create a new key, update your secret store, then archive the old key.
  • Never hardcode keys — use environment variables or a secrets manager. Never commit keys to version control.
  • Monitor last_used_at — keys with no recent activity may be safe to archive.