Aircall Public API
★ Only Publicly Available OpenAPI DocumentCommunicationsVoice Telephonybasic, bearer68 EndpointsREST
For Agents
Place outbound calls, send SMS, manage users, contacts, and tags, and subscribe to call events through the Aircall phone system.
Use for: Place an outbound call from a specific user, I want to send an SMS through Aircall, List all calls in the last 24 hours, Search for a contact by phone number
Not supported: Does not handle email, video conferencing, or live chat — use for cloud telephony, SMS, and contact-centre call workflows only.
Jentic publishes the only available OpenAPI specification for Aircall Public API, keeping it validated and agent-ready. Aircall is a cloud-based phone system for sales and support teams, exposing 68 endpoints for managing calls, users, contacts, numbers, teams, tags, webhooks, and SMS messaging. Both Basic Auth (API ID and token) and OAuth 2.0 bearer tokens are supported. The API is rate-limited to 60 requests per minute per company.
Install Jentic One Beta
Connect the Aircall Public API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Aircall Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Aircall Public API.
Place outbound calls and dial phone numbers from a specified user via /v1/users/{id}/calls and /dial
Search, retag, and annotate calls with metadata, comments, and tags
Pause and resume call recording mid-call for compliance handling
Send and list SMS messages tied to a phone number
Manage users, teams, and number assignments across V1 and V2 endpoints
Register webhooks for call, SMS, and contact lifecycle events
Maintain a contacts directory and pull conversation intelligence transcripts for call review
Use Cases
Patterns agents use Aircall Public API for, with concrete tasks.
★ CRM-Triggered Outbound Calling
Trigger Aircall outbound calls directly from a CRM workflow without forcing reps to switch apps. POST /v1/users/{id}/calls dials the contact's number from the chosen rep's phone, and POST /v1/calls/{id}/tags + /comments capture call disposition back into the CRM record.
Find the user with email rep@example.com, place an outbound call from them to +14155551234, then add the tag 'follow_up' to the resulting call
Two-Way SMS Workflows
Send transactional and conversational SMS from Aircall numbers and capture replies via webhook. POST under the messaging endpoints sends a message tied to a number, and registered webhooks fire on inbound SMS so an agent or workflow can reply within the conversation thread.
Send an SMS from number num_555 to +14155551234 with body 'Your callback is scheduled for 3pm', and register a webhook on inbound SMS to forward replies to a Slack channel
Call Quality and Compliance Monitoring
Pull call records, search by tag or user, and pause recording during PCI or sensitive segments. GET /v1/calls/search filters by user, number, and date range, POST /v1/calls/{id}/pause-recording suspends the recording, and /resume-recording restarts it for compliant playback.
Search calls for user_42 from yesterday, pull each call's transcript via Conversation Intelligence, and flag any call that contains the phrase 'cancel my account'
AI Agent Phone Operator
An agent operating Aircall through Jentic can place follow-up calls, send SMS, and tag calls based on outcome — driven by CRM events. Jentic keeps the OAuth token or basic credentials in the vault and exposes only the operations the agent needs.
Search Jentic for 'place an outbound call', load the schema for POST /v1/users/{id}/calls, place a call from user_42 to +14155551234, then comment 'auto-dialed by agent' on the resulting call
Key Endpoints
68 endpoints — jentic publishes the only available openapi specification for aircall public api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/v1/users/{id}/calls
Start an outbound call from a user
POST
/v1/users/{id}/dial
Dial a phone number
GET
/v1/calls
List calls
GET
/v1/calls/search
Search calls by user, number, or date
POST
/v1/calls/{id}/tags
Add tags to a call
POST
/v1/calls/{id}/comments
Add a comment to a call
POST
/v1/oauth/token
Exchange credentials for an OAuth access token
POST
/v1/calls/{id}/pause-recording
Pause call recording
POST
/v1/users/{id}/calls
Start an outbound call from a user
POST
/v1/users/{id}/dial
Dial a phone number
GET
/v1/calls
List calls
GET
/v1/calls/search
Search calls by user, number, or date
POST
/v1/calls/{id}/tags
Add tags to a call
POST
/v1/calls/{id}/comments
Add a comment to a call
POST
/v1/oauth/token
Exchange credentials for an OAuth access token
POST
/v1/calls/{id}/pause-recording
Pause call recording
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Aircall basic credentials or OAuth bearer tokens are stored encrypted in the Jentic vault. Jentic refreshes OAuth tokens on expiry and applies the correct auth header per call, so secrets never enter agent context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'place an outbound call') and Jentic returns the matching Aircall operation with its input schema, removing the need to navigate 68 endpoints manually.
Time to first call
Direct Aircall integration: 2-4 days for OAuth setup, webhook handling, and rate-limit-aware pagination. Through Jentic: under 1 hour.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Aircall Public API through Jentic.
Why is there no official OpenAPI spec for Aircall Public API?
Aircall does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Aircall Public API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Aircall Public API use?
Aircall supports two schemes: HTTP Basic Auth using an API ID and API token, or OAuth 2.0 bearer tokens obtained via POST /v1/oauth/token. Jentic stores either credential type encrypted in the vault and applies the correct header on each call.
Can I place an outbound call with the Aircall API?
Yes. POST /v1/users/{id}/calls starts an outbound call from a specified user, and POST /v1/users/{id}/dial dials a number into a user's softphone for them to confirm.
What are the rate limits for the Aircall Public API?
Aircall enforces 60 requests per minute per company. For higher-throughput use cases such as bulk call exports, paginate with a backoff loop rather than parallel requests.
How do I send an SMS with the Aircall API through Jentic?
Run pip install jentic, search Jentic for 'send aircall sms', load the messaging endpoint schema, then execute with the from-number, to-number, and body. Jentic applies the OAuth bearer or basic auth credentials transparently.
Can I subscribe to call events via webhook through the Aircall API?
Yes. The webhook endpoints under /v1/webhooks let you create subscriptions for call.created, call.ended, sms.received, and contact lifecycle events. The webhook payload includes the related resource ID for follow-up API calls.
GET STARTED