Overview
SMS in Aircall
Learn how Aircall's Messaging API handles SMS, MMS, and WhatsApp — including the two sending modes and how they shape the conversation flow
Messaging API access is not available for all subscription plans.All numbers must meet carrier registration requirements and local regulations before you can send messages.
The Messaging API lets your integration send and receive SMS and MMS through any Aircall number — programmatically, from your own systems.
Use it to send messages to individuals or groups, receive inbound replies, trigger conversations that agents can continue in the Aircall app, and track all messaging activity (including WhatsApp) through webhook events.
Sending modes
There are two sending modes:
Your system owns the entire conversation, including rendering messages in your own interface. Inbound replies are routed to your callback URL, and nothing appears in the Aircall app. Needs additional setup.
Messages are delivered into the Aircall app, so agents can jump in and continue the conversation. No additional setup is required — you can start sending right away.
Your choice of sending mode determines how the conversation flows and whether any setup is required on the number.
| In Agent Conversation | Full control | |
|---|---|---|
| 🔧 Configuration | Not required — send immediately on any SMS-enabled number | Required — register a callback URL on the number before sending |
| 👁️🗨️ Visible in Aircall app | ✓ Yes — agents see the conversation thread | ✗ No — your system owns rendering and storage |
| 💬 Agents can reply via app | ✓ Yes | ✗ No |
| 🏞️ MMS Support | ✗ SMS only | ✓ SMS and MMS |
| 👥 Group SMS | ✓ Yes | ✓ Yes |
| 📫 Inbound delivery | Webhook events + Aircall app | Pushed to your callback URL |
| 👌 Best for | CRM-triggered greetings, missed call follow-ups, any flow where agents continue the conversation | OTPs, order confirmations, fully automated outreach, external messaging platforms |
ImportantOnce a number is configured for full control mode, it won't be able to send or receive messages via the Aircall app. These two modes are mutually exclusive per number — to switch, delete the configuration first.
Endpoints at a glance
The Aircall Messaging API covers the full lifecycle of business messaging — sending, receiving, and logging — across SMS, MMS, and WhatsApp.
| Capability | Description |
|---|---|
| Send SMS & MMS | Send outbound text or media messages from an Aircall number, triggered by any external system. API reference → |
| Send group SMS | Send the same message to multiple recipients in one API call — each contact gets an individual thread. API reference → |
| Receive inbound messages | Get contact replies pushed to your system in real time via a callback URL or message webhook events. API reference → |
| Send into agent conversations | Trigger automated messages that appear as conversation threads in the Aircall app, so agents can reply directly. API reference → |
| Subscribe to message events | Receive message.sent message.received and message.status_updated webhook events to log all SMS activity in your systems. Webhook reference → |
| Capture WhatsApp activity | The same message webhook events also fire for WhatsApp — subscribe once to capture both SMS and WhatsApp in your integration. Webhook reference → |
Plan & pricing
Access to the Messaging API depends on how it's being used.
Direct API access requires the Professional plan.
If you are calling the Messaging API directly — for example, building your own integration or testing from your own account — your Aircall account must be on Professional. Contact your Customer Success Manager to upgrade.
Access through an integration is available on any plan.
If an integration is calling the Messaging API on your behalf, the Professional plan restriction does not apply — the integration can send and receive messages regardless of the plan your account is on.
Message volume from both the API and the Aircall app is combined on your invoice. Per-message fees are identical regardless of the sending method.
Rate limits
All Messaging API endpoints share a global limit of 60 requests per minute. Additional per-number limits apply based on number type and country.
| Number type | Hourly | Daily | Monthly |
|---|---|---|---|
| US & Canada numbers | 1,000 | 10,000 | 20,000 |
| French mobile lines | 100 | 1,000 | 10,000 |
| Other lines | 500 | 2,000 | 20,000 |
Only domestic messaging is supported, with the exception of US–Canada cross-border messages. Rate limits are subject to change without notice.
Regulatory requirements
Messaging via the API must comply with local regulations. Requirements vary by country — always verify your use case before going live.
United States & Canada
US long codes and US/CA toll-free numbers must be fully registered before use — unregistered numbers will have messages blocked by carriers. Automated and marketing SMS are permitted with proper registration (see A2P 10DLC and toll-free guidelines) and demonstrable customer consent.
France
Mobile lines are for personal and conversational use only. Automated or bulk SMS via API is not permitted, but conversational messaging remains allowed. Mobile lines should be assigned to a single agent who controls their usage.
Seek local legal guidance.Aircall does not provide compliance advice — verify that your specific use case is permitted in your target countries before sending.
Updated 3 days ago