WhatsApp Business Platform: A Map of Every Piece
Open Meta's WhatsApp developer docs and the sidebar runs to hundreds of pages: Cloud API, Marketing Messages API, Direct Send, Groups, Calling, Flows, Payments, Embedded Signup, partner programs, a new account model. Vendors use the names loosely, and it is hard to tell which pieces you need.
The WhatsApp Business Platform is Meta's umbrella name for everything a business or developer uses to message WhatsApp users from software. It is not one API but a set of APIs, account types, tools and partner roles that fit together.
This post is the map: what each piece does, who uses it and where it stands as of October 2026.
The platform in one table
Here is every major piece, grouped by job.
| Piece | What it does | Who uses it | Status, October 2026 |
|---|---|---|---|
| Cloud API messaging | Sends and receives text, media, interactive messages and templates | Everyone on the platform | The core |
| Marketing Messages API | Sends marketing templates with delivery optimization and conversion metrics | Marketers | Generally available since November 19, 2025 |
| Direct Send | Sends utility messages without pre-built templates | High-volume senders | Phased rollout; authentication in alpha |
| Groups API | Creates and messages invite-only groups | Official Business Accounts | Open to all OBAs |
| Calling API | Voice calls inside WhatsApp | Support and sales teams | Live, with country exclusions |
| Flows | Multi-screen forms inside a chat | Lead capture, booking, quotes | Live |
| Payments | In-chat payment requests and order details | Commerce in specific markets | India, Brazil and Mexico documented |
| Meta Business Agent | Meta's hosted AI agent for customer service | Businesses wanting AI without a build | Launched globally June 2026 |
| Business Management API | Manages accounts, numbers, templates and analytics | Developers and ops | The control plane |
| Webhooks | Push inbound messages, statuses and account events | Every integration | Required |
| Embedded Signup | Onboarding popup partners put in their product | Tech Providers and Solution Partners | Versions 2 and 3 deprecated October 15, 2026 |
| WhatsApp Manager | Web interface for accounts, templates and numbers | Everyone | Live |
The complete guide to the WhatsApp API compares the official platform with unofficial options.
Messaging: three ways to send
Which sending route you use depends on the category of message.
Cloud API messaging is the default. You POST to a phone number's /messages endpoint with either a template (allowed any time) or a free-form message (only inside the 24-hour customer service window). The recipient_type is individual for one-to-one chats or group for the Groups API. Our Cloud API explainer covers the request model.
Marketing Messages API is a separate endpoint for promotional templates. Meta says it shares the Cloud API's schema and billing model, and adds delivery optimization, automatic creative tweaks, read and click benchmarks, conversion metrics and message expiry. It matters for planning because, per Meta's page, Messaging accounts created on or after April 13, 2027 cannot send marketing through the Cloud API, and the Cloud API stops supporting marketing messages on October 13, 2027. See our guide to the Marketing Messages API.
Direct Send removes the template step for utility messages. You send a normal message with a category field and Meta matches it to an existing template or auto-generates one behind the scenes:
{
"messaging_product": "whatsapp",
"recipient_type": "individual",
"to": "+919811122233",
"type": "text",
"text": { "body": "Order 4821 has shipped. Track it: https://example.com/t/4821" },
"category": "utility"
}
Per Meta's Direct Send docs, utility Direct Send is generally open to business portfolios at the 100,000 or unlimited messaging limit, authentication is in alpha, and marketing is not supported. A paced message can be dropped, which shows up as a failed status with error 135000.
Beyond text: Groups, Calling, Flows and Payments
These four add capabilities to the chat itself, each with eligibility rules.
Groups API. Businesses with an Official Business Account can create groups, send invite links and message the group. Per Meta's Groups page, groups top out at 8 participants, a number can create up to 10,000 groups, and each group can hold only one Cloud API business. Text, media and templates work. Calling, disappearing messages, view-once, authentication, commerce and interactive messages do not, and neither do editing or deleting messages. It is unavailable to WhatsApp Business app numbers on coexistence, and it cannot touch groups your number is already in. Our post on sending to a WhatsApp group by API compares the options.
Calling API. Businesses can receive and place WhatsApp voice calls over WebRTC or SIP. User-initiated calls are free; business-initiated calls are billed in six-second pulses by the recipient's country. Business-initiated calling needs the user's permission and a messaging limit of at least 2,000, and business numbers with US, Canadian, Egyptian, Vietnamese or Nigerian country codes cannot place those calls. A user's call opens a customer service window just like a message. More in our guide to the WhatsApp Calling API.
Flows. Structured, multi-screen forms that open inside the chat, defined in Flow JSON. Meta's own examples include loan leads, insurance quotes and personalised offers. Inside an open window you send one as an interactive Flow message. See WhatsApp Flows.
Payments. Market-specific. Meta documents UPI-based payments with order_details messages for India, Pix, Boleto and payment links for Brazil, and orders, payment links and cash vouchers for Mexico.
Running it: accounts, management and webhooks
Accounts. Everything belongs to a business portfolio in Meta Business Suite. Since the rollout that began September 23, 2026, the old WhatsApp Business Account (WABA) is two things: a WhatsApp account that holds one phone number and its profile, and a Messaging account that holds templates, billing and webhook subscriptions and keeps the old WABA ID. Existing IDs and calls keep working. New WhatsApp account IDs and endpoints arrive with a new Graph API version in the first half of 2027, and phone-number-path APIs must move to them in the first half of 2028. Our guide to the WhatsApp Business Account explains the split.
Business Management API. The control plane. It creates accounts, adds and removes numbers, links accounts, assigns partner access, manages templates and billing, and returns messaging, pricing and template analytics.
Webhooks. The platform pushes everything inbound: messages, delivery statuses, template approvals and quality changes, account alerts and limit increases. Meta retries failed deliveries for up to 7 days, payloads can be up to 3 MB, and mutual TLS is supported. Start with our guide to WhatsApp API webhooks.
Getting on it: direct, partners and Embedded Signup
There are three roles for getting businesses onto the platform, and they decide who bills whom.
| Role | Who it is | Billing |
|---|---|---|
| Direct developer | A business building on its own app for its own numbers | Pays Meta directly |
| Tech Provider | A software company onboarding its customers | Customers add their own payment method |
| Solution Partner | A provider that also extends credit to customers | Shares its credit line and bills customers |
Meta also has a Tech Partner tier that Tech Providers can upgrade to, and Solution Partners are what most people call Business Solution Providers, or BSPs. Our post on BSP fees explains how they charge on top of Meta's rates.
Embedded Signup is how partners onboard customers. The customer logs in with Facebook or Meta Business credentials inside a popup, picks or creates a portfolio and accounts, verifies a phone number and enters a display name. The partner receives the Messaging account ID, the phone number ID and a code it exchanges server-side for a token. Partners start at 10 new customers per rolling 7 days, rising to 200 after verification and App Review. Our Embedded Signup guide covers the build.
The new account model lets a client share one WhatsApp account with up to five Solution Partners, each with its own Messaging account and billing, so one number can use different providers for marketing and support.
What sits outside the platform
Some things people expect from "WhatsApp for business" are not part of the platform at all.
- The WhatsApp Business app. A free phone app operated by people. Coexistence lets one Business app number also use the Cloud API, with a fixed 20 messages per second and some app features switched off.
- Your existing groups. The Groups API only creates new groups. Groups your number is in stay out of reach.
- Status and Channels. Meta's coexistence documentation lists both as unsupported on the Cloud API.
- Linked-device automation. Tools that drive a regular account as a companion device, like WhatsApp Web, are not endorsed by Meta. See our post on the unofficial WhatsApp API.
- Click-to-WhatsApp ads. Bought in Ads Manager, not through the platform, though they connect to it through the free entry point window.
Two newer pieces of the platform get their own guides: the WhatsApp Business Calling API and the WhatsApp Payments API.
Where Tenashi fits
The platform is built for business-initiated, structured messaging at scale, with Meta in the loop on templates and billing. It leaves out the everyday work on the number customers already use: DMs and existing groups, answered by a team. That is where Tenashi sits.
You link your existing WhatsApp or WhatsApp Business number by QR scan. Your team gets one shared inbox for DMs and groups, a CRM with deals and a pipeline under every chat, tickets with SLAs, scheduled sends and roles. Developers get an API on every paid plan that sends to a phone number or an existing group by conversationId, plus signed webhooks.
Tenashi is not part of the WhatsApp Business Platform and is not a Meta Business Solution Provider. It has no templates, Flows, calling, payments or green tick, and its sends are deliberately paced. For OTPs and high-volume alerts, use the platform; for the team conversations, start from $18/mo.
See every feature · Get started
FAQ
Is the WhatsApp Business Platform the same as the WhatsApp Business API?
Mostly, yes. "WhatsApp Business API" is the older name, still used by vendors. Meta now calls the whole offering the WhatsApp Business Platform, which includes the Cloud API, the Marketing Messages API, Direct Send, Groups, Calling, Flows and management APIs. The self-hosted On-Premises API that once sat alongside the Cloud API was retired in October 2025.
What is the difference between a Tech Provider and a Solution Partner?
Both build software that onboards other businesses through Embedded Signup. A Tech Provider's customers add their own payment method and pay Meta directly. A Solution Partner also holds a line of credit, shares it with customers and bills them itself, which is why most companies called BSPs are Solution Partners. Tech Providers can upgrade to Tech Partner.
Do I need a BSP to use the WhatsApp Business Platform?
No. Any business can go direct: create an app in Meta for Developers, add WhatsApp, register a number and pay Meta. A BSP or Tech Provider saves the build by giving you a dashboard, onboarding help and support, usually for a subscription or per-message markup on top of Meta's rates.
Which parts of the platform cost money?
Meta charges for delivered messages by category and country, for business-initiated calls by duration, and for Meta Business Agent messages by tokens. Access to the APIs, Embedded Signup, WhatsApp Manager and webhooks is free. Partners such as BSPs add their own fees, and some features need eligibility rather than payment.
You rarely need every piece on this map. Pick the job, find the one or two pieces that do it, and ignore the rest. If the job is your team working your own number, see how Tenashi does it.