WhatsApp Business Calling API: What It Is and Where It's Headed (2026)

TL;DR: Status at a Glance

What Is the WhatsApp Business Calling API?

WhatsApp has always supported voice calls between individual users. The WhatsApp Business Calling API is something different: it takes that same voice infrastructure and exposes it as a programmable interface for businesses.

Concretely, this means a WhatsApp user can tap the call button on a business's WhatsApp profile and reach the business's systems — not a personal phone, but a programmatic endpoint. Your backend receives a webhook event when a call arrives, your code decides what to do (answer, route to a queue, play a message, transfer to an agent, hang up), and the interaction is tracked like any other API-driven business communication.

The API is built on top of Meta's WhatsApp Business Cloud API, which already handles message sending, receiving, and template management. Adding voice to the same infrastructure means businesses can manage messaging and calling through one integration layer rather than maintaining separate telephony stacks.

How It Differs from Regular WhatsApp Calling

Consumer WhatsApp calling has been available since 2015. When two individuals call each other on WhatsApp, it routes peer-to-peer (or through Meta's relay servers) with end-to-end encryption and no business visibility into the interaction.

The Calling API changes the model for business accounts:

Use Cases for the Calling API

The Calling API is most valuable where messaging alone creates friction or where the conversation naturally escalates to voice:

Current Rollout Status

Meta is rolling out the Calling API in stages, consistent with how they handled the Cloud API itself before broader BSP availability followed. As of 2026, the practical picture looks like this:

The honest summary: the Calling API is real, it is live for some businesses, and it is not yet available for most SMBs through their BSP of choice.

How the Calling API Works

At a technical level, the Calling API follows the same webhook-driven architecture as WhatsApp messaging:

Inbound call flow:

1. A WhatsApp user initiates a call to the business's WhatsApp number.
2. Meta's infrastructure routes the call event to the business's registered webhook endpoint.
3. The business's backend receives the webhook payload and responds — answer the call, route to an agent queue, play an audio prompt, or reject.
4. The call session is maintained through the API for the duration of the interaction.
5. Status events (call connected, call ended, duration) are delivered via subsequent webhook events.

Outbound call flow (where supported):

1. The business sends a call initiation request to the Graph API with the recipient's WhatsApp number and relevant parameters.
2. Meta initiates the call on the user's WhatsApp client.
3. If the user answers, the call connects; webhook events track the session.

The voice media itself runs over WhatsApp's existing encrypted infrastructure. Businesses integrate their telephony systems — contact centre platforms, IVR engines, voice bots — via the API layer. For full technical specifications, Meta's official Cloud API documentation is the authoritative source.

Pricing

Meta charges for the Calling API separately from messaging. The pricing model includes a per-call charge and/or a per-minute rate, and rates vary by country.

Meta publishes current rates on its WhatsApp Business pricing page. Rather than quote specific numbers here — which would be out of date the moment Meta adjusts them — check Meta's official pricing documentation directly before building your cost model.

A few things worth knowing:

• • Rates differ by direction (inbound vs outbound, where both are available)
• • Country of the calling party and receiving number both affect cost
• • Enterprise BSPs may apply their own margin on top of Meta's base rates

Voice on Hyperleap: Honest Status

Hyperleap is a Meta-authorised Business Solution Provider. Our current platform supports:

• Channels: Website chat widget, WhatsApp, Instagram DM, Facebook Messenger
• Message types: Text, images, documents, rich cards, carousels, and WhatsApp-approved templates
• AI agents: Conversational AI that handles support, lead qualification, FAQs, and escalation — entirely over messaging

If you need a WhatsApp voice capability now, the honest path is one of these:

1. Meta direct Cloud API access — if your organisation has the engineering resources and relationship with Meta to access calling directly.
2. Enterprise BSPs with voice products — LivePerson and Infobip both have contact centre + WhatsApp voice integrations built for enterprise deployments.

We would rather give you an accurate picture of where voice sits today than oversell a capability we have not yet shipped. See our features page for a current, accurate list of what Hyperleap supports.

When Voice and AI Agents Come Together

The longer-horizon story here is the most interesting one.

WhatsApp messaging AI agents are already productive today — they qualify leads, resolve support tickets, and hand off complex cases without human intervention. Voice AI agents on WhatsApp represent the next evolution: a natural-language conversation that happens by voice, within an app users already have on their phones, with the business intelligence of a trained AI model behind it.

This is not science fiction. The component pieces — large language models capable of real-time voice interaction, WhatsApp's calling infrastructure, contact centre routing platforms — exist. The integration is what is still maturing.

Frequently Asked Questions