Migrating to Meta's official API is the technical decision that confuses business owners the most — and is often presented with bias by those who only sell one of the options. The choice changes cost, risk, and how your team works every day. It's worth understanding exactly what you gain and what you lose beforehand.
Quick answer
What it is: the WhatsApp Business API — or official WhatsApp API — is Meta's approved way for a company to use a WhatsApp number within its own system, with multiple agents, automation, and integration. It is not an app: it is neither downloaded nor installed; the number is operated by a platform.
How much it costs: the account has three parts — the monthly fee for the platform providing the interface, Meta's charges for messages in chargeable categories, and any margin from the intermediary provider. Conversations initiated by the customer and replies within the service window are not charged by Meta; campaign and utility messages are.
How to get it: you need a number not in use on the regular app, a verified business account on Meta, and an approved platform to register it. The process involves creating the business account, verifying the company, registering the number, and approving message templates.
When it makes sense: when the company sends many messages initiated by itself, when losing the number would be serious, or when integration with another system exists. For those who only respond to customers, the QR Code method usually suffices.
In this article
What the official API is (and what it is not)
The official WhatsApp Business API is Meta's approved way for a company to operate a number within its own systems. It is not an app: it is not installed, opened, or has a screen. It is an entry point your customer service tool uses to send and receive messages on behalf of the company.
This leads to the consequence that surprises most who migrate: the number stops working on the regular phone app. You cannot answer on the phone's WhatsApp "when it's easier." All customer service happens inside the system — which is why migrating without a good tool is swapping one problem for another.
In exchange, the company gains three things the unofficial path does not offer: legitimacy with Meta, the ability to handle high volume without surprises, and access to features like catalog, buttons, lists, and the verified business account badge — the last granted at Meta's discretion, not guaranteed by migration.
QR Code or API: the honest comparison
| Connection via QR Code | Meta's official API | |
|---|---|---|
| How it connects | Code scanning, like WhatsApp Web | Number registration on Meta's platform |
| Time to go live | Minutes | From several days to several weeks |
| Phone | Number remains in the app | Number leaves the regular app |
| Cost per message | No charge from Meta | Charge applies, by message category |
| Message initiated by the company | Free text | Only with pre-approved template |
| Risk of blocking | Exists if there is abusive use | Low, as it is an approved path |
| Verification badge | No | Possible, at Meta's discretion |
Neither is "the right choice." They are options for different moments, and most companies start with QR Code and migrate when volume justifies it — discussed in detail in the article about how to choose a WhatsApp CRM.
How it works behind the scenes
Message templates
Every message the company initiates must use a template previously approved by Meta. The template has fixed text and variable fields — name, order number, date. Approval takes minutes to days, and rejections happen due to exaggerated promises, ambiguous text, or wrong category.
The 24-hour window
When the customer writes to the company, a 24-hour window opens during which the conversation flows freely, with free text, no template needed. After this period, only approved templates can be used to resume contact. This rule shapes the entire operation: responding quickly is not just good business practice, it keeps the conversation within the window.
Categories and charges
Messages are divided into categories — marketing, utility (confirmations, order notices), authentication (codes), and customer service (initiated by the customer). Each category has its own treatment and price, and Meta's charging model has changed multiple times over the years. Therefore, do not base your budget on numbers you read in any article — including this one: check Meta's current pricing table for Brazil before finalizing your account.
Sending limits
New API numbers start with a daily limit of initiated contacts, which grows based on history and operation quality. Quality here is measured by how people react: blocks and reports lower the level; conversations with responses sustain it.
Building the cost account
The total cost has three parts, and ignoring any leads to surprises on the bill:
- Monthly fee for the tool providing the customer service interface, funnel, and reports.
- Meta's charges for messages in chargeable categories.
- Possible provider fee that intermediates access, if any — some charge a margin over Meta's price, others do not. Ask explicitly before signing.
Example estimate — the unit values below are hypothetical, just to show how the bill is built. Company with 3,000 monthly customer-initiated conversations, 1,200 scheduling confirmations, and 800 campaign messages:
- 3,000 customer service conversations initiated by customers: currently, this category is usually not charged — confirm with the current table.
- 1,200 utility messages × R$ 0.08 (hypothetical) = R$ 96
- 800 marketing messages × R$ 0.32 (hypothetical) = R$ 256
Message cost in the example: R$ 352 per month, in addition to the tool's monthly fee. Note what the calculation reveals: the weight is on marketing messages. A company that runs many active campaigns feels the difference; one that basically only responds to incoming inquiries hardly notices. Before migrating, classify your volume by category — this is what determines whether the API will be cheap or expensive in your case.
Most common budgeting mistake: comparing the tool's monthly fee with API against the tool's monthly fee with QR Code and concluding "the API is more expensive." The relevant cost is the total, including messages — and on the other side of the account, the cost of having the main number blocked on a peak day.
Continue reading for free
Fill out once and unlock this and all other blog articles. We charge nothing — we just want to know who we are writing for.
It takes 20 seconds. Prefer to talk directly on WhatsApp?
When migrating makes sense
It is not a matter of company size, but usage profile. Migrate when at least two of these are true:
- You send many messages initiated by the company — billing, confirmation, recurring campaigns. This is the highest risk scenario on the unofficial path.
- Losing the number would be serious. If half a day without WhatsApp affects the entire operation, the approved path justifies the cost.
- You need the badge or formal credibility with larger clients.
- The volume of simultaneous conversations is high and stability has become a requirement.
- There is integration with ERP, e-commerce, or order system that requires a stable connection.
And the reverse is also true: if your company basically responds to incoming contacts, with two or three agents and little active messaging, the QR Code solves it — migrating too early only adds cost and rigidity.
How migration works, step by step
- 1. Meta business account. Create or organize the company's Business Manager with data matching the CNPJ.
- 2. Company verification. Submit documents. This step usually delays due to discrepancies between legal name, address, and website information.
- 3. Provider and tool selection. Who intermediates access and where the team will serve.
- 4. Number registration. If the number is already used on the regular app, it must be unlinked — and here lies the sensitive point: the chat history from the app does not migrate. Export critical data beforehand.
- 5. Template creation. Write and submit the templates your operation uses daily before switching, not after.
- 6. Testing and switch. Run in parallel with a test number, train the team on the new interface, and choose a low-traffic day to switch.
Mistakes that cause migration to fail
- Migrating without a defined customer service tool. The number leaves the phone and no one has a proper place to serve. This is the most costly and frequent mistake.
- Not informing the team. Agents looking for chats on the phone feel lost on day one.
- Leaving templates for later. Without approved templates, the company cannot initiate conversations in the first week.
- Ignoring the 24-hour window when designing the process. Teams that take a day to respond end up needing templates for everything — and costs rise unnecessarily.
- Assuming the green badge comes automatically. It is granted at Meta's discretion and depends on brand presence and relevance, not migration.
- Not asking about the provider's margin. Two proposals with the same monthly fee can have very different message costs.
The decision in one sentence
If your company responds more than it initiates, and the number you've used for years works well daily, stay with QR Code and invest effort in organizing customer service. If your company depends on initiating conversations in volume — confirming, billing, notifying, promoting — the official API stops being a luxury and becomes protection: you trade a diffuse risk of blocking for a predictable cost per message.
The best scenario for those growing is to choose a tool that supports both paths. This way, the decision is not final: start with the simpler method and migrate when volume demands it — without changing providers, redoing processes, or losing the conversation base built so far.
Frequently asked questions
What is the official WhatsApp Business API?
It is Meta's approved way for a company to operate a WhatsApp number within its own systems. It is not an app: it has no screen or installation and works as an entry point used by the company's customer service tool. Because of this, the number registered on the API stops working on the regular phone app — all service happens within the system.
How much does it cost to use the official WhatsApp API?
The cost has three parts: the monthly fee for the customer service tool, Meta's charges for chargeable messages, and sometimes a margin from the provider intermediating access. Messages are divided into categories — marketing, utility, authentication, and customer service — with different prices. Since Meta's charging model has changed multiple times, check the current pricing table for Brazil before budgeting, and ask the provider if they add a margin to Meta's price.
Do I need to change my number to use the official API?
No. The number can be kept but must be unlinked from the regular app, where it will stop working. The point of attention is the history: chats on the app do not migrate to the API, so export critical data before switching. Those who cannot be without the number on the phone should consider registering a second number on the API.
What is the 24-hour window?
It is the period that opens when the customer sends a message to the company. Within these 24 hours, the conversation flows with free text. After this period, the company can only resume contact using a message template previously approved by Meta. In practice, this makes response speed a matter of cost, not just service quality.
Does migrating to the API guarantee the green verification badge?
No. Business account verification is granted at Meta's discretion and considers brand presence and relevance, not just API use. Migration makes the company eligible but does not guarantee the badge — treat it as a possible consequence, never the main reason to migrate.
Both paths in the same tool
VeyloCRM connects via QR Code or Meta's official API. Start with the simpler method and migrate when volume demands it — without changing providers or redoing processes.