About Aircall
Aircall is a cloud-based business phone system and call-center platform. The Aircall source pulls call, user, and team activity into Iru so you can attach evidence to compliance frameworks. Authentication uses HTTP Basic against the Aircall Public API (api_id as username, api_token as password).
How It Works
Iru calls the Aircall Public API over HTTPS using HTTP Basic:api_id as the username and api_token as the password (see Basic authentication).
| Detail | Value |
|---|---|
| Category | Communications |
| Authentication | HTTP Basic (Username = api_id, Password = api_token) |
| Vendor plan | Any paid Aircall plan (API access included) |
Prerequisites
- Admin or Owner on the Aircall account (standard users cannot create API keys).
- About 5 minutes for setup.
- HTTPS for Aircall API traffic.
- Browser pop-ups allowed so the connector wizard can open.
Connect Aircall to Iru
- Aircall
- Iru Compliance
Complete this tab before you connect the source in Compliance.
Sign in to Aircall
Open the Aircall Dashboard and sign in with an account that has Admin or Owner rights (only those roles can create API keys).
Open Integrations & API
In the left sidebar, select Integrations & API (wording may vary slightly by Aircall UI version).
Go to API keys
Open the Aircall API section or the API Keys tab, depending on how your workspace labels it.
Create a new API key
Choose Add a new API Key or Generate an API Key. Enter a clear name (for example Iru Compliance) and confirm so Aircall creates the key pair.
Copy api_id and api_token
Aircall shows
api_id and api_token together. Copy both to a secure place: you will use api_id as the Username and api_token as the Password in Iru’s Basic Authentication step.api_token appears only once. If you lose it, delete this key in Aircall and create a new one, then update Iru with the new values.Continue on the Iru Compliance tab.
Considerations
- Account-wide keys: API keys apply to the account, not a single user. The integration can keep working if the person who created the key leaves, unless your team rotates or deletes the key in Aircall.
- Rate limits: Aircall’s Public API default is 60 requests per minute. Iru applies backoff when limits are hit. Unusually frequent manual evidence refreshes could still trigger 429 responses. See troubleshooting.
- Access mode: Iru uses this connection for read-oriented compliance evidence. The
api_tokenstill grants the access level Aircall assigns to that key. Store and rotate it like a secret.
Troubleshooting
Nothing opens when you turn the source on
Nothing opens when you turn the source on
Check pop-up blocker settings for the Iru site and try again.
401 Unauthorized
401 Unauthorized
429 Too Many Requests
429 Too Many Requests
You hit Aircall’s rate limit (60 requests per minute by default). Iru backs off automatically. If 429 persists, contact Aircall support about a higher limit.
“You don’t have permission” when creating the API key
“You don’t have permission” when creating the API key
Only Admin or Owner can create keys. Ask an Aircall administrator to create the key, or have your role updated.
Related Articles
Sources Management
Browse and manage every Compliance source.
Getting Started With Compliance
Frameworks, actions, and Artifacts.
Iru Overview
How Endpoint, Compliance, and Identity fit together.
Artifacts Management
Upload, review, and organize evidence from sources and actions.