Click Create new key, name it, choose an expiration, then click Create key
Copy the key value — you’ll need it for API requests
Your API key is shown only once. Store it in a secure secret manager (e.g. 1Password, AWS Secrets Manager, Vercel/GitHub environment variables) immediately after creation.
Never commit keys to source control or share them in plaintext (Slack, email, screenshots).
Treat the key like a password — anyone with it can call the API and incur usage on your organization.
If a key is lost or leaked, revoke it from the API Keys page and create a new one.
Every key requires an expiration setting at creation time. Choose one of:
Option
Behavior
Never
The key stays active until you manually revoke it.
Duration
The key expires automatically after the specified time. Maximum 730 days (2 years), in days or months.
Expired keys stop authenticating immediately and return 401 Unauthorized. Rotate before expiry to avoid downtime — create a new key, update your secret manager, then revoke the old one.
Short-lived keys reduce blast radius if a key is leaked. Pick the shortest duration that fits your rotation schedule.
