Aircall
API keyCommunicationOrg connection
Org-level connection
Aircall is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
Getting your API key
In Aircall, go to Integrations & API → API Keys → Create an API Key. You'll get an API ID and API Token — enter both below.
Ready to connect?
Sign in to On Belay and open the Integrations page to add Aircall.
Permissions (scopes)
These are the data scopes On Belay can be granted for Aircall. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
calls:read | Read call logs | Read only |
calls:write | Tag and comment on calls | Read / Write |
contacts:read | Read contacts | Read only |
contacts:write | Create and update contacts | Read / Write |
contacts:delete | Delete contacts | Admin |
users:read | Read users/agents | Read only |
numbers:read | Read phone numbers | Read only |
teams:read | Read teams | Read only |
tags:read | Read call tags | Read only |
Troubleshooting
"Invalid API key" or "Unauthorized" error
Double-check that you copied the full key without any leading/trailing spaces. Some platforms show a truncated preview — make sure to copy the full token. If the key was generated with restricted scopes, verify it includes the permissions listed above.
Connected but Claude can't access data
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
The key expires or stops working
Some API keys have expiration policies. Generate a new key in Aircall and update it in On Belay → Integrations → Aircall → Update key. Consider creating a dedicated service account or machine user for On Belay so the key isn't tied to a personal account.
Still stuck? We're happy to help.
Contact support →