WhatsApp Business API

The WhatsApp Business API is Meta's programmatic interface for sending and receiving WhatsApp messages at enterprise scale. It is distinct from the WhatsApp Business app — the mobile application used by small businesses — in that the API is designed for high-volume, automated, and integrated messaging workflows. Organizations access the API through the Meta Cloud API directly or through a Meta-approved Business Solution Provider (BSP), and use it to send transactional notifications, handle customer support conversations, run marketing campaigns, and deploy conversational AI agents over the WhatsApp channel.

The scale difference between the app and the API is significant. The WhatsApp Business app is designed for a single operator handling a relatively small volume of conversations manually. The API supports thousands of simultaneous conversations, programmatic message sending, CRM and helpdesk integrations, chatbot automation, and webhook-based message routing — all operating against a single business phone number that can be managed by multiple agents or systems simultaneously.

How businesses access the API

There are two primary access paths. Direct API access through Meta Cloud API allows businesses to integrate directly with Meta's infrastructure using standard HTTPS webhooks and REST API calls, managing phone number provisioning and compliance themselves. BSP-mediated access routes API calls through a Meta-approved third-party provider that handles the underlying Meta integration, phone number management, and some compliance requirements — in exchange for a platform or per-message fee on top of Meta's conversation fees.

Phone number provisioning requires Meta review and approval. A business phone number used with the WhatsApp Business API cannot simultaneously be active on the WhatsApp consumer app or the WhatsApp Business app — the number is dedicated to API use once activated. Businesses that want to migrate an existing WhatsApp Business app number to the API can do so but must accept a transition period during which the number is unavailable.

Template messages and session windows

Message type rules govern what a business can send and when. WhatsApp messages through the API fall into two categories with fundamentally different rules.

Template messages are pre-approved message formats that a business submits to Meta for review before use. Once approved, template messages can be sent to users who have opted in to receive messages from the business, regardless of whether a conversation session is active. Template messages are used for transactional notifications: order confirmations, shipping updates, appointment reminders, payment receipts, and authentication codes. Templates must be submitted in all languages the business intends to use, and each template-language combination requires separate approval.

Session messages can be sent and received freely — including rich media, arbitrary text, and interactive elements like buttons and lists — but only within a 24-hour service window. The 24-hour window opens when a user sends a message to the business and resets with each new inbound message. Once the window expires, the business can only restart the conversation by sending an approved template message. This asymmetry between inbound-initiated sessions and outbound-initiated template messages is a defining constraint of the channel and shapes how businesses design conversation flows.

Conversation-based pricing

Meta's pricing model is conversation-based rather than per-message. A conversation is a 24-hour window of messages between a business and a user. Conversations are categorized by type: marketing conversations (business-initiated with marketing intent), utility conversations (business-initiated for transactional purposes), authentication conversations (OTP and verification flows), and service conversations (user-initiated). Each category carries different pricing, with service conversations generally priced lower or free above certain thresholds in some markets. Pricing varies by country and is updated periodically by Meta.

The conversation-based model has implications for how operations are designed. A business that can resolve a customer issue within the first 24-hour window pays for one conversation. A business with a complex issue that spans multiple sessions pays for multiple conversation windows. This incentivizes fast, first-contact resolution — a dynamic that aligns the API pricing model with good CX practice.

WhatsApp in omnichannel CX architectures

WhatsApp is one channel within a broader omnichannel customer support architecture. Organizations that route WhatsApp conversations through the same helpdesk or CRM platform as email, chat, voice, and SMS interactions can apply consistent routing logic, reporting, and quality management regardless of channel. For AI automation, WhatsApp conversations are structurally similar to web chat — text-based, asynchronous, and multi-turn — making them compatible with existing conversational AI architectures. Multi-turn conversation management, intent classification, and entity extraction work the same over WhatsApp as over web chat, with the added constraint that automated outbound messages outside the session window require pre-approved templates. Teams deploying AI agents over WhatsApp must design their conversation flows to either resolve within the 24-hour session window or use template-based re-engagement to continue conversations that span sessions.