Most teams meet the WhatsApp Business API at the exact moment the free Business App stops working for them. Two people are fighting over one phone, replies are slipping past midnight, and nobody can tell you how many conversations came in last week. The API solves all of that, but it introduces its own vocabulary, its own approval process, and a pricing model that surprises people on the first invoice.
This guide covers what the API actually is, how it differs from what you are probably using now, what it costs, and the order to do things in so you are live in days rather than a month.
Key takeaways
- The API has no interface of its own. It is plumbing, and you supply the app on top of it.
- Pricing is per 24-hour conversation window, not per message, and the category you pick changes the rate.
- Outside that window you can only send pre-approved templates, which is the rule that catches everyone.
- Approval is fast when your business details and display name match your legal entity exactly.
What the API actually is
The WhatsApp Business App is a phone app. It is free, it runs on one device, and it is genuinely fine for a sole trader. The API is not an app at all. It is an interface that lets software send and receive WhatsApp messages on behalf of a verified business, and it deliberately ships with no user interface.
That means you always need something sitting on top of it: a shared inbox, an automation layer, and somewhere for the conversation history to live. That layer is what you actually buy when you buy a platform. The API itself is just the pipe.
| Business App | Business API | |
|---|---|---|
| Users | 1 phone, up to 4 linked devices | Unlimited agents |
| Automation | Away messages and quick replies | Full programmatic control |
| Cost | Free | Per 24-hour conversation |
| Bulk sending | Broadcast lists, 256 contacts | Approved templates at scale |
| Interface | Built in | You supply it |
| Good for | Solo operators | Teams of two or more |
The practical trigger for switching is almost never features. It is the second person. The moment two people need to answer the same number, the app stops being viable and everything downstream (reporting, routing, accountability) becomes guesswork.
How pricing really works
Meta does not charge per message. It charges per conversation, which is a rolling 24-hour window opened by the first message. Every message inside that window is included, whether you exchange three or ninety.
Conversations are billed in categories, and the rate varies significantly by country:
- Service: the customer messaged you first. Often free within the monthly allowance, and the cheapest category everywhere.
- Utility: order updates, receipts, appointment reminders. Transactional, and tied to an action the customer took.
- Marketing: promotions, launches, re-engagement. The most expensive category, and the most heavily policed.
- Authentication: one-time passcodes and login verification.
The mistake that costs money. Sending a utility-shaped message under the marketing category, or the reverse. Meta reviews category on the template, and misclassification either inflates your bill or gets the template rejected. Categorise by the message's purpose, not by which team requested it.
The number worth modelling before you commit is not cost per message. It is cost per resolved conversation, and it only makes sense next to the labour cost of a human answering the same thing. Most teams find the API cheaper the moment it deflects even a modest share of routine questions.
The 24-hour window and why templates exist
This is the rule that catches every team at least once. When a customer messages you, a 24-hour window opens and you can reply freely with any content. Once it closes, free-form messages are blocked. You can only send a template: a message pre-approved by Meta before you ever use it.
Templates support variables, so "Hi {{1}}, your order {{2}} has shipped" is one approved template covering every customer. Approval usually takes minutes to a few hours.
Rejections are common and almost always for the same reasons: promotional language submitted under a utility category, missing or unclear variable context, or a call to action that does not match the stated purpose. Write the template for what it genuinely does, and approval is routine.
Getting approved without losing a week
The approval path is Meta Business Verification, then a WhatsApp Business Account, then a phone number, then a display name. It moves quickly when your details are consistent and stalls indefinitely when they are not.
- Match your legal entity exactly. Business name, address and registration number must match your registration documents character for character. This is the single largest cause of delay.
- Use a number with no active WhatsApp account. If your intended number is on the Business App, fully delete that account first, or migrate it deliberately.
- Pick a display name that resembles your brand. Meta rejects generic names and anything implying a relationship you do not have.
- Have your website live and consistent. The domain should carry the same business name and contact details you submitted.
- Submit templates early. They can be drafted while verification is pending, so you are not waiting twice.
Teams that fail verification almost always fail on a detail they considered cosmetic. Meta treats the paperwork as the product.
What to build in the first month
Do not try to automate everything at once. The pattern that works is narrow and boring: pick the highest-volume question you already answer the same way every time, automate exactly that, and measure it for two weeks.
For most consumer businesses that is order status. For services it is opening hours and availability. For B2B it is qualification: budget, timeline and fit, asked conversationally so a real person only joins once the lead is worth their time.
Once that one flow is genuinely reliable, add the next. Teams that launch with fifteen flows spend the following month debugging all fifteen simultaneously and usually conclude, wrongly, that the technology does not work.
Frequently asked questions
Can I keep my existing WhatsApp number?
Yes. An existing Business App number can be migrated to the API without changing the number your customers already know. Chat history on the device does not transfer, so export anything you need first.
How long does approval take?
Business verification typically takes one to three business days when documents match. Template approval is usually minutes to a few hours.
Do I need a developer?
Not if you use a platform that provides the inbox and automation layer. You would need one only to connect your own internal systems through the API.
What happens if I message someone outside the 24-hour window?
A free-form message is rejected by the API. You must use an approved template, and the customer must have opted in.