Aircall

DSALTA connects to Aircall using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules.

Read-only access. DSALTA never modifies, creates, or deletes resources in your Aircall account. DSALTA only reads your user roster.

DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

What DSALTA reads

DSALTA reads the Aircall user roster — names, email addresses and creation dates, which appears on your Access page. Aircall’s user API exposes no role or account status, so every member is listed as an active Member.It calls these Aircall endpoints:

/v1/users
/v1/company

Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Aircall environment.

Troubleshooting

Integration shows Disconnected

There is no Reconnect button. Open Integrations → Connected, click Manage on the Aircall card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Aircall. This can happen if the API key was revoked or regenerated in Aircall (Integrations & API → API Keys).

Data is not syncing

Confirm the API ID and API Token are current and the key was generated by an admin, then click Sync from integrations on the Integrations page (Connected tab) — it refreshes every connected integration at once. If the key was regenerated, reconnect with the new credentials.

1

Start in DSALTA

Open Integrations in the DSALTA sidebar, find Aircall, and click Connect to open the connect panel.

2

Open Aircall API Keys

Sign in to Aircall as an admin, open Integrations in the left sidebar, then open API Keys — Aircall now surfaces it as a button at the top right of the Integrations & API page rather than as a tab.

Aircall's API Keys page with the Generate API key button at the top right

3

Generate an API key

Generate a new API key. A modal shows your API ID and API Token — copy and store both now; the token is shown only once and cannot be retrieved after you close the modal.

Treat the API Token like a password. Aircall API keys carry no scopes — the pair grants full access to your Aircall account, so anyone holding it can make requests on your behalf. If a key leaks, revoke it from Integrations & API → API Keys and connect again with a fresh pair.

Aircall's Generate API Key dialog showing the key name, API ID and API Token with a copy button

4

Connect

Continue, then paste the API ID (username) and API Token (password) in the next step to complete the connection. DSALTA only reads your user roster.

DSALTA's Link Aircall account panel with API ID and API Token fields

Once connected, Aircall appears on the Connected tab and the checks below begin reporting after the first sync.

Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.

Check	Severity	What it verifies
User access to Critical System should be valid	Info	Checks that everyone with Aircall access is an active employee on the People page.
Offboarded users should not have active access	High	Checks that offboarded employees no longer have active Aircall access.

Topic	Link
Setup	Getting your Aircall API key
Setup	Aircall Public API reference
General	Aircall website
DSALTA	Connection error messages

Getting Connected

Identity Providers

Cloud Infrastructure

Code Repositories

Security & Monitoring

Databases

SaaS & Productivity

What DSALTA reads

Troubleshooting

​What DSALTA reads

​Troubleshooting

What DSALTA reads

Troubleshooting