Skip to main content
All API requests require an API key passed in the Authorization header.

Header format

You can also send the raw key on its own, with no prefix:
Do not send an API key as Bearer <your-key>. Allo reads a Bearer value as a user session token, not as an API key, so the request returns 401. Use Api-Key <your-key> or the raw key.

Generating API keys

  1. Go to Allo Settings > API
  2. Click Create API Key
  3. Select the scopes your integration needs
  4. Copy the key. It won’t be shown again

API key scopes

Each API key has specific scopes that determine what operations it can perform. GET /v2/api/me requires no scope. Any valid key can call it, and its endpoints array is the authoritative list of what your key can reach.

Scope-to-endpoint mapping

Every documented endpoint and the scope it needs. If a call returns 403 with code API_KEY_INSUFFICIENT_SCOPE, the key is valid but missing the scope listed here. Discovery Conversations CRM Threads Inboxes SMS Phone numbers and call flows AI receptionist Summary templates Tags Users Webhooks Analytics Dialing queues Partner

Example request

Error responses

Invalid or missing key (401)
Insufficient scope (403)

Security

  • API keys are scoped to a single team
  • Keys can be revoked at any time from settings
  • Never expose keys in client-side code or public repositories
  • Use environment variables to store keys in your application