LinkedIn
Instagram
WhatsApp
Telegram
Gmail
Outlook
Google Calendar
Join Slack Community
WhatsApp API: Types, Access, Pricing and Limits
// Link an existing WhatsApp account
const account = await client.account.connectWhatsapp();
// account.qrCodeString -> show to the user
// or pass a pairing_phone_number instead
const chats = await client.chats.list({
account_type: 'WHATSAPP'
});What is the WhatsApp API?
| Name | What it is | Who operates it | Access requirements |
|---|---|---|---|
| WhatsApp Business Platform (Cloud API) | Meta's own official API for provisioning new business phone numbers and sending template messages at scale | Meta | Meta developer app, WABA, business phone number, verification for higher tiers |
| Business Solution Provider (BSP) access | A third party (Twilio, 360dialog and similar) reselling the same Cloud API, wrapped in its own dashboard and billing | Meta infrastructure, BSP-managed | Same underlying Meta requirements, provisioned through the BSP |
| Unified session API (Unipile) | Connects a WhatsApp account, business or personal, the way WhatsApp Web does, by QR code or pairing code | Unipile, on behalf of the authenticated user | No Meta Business verification, no new number, no template approval |
What are the different types of WhatsApp API?
| Type | Provisioning | Best for | Works with an existing account |
|---|---|---|---|
| Cloud API | New business phone number + Meta Business verification for higher volume | Companies sending high-volume marketing or notifications at scale | No, requires a new number |
| On-Premise API | Deprecated. Meta retired it and pushed migration to the Cloud API | Legacy integrations only | No |
| WhatsApp Business App | Free consumer-facing app, manual setup on one device | Small businesses managing chats by hand | Yes, but manually, one device, not programmatic |
| Unified session API (Unipile) | Links the account the way WhatsApp Web does, no new number | SaaS platforms embedding each user's own WhatsApp account in-product | Yes, this is the primary use case |
WhatsApp API ecosystem
Meta offers two official APIs that allow businesses to integrate WhatsApp into their software. Both are designed to enable high-volume messaging, with features such as templated messages, media sharing, and customer support tools.
WhatsApp Business API
The Business API was the first solution released by Meta to help companies interact with their customers on WhatsApp. It is typically self-hosted or managed by an approved provider, giving businesses more control over infrastructure. It supports templated outbound messages, customer replies, and rich media formats, making it suitable for enterprises that need to integrate WhatsApp directly into their CRM, contact center, or support system.
WhatsApp Cloud API
Launched later, the Cloud API is fully hosted by Meta. It removes the need for companies to manage servers or handle heavy infrastructure. The Cloud API provides similar core functionalities, sending and receiving messages, managing templates, and supporting media, while being easier to deploy for developers. It is positioned as a faster way to access WhatsApp programmatically, especially for businesses that want scalability without the overhead of on-premise hosting.
The complexity of WhatsApp integration
While Meta's Business and Cloud APIs provide powerful capabilities, their integration is far from straightforward. Developers need to manage business verification, template approvals, and message quotas before even going live. Hosting or connecting to the Cloud API also requires handling webhooks, encryption, and compliance with strict opt-in rules. These hurdles often delay projects and limit access to smaller SaaS providers who want to add WhatsApp quickly to their platforms.