Reference · built on requestConnectorVoice & contact center

Aircall

Calls, contacts, users, numbers, tags, and conversation intelligence from Aircall, with webhooks for every call event.

About

Aircall is a cloud phone system for sales and support teams. Its REST API at api.aircall.io/v1 covers Users, Teams, Calls, Numbers, Contacts, Messages, Webhooks, Outbound Campaigns, Conversation Intelligence, and Analytics. A private app authenticates with an API ID and API token from the Dashboard; a public app uses OAuth 2.0 and passes Aircall review before it reaches the App Marketplace.

Through Fibric, an operator watches call.ended, summary.created, and sentiment.created events, reads the call with its tags and comments, and proposes an outbound call, a tag, or a comment. You approve it, and the receipt records what changed and how to undo it.

This is a reference listing. It documents what Fibric would read from Aircall and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Calls through GET /v1/calls and Call Search, with id, direction, status, started_at, answered_at, ended_at, duration, user, contact, number, tags, and comments
  • Call events such as call.created, call.ringing_on_agent, call.answered, call.transferred, call.hungup, call.ended, call.voicemail_left, and call.comm_assets_generated
  • Conversation Intelligence events transcription.created, summary.created, sentiment.created, topics.created, and action_item.created, with a retrieval endpoint for each
  • User availability through GET /v1/users/:id/availability and user.connected, user.disconnected, user.opened, and user.closed events
  • Contacts, Numbers, and Teams, plus contact.created, contact.updated, contact.deleted, number.opened, and number.closed events
  • Analytics report exports through POST /v1/analytics/report/export, delivered as CSV files behind a presigned URL

Proposed actions

  • Target capability: propose an outbound call through POST /v1/users/:id/calls with number_id and an E.164 destination
  • Target capability: propose a tag or a comment on a call through the Tag a Call and Comment a Call endpoints
  • Target capability: propose a contact create or update through the Contacts endpoints
  • Target capability: propose a webhook through POST /v1/webhooks with custom_name, url, and the events to receive

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Return a missed call within the hour

    A call.ended event without answered_at marks a missed call. The operator checks the user's availability and drafts the outbound call for approval.

    With Callback Promise

  • Summarize and tag each finished call

    summary.created and topics.created arrive after the call. The operator proposes a comment with the summary and the tags that fit, for one-click approval.

    With Call Summary

  • Catch a run of negative calls

    sentiment.created events feed a rolling read per number and agent. When negatives cluster, the operator raises it with the call ids as evidence.

    With Sentiment Spike

  • Dial a new lead first

    When a contact.created event matches a lead, the operator proposes the first call to the assigned user and records the outcome as a comment.

    With Lead Response

Requirements

  • An Aircall account whose Dashboard user can generate an API key under Integrations > API keys; the token is shown once
  • A public HTTPS URL to receive webhook events, each carrying the webhook token that identifies your account
  • The AI Assist or AI Assist Pro package for Conversation Intelligence endpoints and events
  • The Analytics+ add-on for report exports, and a user signed in to Aircall Workspace or the Aircall Phone app to place calls
Authentication
For a private app, an API ID and API token from Dashboard > Integrations > API keys, sent as Basic auth; for a public app, an OAuth 2.0 access token from POST /v1/oauth/token.

Limits

  • 120 requests per minute per company, reported in X-AircallApi-Limit, X-AircallApi-Remaining, and X-AircallApi-Reset headers
  • Paginated Calls and Contacts stop at 10,000 items; pages hold 1 to 50 results, 20 by default
  • Recording and voicemail URLs expire after 1 hour, short URLs after 3 hours; archive on call.comm_assets_generated
  • An outbound call fails when the user is offline, on a call, in do-not-disturb, or in after-call work

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Aircall ↗

Questions and answers

Which webhook events does Aircall send?
Events cover users, calls, numbers, messages, contacts, Conversation Intelligence, AI voice agents, analytics, and outbound campaigns. Call events run from call.created through call.ended, plus call.tagged, call.commented, and call.comm_assets_generated. Omit the events parameter when creating a webhook and it receives all of them.
How does Aircall rate limit the API?
120 requests per minute per company. Each response carries X-AircallApi-Limit, X-AircallApi-Remaining, and X-AircallApi-Reset so you can pace calls. Paginated Calls and Contacts lists stop at 10,000 items.
Do I need a public app?
No. A private app uses an API key and serves a single Aircall account with no review. A public app uses OAuth 2.0, serves many customers, and needs Aircall review before listing on the App Marketplace.
Ask about Aircall

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.