The WhatsApp Business API, without the sales pitch.
What it is, what it is not, how to get access, what Meta will bill you, and the rules that decide whether a message goes through. Written by people who run it, including the parts that are inconvenient for us to tell you.
Not an app.
Access.
There are three WhatsApp products and they get confused constantly. WhatsApp is the consumer app. The WhatsApp Business app is the free one for small businesses — catalogue, quick replies, labels, one phone. The WhatsApp Business Platform — what everyone calls "the API" — is the third thing, and it is not an application at all.
You do not log into the API. It is an interface that a platform connects to on your behalf, and the platform is what you actually use. That is why "should I get the WhatsApp API?" is really two decisions: whether you need API-level capabilities, and whose software you want in front of it.
Almost everybody now means the Cloud API, hosted by Meta. The older On-Premises API, which you hosted yourself, is being wound down. Watx runs entirely on the Cloud API.
A shared team inbox
Many people working one number at once, with assignment, status and full contact history — the thing the free app cannot do at all.
Broadcasts at real scale
Approved templates to a segment, to people who never saved your number, with delivery and read reporting per recipient.
Automation
Triggers, branching conditions, scheduled follow-ups and HTTP calls — no developer required, but an API if you have one.
AI agents
Answer from your own documents in seconds, run real skills, and hand over to a person on rules you set.
Integrations
A REST API, webhooks, Zapier and a website chat widget, so the conversation and the order stop living in different systems.
Attribution and pipelines
Which ad started the conversation, and which conversation became revenue.
Do not buy this too early.
The free app is genuinely good. Four things break before anything else does, and until one of them has, you are paying for capability you cannot use yet.
More than one person must reply
The app is tied to a handset. No assignment, no shared history, no way to know if Tuesday’s message was ever answered.
Broadcast lists stop reaching people
They cap at 256 and only reach contacts who saved your number. You send to 250 and reach 40.
Nothing connects to anything
No API, no webhooks, no CRM. The order and the conversation that produced it never meet.
The number belongs to a phone
When that person leaves, the history leaves with them.
If none of those are true for you yet, stay on the free app. When one becomes true, the long version of this decision is here: WhatsApp Business app vs the API.
Four things you need.
- 1
A Meta Business Account
Verified, with a business you can document. Verification is Meta’s process, not your provider’s, and it is where most delays happen.
- 2
A phone number
One that can receive a verification code, and that is not currently active on regular WhatsApp. A number already on the WhatsApp Business app can be used either way — see the next section.
- 3
A provider
The API is not something you log into. You connect it to a platform, which is what gives you an inbox, templates, automations and everything else.
- 4
Approved templates
Before you can message anyone outside an open conversation, you need at least one approved template. Usually quick, occasionally not.
Coexistence
One number runs the WhatsApp Business app and the Cloud API together. Your team carries on replying from the phone and the same conversations also land in the platform. Meta caps sending at 20 messages per second, the catalogue and orders are unavailable, and a few app features switch off.
The right starting point for most businesses: it costs nothing to try and changes nothing about how your team works today.
The full list of what switches offFull migration
The number moves onto the Cloud API completely. No throughput ceiling, nothing switched off, the whole template and catalogue surface available.
It ends the WhatsApp Business app on that number, and it is one-way. The better end state for most teams — but a decision to make after you have seen the platform work on your own traffic, not before.
Compare the two routesTemplates and the 24-hour window.
Between them, these two rules explain almost every surprise people hit in their first month on the API.
The 24-hour service window
When a customer messages you, a 24-hour window opens. While it is open you can reply with anything — free text, media, buttons — with no template and no charge. It resets every time they write again. When it closes, you can only send an approved template, and templates are billed.
Which makes reply speed a cost control as much as a service metric.
How the window opens, resets and closesMessage templates
Anything sent outside an open window must be a template Meta approved in advance, filed under marketing, utility or authentication. The category is not a label you choose freely — Meta re-categorises templates it judges to be filed wrongly, and the categories are priced very differently.
Why templates get rejected, and how to passTwo bills, not one.
Meta bills you per delivered template message, by category and by the recipient's country. Your platform bills you for the software. They are separate, and the first one is usually larger.
Service
Free
Your free-form replies inside the 24-hour window.
Utility
₹0.115
Order updates, reminders, receipts. Free if the window is open.
Authentication
₹0.115
One-time passcodes and verification.
Marketing
₹0.8631
Offers, launches, re-engagement. Billed always.
Per delivered message to an Indian number, Meta's list rate as of 1 July 2026, before 18% GST. Rates are per-market and Meta revises them — check the current rate card.
Marketing costs roughly 7.5× what utility costs. That single ratio should shape how you use the channel more than any other number on this page.
Limits, quality
and opt-in.
Your messaging tier caps how many people you can start conversations with per day, and your quality rating decides whether that tier goes up or down. Neither is something a platform can raise for you, whatever anybody implies.
Messaging limits
New numbers start at 250 unique customers per 24 hours and climb through 1,000, 10,000 and 100,000 to unlimited, based on volume and a quality rating that is not low. Replies to inbound conversations are never capped.
The most common first-week surprise: a 40,000-contact segment meeting a 1,000 ceiling.
Quality rating
High, medium or low, calculated mostly from blocks and the reasons people give for them. Volume alone does not hurt you; volume to people who did not ask for it does. Sustained low quality reduces your limit.
How tiers move, and what protects a numberOpt-in
Required before any business-initiated message, collectable through any channel, and the single thing that decides whether your first campaign builds a number or destroys one. A bought list is the fastest reliable way to kill a new number.
What counts as opt-in, and where to collect itEvery provider says the same things.
They all run the same official Cloud API, so delivery is identical and Meta bills you the same whoever you pick. Four questions separate them.
Do you mark up Meta’s per-message rate?
Some add a fee on top of Meta’s. Ask in writing. Watx adds nothing — Meta bills you directly.
Do you support coexistence?
If onboarding ends the WhatsApp Business app on your number, you are committing before you have evaluated anything.
Is the API on my plan, or the top one?
Developer access gated behind an enterprise tier is a very different product from the one in the demo.
Can I export everything and leave?
Contacts and conversations, without opening a support ticket. The answer tells you how the rest of the relationship will go.
Questions, answered.
Is the WhatsApp Business API free?
Access to the Cloud API itself is free, but two things are not. Meta bills you per delivered template message, priced by category and by the recipient’s country. And the API is unusable on its own, so you pay a platform for the inbox, templates, automations and reporting that sit on top of it. Replies you send inside the 24-hour service window are free.
What is the difference between the Cloud API and the On-Premises API?
The Cloud API is hosted by Meta and is what almost everyone now uses — nothing to host, faster onboarding, and it is where Meta ships new features. The older On-Premises API required you to run and maintain the infrastructure yourself. Watx runs entirely on the Cloud API.
Can I keep using the WhatsApp Business app?
Yes, through coexistence: one number runs the Business app and the Cloud API at the same time, your team keeps replying from the phone, and the same conversations also reach the platform. Meta sets trade-offs — sending is capped at 20 messages per second, catalogue and orders are unavailable, and a few app features switch off. Full migration removes those limits but ends the app on that number.
Do my existing chats transfer?
No, on either route, and no provider can change that. The inbox fills from the next message onward and contacts are created as people write in. Export anything you need from your phone first, and import your contact list from CSV separately.
Will using the API get my number banned?
The official Cloud API is the compliant path — the ban risk people talk about comes from unofficial bridges and grey automation tools. Restrictions follow policy breaches: sending without opt-in, prohibited content, or a quality rating that stays low. Using approved templates, honouring opt-outs and segmenting properly is what keeps a number healthy.
How long does it take to go live?
If your Meta Business verification is already done, connecting a number and getting a first template approved is often same-day. If it is not, business verification is the long pole and can take considerably longer — start it first.
Ready when you are.
15-day free trial on the official Meta WhatsApp Business Cloud API. No card, and coexistence means you can keep the WhatsApp Business app on your number.