Is the official WhatsApp API free? What's free and what changed in October
By José Pedro · Co-founder of CRPRO
Access to Meta's Cloud API costs nothing; what's paid is template messages delivered. See what's free, what has been charged per message since October 1, 2026, and why the 72-hour Click-to-WhatsApp window stays free either way.
The official WhatsApp API — Meta's Cloud API — is free to access and paid on the messages the business initiates outside the conversation. Meta doesn't charge a subscription for access, doesn't charge per connected number, and doesn't charge you to create and submit a template. The cost shows up somewhere else. Until September 30, 2026, nearly all inbound support cost zero. Since October 1, 2026, that free tier has shrunk. And one piece of it stays standing: the 72-hour window opened by a Click-to-WhatsApp ad.
Why does the same question have three answers?
Whoever asks if the API is free usually mixes up three different accounts. Split apart, they answer themselves:
| What you're signing up for | Does it have a fee? | Who charges it |
|---|---|---|
| Access to the Cloud API: account, connected number, webhooks, registered templates, quality rating in WhatsApp Manager | No | nobody |
| Template messages delivered to the recipient | Yes | Meta |
| The platform that operates the API: inbox, team, pipeline, campaigns | Yes, a monthly fee | whichever partner you choose |
Since July 1, 2025, Meta's charge is per delivered template message, no longer per conversation. And the raw API is a handful of HTTP requests: with no software on top, you have no inbox, no team, no pipeline, and no campaigns — that third layer is the line that shows up on your bill every month.
Whoever answers "the API is free" is talking about the first row. Whoever answers "it's very expensive" is adding the second and third together. Neither answer stands on its own.
What's free on the official API?
This holds as of October 2026:
| Item | Cost verified as of August 2026 |
|---|---|
| API access, connected number, webhooks | Free |
| Creating and submitting a template for approval | Free (the charge is on delivery, not on registration) |
| Everything inside the 72-hour window opened by a Click-to-WhatsApp ad | Free |
| Quality rating, per-number metrics, ban appeal | Free |
In practice: until September 30, 2026, an inbound operation — the customer reaches out, you reply inside the 24-hour window — paid the platform and almost no fee. That exact setup is what changed on October 1.
What's already paid today: marketing, utility, and the AI agent
| Item | Cost verified as of August 2026 |
|---|---|
| Marketing template (you initiate, outside the window) | ~US$0.0625 per delivered message (~R$0.32) |
| Utility template outside the window | about US$0.0068 per message (~R$0.035) |
| Authentication template | about US$0.0068 per message (~R$0.035) |
| Meta Business Agent (Meta's own AI agent) | US$2.00 per million tokens |
| Platform/partner operating the API | Monthly fee |
Two honest caveats. The marketing rate, US$0.0625 per delivered message (in effect as of August 2026), is the best-corroborated one — use it as your anchor. The utility and authentication ones are "about": good for order of magnitude, not for hanging your whole projection on.
Meta's own agent has been billed per token since August 1, 2026, and Meta's documentation says a message typically consumes 20,000 to 25,000 tokens. At US$2.00 per million tokens, the math lands between 4 and 5 US cents per message — more expensive, per message, than a utility template. Turning it on isn't mandatory.
A table that charges per conversation belongs to a retired model
If you found a table that charges per conversation instead of per delivered message, it belongs to the conversation-based pricing model, retired in July 2025 — its figures no longer apply. The same goes for the monthly quota of free conversations: that was a perk of that model, not of the current one.
The difference isn't cosmetic. Under the old model, one open conversation covered 24 hours of exchange for a single fee; under the current one, what counts is each delivered template. When comparing a vendor's quote, check first what unit is being charged: if the proposal talks about conversations, either the material is outdated or the unit is the vendor's own, not Meta's.
What stopped being free on October 1, 2026?
The change is narrow and specific. Nothing happens to marketing campaigns — they're already paid and stay the same.
| Message type | Through 09/30/2026 | Since 10/01/2026 |
|---|---|---|
| Marketing template outside the window | Paid | Same |
| Utility template outside the window | Paid | Same |
| Utility template inside the 24h window | Free | Charged per message |
| Service message inside the window | Free | Charged per message |
| Message inside Click-to-WhatsApp's 72h window | Free | Stays free |
One detail changes the math for anyone with heavy support volume: service messages get no volume discount. Utility and authentication keep the discount ladder as volume rises; service doesn't. Doubling the number of conversations doubles the cost line, with no relief in the curve.
How much does a service message cost?
The service-message rate is in Meta's current price table. Any article showing an exact price without citing that table is guessing, so check the table.
One good piece of news on the side: since July 1, 2026, billing in Brazilian reais is available, and it becomes mandatory by June 30, 2027. Currency risk is coming off the table — while it still exists, a rate in US dollars like the US$0.0625 marketing template (August 2026) still changes size on your bill depending on that month's exchange rate.
The 72-hour Click-to-WhatsApp window stays free
This is the detail almost nobody mentions, and it changes how you should design campaigns. When a customer arrives through a Click-to-WhatsApp ad (the "Send message" button on Facebook or Instagram that opens the conversation), it opens a 72-hour window, not 24. Everything that happens inside it is free. And unlike the 24-hour window, it wasn't touched by the October 1, 2026 change: it stays free.
The practical effect is that, since October 1, two identical conversations end up with different costs depending on the entry door. Same customer, same topic, same number of messages:
| Entry door | Window opened | Cost of messages since 10/01/2026 |
|---|---|---|
| Click-to-WhatsApp ad | 72 hours | Free; you only pay for the media |
| Website link, Instagram, or a typed-in number | 24 hours | Every service message is a cost line |
What does the free window change in your planning?
Three consequences worth building into the budget.
The source of the contact became a cost variable. If you already run paid media, shifting part of acquisition to Click-to-WhatsApp moves the spend from a per-message fee to CPM, where you already know how to optimize.
A follow-up cadence fits inside the window. Seventy-two hours is enough room for a D0/D+1/D+2 sequence with no template and no fee. Whoever lets the lead go cold until day four pays a template to reopen the conversation.
Opt-in and policy still apply. A free window isn't a license for volume. Contact permission is still a requirement of the official policy, and the number's quality rating is still calculated over the last 7 days, weighted, based on what people do with your messages. Cheap and blocked isn't savings.
And QR code, which has no fee at all?
This is where most content lies by omission. A QR code connection has no per-message fee — not before October 1, 2026, and not after. For a small inbound-support operation with little campaign activity, that's real money saved, and there's no point pretending otherwise. What you pay on QR code simply doesn't show up on the invoice:
| QR code | Official API | |
|---|---|---|
| Per-message fee | None | Per delivered template |
| Visibility | No quality rating, no quality dashboard, no delivery metrics at the API's standard | Per-number quality rating, calculated over the last 7 days, and delivery metrics |
| Due process | The ban can arrive with no warning at all | Meta warns by email before penalizing, gives a deadline to fix it, applies the penalty in stages, and keeps a formal appeal channel |
| Window enforcement | Nothing stops sending outside the window | A free-form message outside the 24-hour window is refused with an error; only a template reopens the conversation |
The official API doesn't eliminate ban risk
Important to be precise here: a number on the official API can be disabled, and Meta even keeps a ban-state field in the account webhook. The difference isn't immunity, it's having a warning, a metric, and a right to respond.
What you're buying with the official API is the ability to see the problem while it's still reversible: the quality rating, calculated over the last 7 days, shows the decline before the account hits the limit, and the email warning arrives before the penalty. Anyone who wants to understand when the QR code math still works out better can find the four concrete cases in when not to migrate to the official API, and the cost-of-risk read in the anti-ban playbook.
How to estimate your cost?
A short roadmap, so you have a number in hand instead of a surprise on the invoice:
- Count messages, not conversations. Tally how many messages your team sends per resolved conversation — the average tends to surprise people.
- Split the volume into three buckets: ones you initiate outside the window (always paid), replies inside the window (free until 09/30/2026, charged per message since 10/01/2026), and conversations coming from Click-to-WhatsApp (free under both rules).
- Measure the back-and-forth. Every message shaved off per conversation is direct savings. Ready-made replies and a first contact that already asks for the right information cut more than any rate negotiation ever will.
- Check Meta's current price table and only then finalize your projection.
CRPRO operates both the official API and the QR code connection: you can start with whichever path makes sense for your volume and switch later, without changing tools. Pricing is on the plans page.
Frequently Asked Questions
Is the official WhatsApp API free?
Access is. Meta doesn't charge a subscription for the API, for the connected number, or for creating templates. What's charged are delivered template messages and, if you sign up for one, the platform that operates the API.
Do I have to pay to create and get a template approved?
No. Submitting a template for approval generates no fee. The charge happens when the message is delivered to the recipient.
What exactly has been charged since October 1, 2026?
Service messages and utility templates sent inside the 24-hour window, which were free until September 30, 2026. Marketing campaigns and templates outside the window are already paid and don't change.
How much does a service message cost?
The rate is in Meta's current price table. Anyone quoting an exact figure without citing that table is estimating without a source.
How much does Meta's AI agent cost per message?
The Meta Business Agent has been billed at US$2.00 per million tokens since August 1, 2026. Since a message typically consumes 20,000 to 25,000 tokens, according to Meta's documentation, the cost lands between 4 and 5 US cents per message. It's optional: nothing requires you to turn the agent on.
Is the Click-to-WhatsApp 72-hour window also charged?
No. It wasn't touched by the October 1 change: messages exchanged inside those 72 hours stay free.
Does using the official API prevent my number from getting banned?
It doesn't. The difference is the process: you track the number's quality rating, calculated over the last 7 days, get an email warning with a deadline to fix things, face a penalty applied in stages, and can formally appeal. On the regular app, the ban can arrive with no warning.