Where keys live
Admins on a paid plan manage keys in Settings → Integrations → API keys. The full key appears once at creation.Create a key
Choose a name, access, permissions and expiry. All resources covers the organization. Selected resources can mix chat agents, voice agents, campaigns and knowledge bases. Choose permissions that apply to your selection. Expiry can be Never, 30 days, 90 days, 1 year or a date.Permissions
Included permissions are granted automatically. Organization-wide permissions require All resources access.
The catalogue describes access. It does not promise an HTTP endpoint for every permission. Each operation names its required permission.
Send the key
Use the Authorization header. Keep the key on your server.Roll a key
Select Roll key, then In 24 hours or Now. Copy the replacement key once and update your integrations. In 24 hours keeps the old key valid during the overlap. Now stops it immediately.Revoke a key
Select Revoke to stop access immediately. Replace it in your integrations before revoking if you need uninterrupted access.Expiry and removal
Revoked and expired keys remain listed for 30 days, then are removed. Requests using a removed key fail with invalid_key.Keys and regions
Each key works at its organization’s base URL. When the organization moves region, its keys move with it. MCP sign-ins do not move. Members must sign in again after a region move. Every request goes to the base URL for your organization’s region. Each key works at its organization’s base URL. When the organization moves region, its keys move with it. Pick the matching row.| Region | Base URL |
|---|