Official vs unofficial WhatsApp API: which one to use and when

Updated in August 2026. We review Meta’s tariffs and rules at the official source before every update to this post.

The short answer: use the official API when WhatsApp carries your sales operation and you send messages at scale. Use the unofficial API (QR code connection) to test automation, run small operations or handle secondary numbers, accepting the risk of a ban.

Our position here is different from most comparisons. NicoChat offers both modes on the same platform: Meta’s official Cloud API and the QR code connection through NicoZap. We do not need to demonize either side in order to sell the other. This guide shows what each mode delivers, how much it costs and which one to choose in your case.

A note on scope: the tariff figures in this post come from Meta’s rate card for Brazil, in reais. The rules apply worldwide, but the amounts change by country, so check the rate card for your own market.

Quick summary

The official API (WhatsApp Business Platform, through the Cloud API) is the route authorized by Meta: stable, with no ban risk from the connection itself, and mandatory for mass sending

The unofficial API connects by QR code, like an automated WhatsApp Web. It is fast to activate and has no per message cost, but Meta can ban the number

Since July 1, 2025, Meta charges the official API per delivered template message, with a tariff per category. The Brazilian tariffs are in the comparison table in this post

Replies inside the 24 hour window opened by the customer remain free on the official API until October 1, 2026

You can start with QR code and migrate to the official API later. At NicoChat, the two modes coexist on the same platform

the complete guide to WhatsApp customer service automation

What changed in 2026

Two Meta changes alter the math of this comparison. If you read an earlier version of this post, update your numbers.

1. Charging per delivered message. Since July 1, 2025, the official API no longer charges per 24 hour conversation. Each delivered template message is charged individually, according to its category (Meta’s official pricing page, consulted in August 2026). A message that does not reach the recipient is not charged.

2. Tariffs in Brazilian reais. Since July 1, 2026, Meta bills Brazilian accounts in BRL, per WABA account and subject to opt in. The official rate card in reais (CSV, in force since July 1, 2026, on Meta’s pricing page) sets the following for Brazil: marketing R$0.3217, utility R$0.0350 and authentication R$0.0350 per delivered message. If you operate outside Brazil, the billing currency and the amounts are different; the structure of the categories is the same.

A third change is coming: starting October 1, 2026, Meta will also charge for service messages, which are free today inside the 24 hour window. Until then, replying to a customer who messaged you first remains free on the official API.

Meta will start charging for WhatsApp service messages: what changes

What the WhatsApp API is

API stands for “application programming interface”. It is the technical channel that lets you connect WhatsApp to other systems: automation platforms, CRMs and customer service tools.

Without an API, WhatsApp is operated by hand, in the app. With an API, a platform like NicoChat can answer customers 24/7, distribute conversations among agents and run campaigns. For small and midsize businesses (SMBs) that lose sales outside business hours, this connection is what changes the game.

There are two paths to that connection. And this is where the confusion starts.

What the official WhatsApp API is

The official API is the WhatsApp Business Platform, maintained by Meta itself. Since October 23, 2025, it exists only in its cloud version (Cloud API): the old on premises API was shut down (official Meta documentation).

In practice, your company creates a WABA (WhatsApp Business Account), verifies the business and connects the number to the automation platform. Meta authorizes, documents and supports this path.

Advantages of the official API

No ban risk from the connection. The number operates inside Meta’s rules. A ban only happens through a content policy violation, such as spam reported by users.
Authorized mass sending. Marketing campaigns, reminders and notifications at scale exist officially only here, through approved templates.
Stability. The Cloud API is Meta infrastructure, with high availability. It does not depend on a phone being switched on or on a browser session.
Exclusive features. Eligibility for the verification badge, interactive buttons, lists, catalogs and WhatsApp Flows (native forms inside the chat).
Predictable, auditable cost. A public tariff per delivered message, now in reais for Brazilian accounts.

Limitations of the official API

Cost per message. Every delivered marketing template has its own tariff, detailed in the comparison table below. At high volume, that weighs on the budget.
Onboarding process. Business verification, template approval and initial setup take more time than scanning a QR code.
Approved templates to start conversations. Outside the 24 hour window, you can only send message templates pre approved by Meta.
Dedicated number. The number connected to the Cloud API does not work at the same time in the regular phone app.

how much the official WhatsApp API costs in 2026

What the unofficial WhatsApp API is

The unofficial API is not a Meta product. These are technologies that automate WhatsApp through WhatsApp Web: you scan a QR code and the platform starts operating that number’s session.

At NicoChat, this mode is called NicoZap. The instance is managed inside the platform, with connection and status visible, and the automation flows run on top of it.

It is important to be honest here: this path operates outside WhatsApp’s terms of service. It is popular in Brazil because it solves real problems for people who are starting out. But the risks are equally real, and you need to know them before you decide.

Advantages of the unofficial API

Activation in minutes. Scan the QR code, connected. No business verification, no template approval.
No cost per message. You only pay for the platform plan. There is no Meta tariff per template.
Freedom of format. Any message, at any time, with no dependency on an approved template.
The number stays on the phone. The session is mirrored, as in WhatsApp Web. The app keeps working.

Real risks of the unofficial API

Number ban. Meta detects and can ban numbers automated through unauthorized routes. Mass sending multiplies that risk. Whoever uses QR code for spam tends to lose the number fast.
Instability. WhatsApp updates can drop the connection without warning. The session has to be reconnected and messages can be lost in the meantime.
No Meta support. A number banned for unofficial automation rarely comes back. There is no official appeal channel for that case.
No official features. No verification badge, no templates, no native catalog, no WhatsApp Flows.

