Skip to content

Authentication

Every API request is authenticated with an organization API key. Keys are created and managed by organization admins under Settings → API Keys in the Caller 9 studio.

Send the key as a Bearer token:

Authorization: Bearer c9_...

or in the X-Api-Key header:

X-Api-Key: c9_...

Keys always start with c9_. Always call the API over HTTPS.

Access level Can do
Read-only GET requests only. Any other method returns 403.
Full access Everything an organization admin can do through the API: create and change studios, numbers, contacts and automations, and control live calls.

Each endpoint in the API reference notes whether it needs a full-access key.

A key belongs to exactly one organization. Requests for another organization’s resources return 404, exactly as if they didn’t exist.

Some things are only available to signed-in people in the studio app, never to API keys. Keys get a 403 for:

  • viewing or managing members, invitations or API keys
  • viewing or editing organization details, and requesting new phone numbers (these are planned for API keys)
  • billing, checkout and plan changes
  • creating or deleting organizations
  • the live operator dashboard and browser phone, including sending a call to Browser (an API key has no operator behind it, so use an on-air line or hold instead)
  • Expiry: keys can be set to expire after 1 hour, 1 day, 7 days, 30 days, 90 days or 1 year, or never. Expired keys stop working and are removed.
  • Rotate: issues a new key with the same name, access level and lifetime. You choose when the old key stops working: immediately, or after 1 hour, 24 hours or 7 days. That gives you time to roll the new key out without downtime.
  • Revoke: the key stops working immediately. It stays in the list (marked Revoked, with who revoked it and when) until you delete it.

Each key shows when it was last used. That’s a quick way to find keys you no longer need.