> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iru.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Aircall

> Connect Aircall to Iru Compliance with HTTP Basic auth (api_id and api_token) to collect call activity, user, and team membership evidence.

### 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](https://developer.aircall.io/tutorials/basic-authentication)).

| Detail             | Value                                                            |
| ------------------ | ---------------------------------------------------------------- |
| **Category**       | Communications                                                   |
| **Authentication** | HTTP Basic (**Username** = `api_id`, **Password** = `api_token`) |
| **Vendor plan**    | Any **paid** Aircall plan (API access included)                  |

Official references: [Basic authentication](https://developer.aircall.io/tutorials/basic-authentication), [API references](https://developer.aircall.io/api-references/).

### 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

<Tabs>
  <Tab title="Aircall">
    <Note>
      Complete this tab before you connect the source in Compliance.
    </Note>

    <Steps>
      <Step title="Sign in to Aircall">
        Open the [Aircall Dashboard](https://dashboard.aircall.io) and sign in with an account that has **Admin** or **Owner** rights (only those roles can create API keys).
      </Step>

      <Step title="Open Integrations & API">
        In the left sidebar, select **Integrations & API** (wording may vary slightly by Aircall UI version).
      </Step>

      <Step title="Go to API keys">
        Open the **Aircall API** section or the **API Keys** tab, depending on how your workspace labels it.
      </Step>

      <Step title="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.
      </Step>

      <Step title="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.
      </Step>
    </Steps>

    <Note>
      Continue on the [**Iru Compliance**](#iru-compliance) tab.
    </Note>
  </Tab>

  <Tab title="Iru Compliance">
    <Note>
      Finish the [**Aircall**](#aircall) tab first.
    </Note>

    <Steps>
      <Step title="Open Sources">
        In Iru Compliance, on the left navigation bar, expand **Compliance** and select **Sources**.

        <Frame>
          <img src="https://mintcdn.com/iru/7HsGH7lnQ8GpVmI0/assets/media/images/iru-navigation-compliance-sources.png?fit=max&auto=format&n=7HsGH7lnQ8GpVmI0&q=85&s=595982441fd777b333b3ecfea24adc24" alt="Left navigation: Compliance expanded, Sources selected" width="424" height="1056" data-path="assets/media/images/iru-navigation-compliance-sources.png" />
        </Frame>
      </Step>

      <Step title="Turn on Aircall">
        Find **Aircall** (set **Category** to **Communications** or use **Search by name or description**). On the **Aircall** card, turn on the **toggle**. A **new browser tab** may open for the wizard.
      </Step>

      <Step title="Enter Basic authentication">
        On **Enter Basic Authentication**, put **`api_id`** in **Username** and **`api_token`** in **Password**.
      </Step>

      <Step title="Finish the connection">
        Click **Submit Credentials**. When the connection succeeds, the wizard shows **Connection Configured**.
      </Step>

      <Step title="Confirm the source is Active">
        Close the **Iru is requesting access to external services** browser tab, then return to **Compliance** → **Sources** and confirm the **Aircall** card is **Active**.
      </Step>
    </Steps>
  </Tab>
</Tabs>

### 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_token`** still grants the access level Aircall assigns to that key. **Store and rotate it like a secret**.

### Troubleshooting

<AccordionGroup>
  <Accordion title="Nothing opens when you turn the source on">
    Check **pop-up blocker** settings for the Iru site and try again.
  </Accordion>

  <Accordion title="401 Unauthorized">
    The **`api_token`** may be wrong, or the key was **deleted** in Aircall. Create a new API key in Aircall and submit the new **`api_id`** / **`api_token`** in Iru.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="“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.
  </Accordion>
</AccordionGroup>

### Related Articles

<CardGroup cols={2}>
  <Card title="Sources Management" icon="plug" href="/en/compliance/sources-management">
    Browse and manage every Compliance source.
  </Card>

  <Card title="Getting Started With Compliance" icon="rocket" href="/en/compliance/getting-started-with-compliance">
    Frameworks, actions, and **Artifacts**.
  </Card>

  <Card title="Iru Overview" icon="layer-group" href="/en/iru/platform-overview/iru-overview">
    How Endpoint, Compliance, and Identity fit together.
  </Card>

  <Card title="Artifacts Management" icon="folder-open" href="/en/compliance/artifacts-management">
    Upload, review, and organize evidence from sources and actions.
  </Card>
</CardGroup>