Blog · WhatsApp and channels
What the WhatsApp Business API is, and how you get one
What the WhatsApp Business API is, what Meta requires: WABA, verification, number and templates, and which channel rules shape your project.
What is the WhatsApp Business API and what do I need to get one?
The WhatsApp Business API is the official route through which a system can read and send WhatsApp messages on behalf of a company. It is not an app: it has no screen of its own, it is not installed on a phone, and on its own it displays no conversation at all. Getting one takes four things from Meta: a WhatsApp Business Account (WABA), verification of your company, a phone number registered to that account, and approved templates if you also intend to message people first. One rule governs all of it. Within 24 hours of the customer's last message you may reply in free text, and outside that window the only thing that goes out is a template Meta reviewed beforehand.
Almost every WhatsApp project starts at the wrong end. People debate the model, the price and the tone of the replies, and by the third meeting the question that should have come first finally shows up: how are messages going to get in and out?
That question has exactly one official answer, and this article is about it.
Three things with confusingly similar names
| What it is | Who it is for | What it looks like |
|---|---|---|
| People | The usual app | |
| WhatsApp Business (the app) | A small business | An app on a phone, with a catalog and quick replies |
| WhatsApp Business Platform | A company with systems | An API. No screen at all |
The third one is what people call “the WhatsApp API,” “WhatsApp Business API” or “Cloud API.” Same thing, three names. It is not an upgraded version of the app: it is a different road, with different rules, a different process and a different way of being billed.
And the part that explains everything else: the API shows no conversations. It is a door. It receives what comes in and lets out what you send. Whatever displays, sorts and answers those messages is a separate system, and you pick it.
What Meta asks for, in order
Four pieces. None is optional, and the order below is the order worth solving them in.
1. A WhatsApp Business Account (WABA)
This is the container. Your numbers, your templates and your sender quality history all live inside the WABA, which in turn hangs off a Meta business account, the same one used to manage pages and ads.
There is a decision here that looks administrative and is not: whose name the account is in. In your name, any vendor connects through a permission you grant and can revoke. In the vendor’s name, your number lives in someone else’s house. Both work identically on day one and differ enormously on the day you want to switch vendors.
2. Business verification
Meta needs to know you exist. It asks for incorporation documents, an address and some way of confirming that the business and the website belong to the same organization. It does not measure size or revenue, it checks identity.
This is the slowest step and the only one that does not depend on you. It can clear in a day or bounce three times over a detail in a document. Start here.
3. A phone number
The number gets registered inside the WABA. The rule that surprises everyone in the first meeting is this one: a number lives in the app or in the API, never both. Register it on the platform and it stops opening on the phone.
So decide early whether you are bringing the number people already know, the one printed on your cards and your site, or starting on a fresh line and migrating the known one once everything is tested. Both are reasonable. The second cannot be chosen after the fact.
Each number also carries a display name, which is how customers see you, and Meta reviews it the same way it reviews a template.
4. Approved templates, if you plan to message first
You only need these if your company starts conversations. If you strictly answer people who write to you, you can launch without a single one.
The rule that reshuffles the whole project: the 24-hour window
This is the part almost nobody mentions before selling, and the one that decides what is possible.
- Within 24 hours of the customer’s last message, you can reply in free text. Talk, ask, quote, send a photo, book.
- Outside those 24 hours, the only thing that goes out is an approved template.
It is not a limitation of the tool you hire. It belongs to the channel and applies to everyone. If someone offers to send free text to a cold list over WhatsApp, they are describing a route that is not official.
The practical consequence is that your use cases split in two, and sorting them early saves weeks:
| What you want to do | Who starts | What you need |
|---|---|---|
| Answer questions, quote, book | The customer | Nothing extra |
| Remind someone of tomorrow’s appointment | You | Approved template |
| Chase an overdue invoice | You | Approved template |
| Announce that an order shipped | You | Approved template |
Everything in the bottom half waits exactly as long as Meta takes to approve your template, so registering them on day one is the difference between launching in two weeks and launching in five.
How a template gets approved, and why yours gets rejected
You register the text with its variables, pick a category, and Meta reviews it. The category matters more than it looks: it defines what you may say and it also drives what the send costs.
- Utility: something the person expects because a relationship already exists. An order confirmation, an appointment reminder, a shipping notice.
- Authentication: one-time codes and verifications.
- Marketing: promotions, news, invitations. The most heavily filtered category.
The most common rejection is not about intent but about wording: variables at the very start or end of the message, text that never says who it is from, or a utility template that is quietly selling something. You fix it and resubmit, but every round costs days.
Sending limits go up on their own, and they come down too
A new line cannot message everybody on day one. Meta assigns a limit on how many distinct customers you can contact in 24 hours and raises it in tiers as you demonstrate good behavior.
What drives that climb is the number’s quality rating, and your customers are the ones writing it: block you or report you and it falls. A number with low quality loses its limit, and if it keeps falling, Meta restricts it.
That is the real reason a purchased list is a bad idea on this channel. It is not a moral rule: it burns the number, and the number is the line your actual customers write to.
What to check before signing with any vendor
Six short questions. All of them answer yes or no, and all six get expensive if you ask them later:
- Is the WABA in my name?
- Is the vendor recognized by Meta as a technology partner?
- Can I see and export my conversations if I leave?
- Is access to my account a permission I can revoke?
- Who creates and maintains the templates?
- What happens to the number if the contract ends?
The second question separates two worlds. A partner recognized by Meta works against the official platform and answers to it. Anyone connecting WhatsApp by reading the app’s QR code appears on no Meta list, because they are not using the platform at all, and that is precisely the route that ends with a suspended number.
And once the line exists, who answers?
The channel ends here. What comes next is a system that receives those conversations, shows them, answers them and looks up whatever data a good answer needs.
That is what Meteor does, as an official Meta Tech Provider. The line stays yours: you keep your own WhatsApp Business Account and your own credentials, and access is a permission you grant and can revoke. On top of what Meta charges for messages there is no resale and no markup. To see the scope against a real operation, read the Spanish AI agent for WhatsApp Business page. To wire it into your own code instead, there is a documented API, a TypeScript SDK, an MCP server and signed outbound webhooks under Developers.
Two questions are kept separate because they deserve their own answer: what the channel costs and whether the API or the WhatsApp Business app fits you.
The limits
What this article does NOT answer
We would rather say it here than leave you hunting for something that is not there.
-
It is not a walkthrough of Meta's console. The screens and the exact order of the steps change several times a year, and Meta is the one who documents them.
-
It does not compare platforms or vendors. What is here is Meta's channel and its rules, which are the same for anyone using it.
-
It does not work out what the channel costs. Meta's billing model changed and deserves its own article, linked further down.
-
It does not tell you whether your current vendor supports each step. Your vendor answers that, and it is worth asking with these names in hand.
Keep going
What this article mentions, in detail
The integrations, the Mets and the automations named above, each with its own page.
Cards marked ES open a page published in Spanish.
- Section
ES
AI agent for WhatsApp Business
Who answers the conversations once the official line is actually connected.
- Automation
Cobrar la cartera vencida por WhatsApp, sin perseguir a nadie a mano
Where the 24-hour window really bites, because that is the case where you message first.
- Integration
CRM de Meteor
Where every contact arriving through the channel is recorded, with nothing external to connect.
- Section
Developers
API reference, TypeScript SDK and MCP server, for wiring the channel into your own code.
Where it comes from
Sources
Everything this article claims that we did not measure ourselves, with its origin.
Frequently asked
Questions on this topic
Access itself costs nothing. Meta charges neither for opening the account nor for connecting. What carries a rate is outbound template traffic, and that rate depends on the country and on the template category. Separate from all of it is whatever the platform you use to run the channel charges, which is a different vendor and a different bill.
No. Meta asks for a verifiable company, not a big one: essentially that it exists, that there are documents in someone's name, and that there is a site or presence you can check. Business verification is an identity check, not an assessment of size or revenue.
It is a message you register in advance and Meta reviews before letting you send it. It has fixed text plus slots for variables, such as a person's name or an invoice number. It exists because outside the 24-hour window Meta will not let a company write whatever it wants: only what was approved beforehand goes out.
The technical part takes hours. The part nobody controls is business verification, which can take a day or several weeks depending on how your paperwork looks and how often it comes back. Start there instead of leaving it for last: it is the only step you cannot speed up by working harder.
Yes, and that is one reason the account should be in your name. The WABA and the number are yours, and a vendor connects to them through a permission you can revoke. If the account ended up in the vendor's name, moving stops being a permission change and becomes a negotiation.
Keep reading
Other articles on the same thing
What it is and how it works
Enterprise AI agent security: what to check before enabling one
How do I evaluate an enterprise AI agent's security before connecting it to my data?
- Published
- Reading time
- 4 min read
WhatsApp and channels
Meteor vs Kommo: what a Latin American company should actually compare
When is Kommo the right choice, and when is Meteor, for selling on WhatsApp?
- Published
- Reading time
- 6 min read
WhatsApp and channels
The WhatsApp API or the WhatsApp Business app, which one is yours
What is the difference between WhatsApp Business and the API, and which suits me?
- Published
- Reading time
- 5 min read
Want to see it running on your operation?
We show it with your own accounts connected, not with a canned demo.