Safeguard Docs
Compliance ConnectorsSetup by categoryCommunications Platforms

Aircall

Connect Aircall to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Connect Aircall to collect communications platforms evidence with automated compliance tests, switched on per workspace.

CategoryCommunications Platforms
Connect withAPI token
What a connection producesAutomated compliance tests
Aircall's guidedevelopers.aircall.io

Connect with an API token

  1. In Aircall:

    1. Sign in to the Aircall Dashboard as an Admin and open your Company's Settings page (dashboard.aircall.io/company).
    2. Find the API Keys section.
    3. Click Add a new API key.
    4. Copy the api_id and the api_token right away; Aircall does not store the token in plain text and cannot show it again.

    Where to find the other values:

    • API ID: Shown as the api_id next to the new key in the API Keys section of the Company Settings page.
    • API token: Shown as the api_token once, when you click Add a new API key.

    Aircall shows the secret only once, so copy it before you leave the page.

    Only Admins can manage API keys. Aircall API keys have no read-only scope; the key has full company access. The API ID and token are used as HTTP Basic credentials (ID as username, token as password). The optional Access token field is an OAuth token from an Aircall technology-partner app; its issuance was not documented here.

    Source: developers.aircall.io, checked 2026-10-07.

    The permissions Safeguard needs. Aircall issues no read-only credential. Safeguard only reads with it, and you can revoke it at any time.

  2. On Compliance › Connectors, open Aircall, click Connect, choose API token and fill in:

    FieldWhat to enter
    API IDOptional.
    API tokenOptional. Stored encrypted and never shown again.

    Or, instead: Access token (optional).

  3. Click Connect with token.

Frameworks

Safeguard's automated tests read Aircall and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

FrameworkEvidenceControlsTests
SOC2Automated testsCC6.2, CC6.32
ISO/IEC 27001Automated testsA.5.16, A.5.18, A.6.52
HIPAA Security RuleAutomated tests164.308(a)(3), 164.308(a)(4)2
PCI DSSAutomated tests7.2.4, 8.2.52
NIST CSF 2.0Automated testsPR.AA-01, PR.AA-052

These tests are switched on per workspace by the Safeguard team.

8x8

Connect 8x8 to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Dialpad

Connect Dialpad to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

On this page

Connect with an API tokenFrameworksRelated