> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/sales/aircall/faq.md).

# FAQ

<details>

<summary>Where do I find my Aircall API credentials?</summary>

Log in to your Aircall Dashboard and go to **Integrations > API Keys**. You'll see your **API ID** and **API Token** listed there. You need Admin access to view this section — if you don't see it, ask your account admin.

</details>

<details>

<summary>What's the difference between the API ID and the API Token?</summary>

The **API ID** acts like a username and identifies your account. The **API Token** acts like a password and authenticates your requests. Coupler.io needs both to connect — entering only one will result in an authentication error.

</details>

<details>

<summary>Can I connect multiple Aircall accounts?</summary>

Yes. You can create separate importers in Coupler.io, each using a different set of API credentials. This is useful if your organization manages more than one Aircall account.

</details>

<details>

<summary>How far back can I pull historical call data?</summary>

Aircall's API supports historical data retrieval, and the range depends on your Aircall plan. Use the date picker in Coupler.io to set your start date. For very long date ranges, expect the initial import to take more time.

</details>

<details>

<summary>Why does the User availabilities entity not show historical data?</summary>

The User availabilities entity reflects the most recent availability status for each agent, not a full history of status changes. If you need to track availability over time, consider scheduling frequent imports and appending data to your destination rather than replacing it.

</details>

<details>

<summary>Can I get call recordings through Coupler.io?</summary>

Call recording URLs are included in the Calls entity as a field, provided recording is enabled on your Aircall plan and configured for your numbers. Coupler.io exports the URL — you access the actual recording file directly from Aircall's storage.

</details>

<details>

<summary>Does Coupler.io support real-time Aircall data?</summary>

Coupler.io works on a scheduled refresh model, not true real-time streaming. You can set refresh intervals as short as every 15 minutes, depending on your plan. For live call monitoring, use Aircall's native dashboard.

</details>

<details>

<summary>What happens if my API key expires or is regenerated?</summary>

Your scheduled data flows will fail with an authentication error. Go to your Coupler.io Sources, update the API credentials with the new values, and re-run the data flow to resume normal operation.

</details>

{% hint style="info" %}
For details on available fields and metrics, see [Data Overview](/sources/category/sales/aircall/data-overview.md). If you're running into connection or data problems, check [Common Issues](/sources/category/sales/aircall/common-issues.md). For tips on structuring your imports, visit [Best Practices](/sources/category/sales/aircall/best-practices.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/sales/aircall/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.