Official vs unofficial API: side by side

Comparison from August 2026. Meta rules and tariffs can change; always check the official source on the date of your decision.

Criterion	Official API (Cloud API)	Unofficial API (QR code)
Meta authorization	Yes, an authorized and documented route	No, outside the terms of service
Activation	Business verification + setup	Minutes, by scanning a QR code
Cost per message	Marketing R$0.3217 / utility R$0.0350 per delivered message (Meta, BRL rate card for Brazil, July 2026)	No tariff per message
Reply inside the 24h window	Free until October 1, 2026	Always free of tariff
Ban risk	Low (only for content violations)	Real and unpredictable
Mass sending	Authorized, through approved templates	Not recommended, high ban risk
Stability	Meta infrastructure	Depends on the session; can drop on updates
Verified badge, templates, Flows	Yes	No
Number in the phone app	No (dedicated number)	Yes (mirrored session)
Ideal for	Sales operations, scale, campaigns	Testing, small operations, secondary numbers

When to use each one

There is no single answer. There is the stage your operation is in.

Use the official API when

WhatsApp carries your revenue. If losing the number means losing sales, the QR code risk is not worth it. A clinic with a full schedule on WhatsApp cannot wake up to a banned number.
You send at scale. Marketing campaigns, payment reminders and order notifications at volume require the official API. It is the only authorized route for that.
You want the badge and the native features. Verification, catalog, buttons and in chat forms exist only on the official API.
You need predictable cost. A public tariff, charged per delivered message, goes into the spreadsheet without surprises.

The cost is less frightening than it looks. A utility message costs around 9 times less than a marketing one. And replying to a customer who messaged you first, inside the 24 hour window, remains free until October 1, 2026.

the WhatsApp 24 hour service window: how it works

One detail few people take advantage of: click to WhatsApp ads open a 72 hour window in which every send is free (Free Entry Point, Meta’s pricing documentation, consulted in August 2026). Free conversation still follows the 24 hour window; a customer who goes quiet for a day receives a template, free within those 72 hours. Anyone running paid traffic to WhatsApp practically zeroes out the message cost of the post click.

click to WhatsApp: how to automate what happens after the ad click

Use the unofficial API (QR code) when

You are testing automation. Before investing in verification and templates, validate the flow with real customers on a test number.
The operation is small and reactive. If the customer always messages first and volume is low, QR code serves well with lower risk.
You need a secondary number. Groups, internal notices or a parallel channel that does not compromise the main operation.
The budget is tight. With no tariff per message, the cost is only the platform plan.

The rule of responsible use: on QR code, do not run mass sends to cold lists. That is the behavior Meta punishes most. Reactive service and automation of customer initiated conversations carry much lower risk, though never zero.

How NicoChat works with both modes

NicoChat connects the official Cloud API and WhatsApp by QR code (NicoZap) on the same platform. The same flow builder, the same AI agents and the same service panel work in both modes.

That changes the decision in practice:

Start where it makes sense. Many customers validate automation on NicoZap within days, with no bureaucracy.
Migrate without starting over. When the operation grows, you connect an official channel and reuse flows, contacts and the work history on the platform. The migration becomes a channel swap, not a new project.
Use both at once. A common setup among our customers: the official number for campaigns and main customer service, the QR code number for secondary functions.

On official API sending, NicoChat passes Meta’s tariff through at cost price, with no markup on the message. You pay the platform plan and the official tariff, nothing more.

FAQ: common questions

Can I use the official API number on my phone?

No. The number connected to the Cloud API is dedicated: it stops working in the regular app. Customer service moves to the platform, where the whole team works together.

Does the unofficial API let me keep using the WhatsApp app?

Yes. The QR code connection mirrors the session, like WhatsApp Web. The phone app keeps working normally.

Which API is safer?

The official one, no argument. It operates inside Meta’s rules, and the ban risk comes down to content violations. On QR code, the risk of losing the number is always there, even with moderate use.

Does NicoChat force you to use a specific API?

No. The platform supports both modes, including at the same time. The choice is yours, and this guide exists so you can decide based on your case, not on our interest.

Can I migrate from unofficial to official without losing data?

On the same platform, yes. At NicoChat, flows, contacts, tags and automations are reused when you connect the official channel. Conversation history from the app does not migrate to the API, a limitation from Meta itself.

Is the official API much more expensive?

It depends on your message mix. Replying to customers inside the 24 hour window is free until October 1, 2026. Utility costs a fraction of the marketing price; the Brazilian tariffs are in the comparison table in this post. Whoever sends little marketing spends little. Whoever sends a lot would need the official API anyway.

how much it costs to send 1,000 WhatsApp messages

Can I automate everything with both?

Almost everything. Flows, AI agents, human handoff and integrations work in both NicoChat modes. Native Meta features, such as approved templates, catalog and WhatsApp Flows, exist only on the official API.

Conclusion: the criterion is your stage, not your team colors

The honest comparison ends like this: the official API is the destination of every operation that takes WhatsApp seriously. The unofficial one is a valid entry door, as long as you know the risks and do not use it for mass sending.

Our practical advice: if WhatsApp is already your revenue channel, go official now. If you are validating, start with QR code and migrate when the operation proves its value. In both cases, pick a platform that does not lock you into a single mode.

Want to test both paths in practice? NicoChat offers a 7 day free trial, no credit card, with the official Cloud API and NicoZap in the same account. Connect, build your first flow and decide with real data.