Official vs. Unofficial WhatsApp API: A 2026 Business Guide

Anyone researching official vs. unofficial WhatsApp API almost always faces the same choice: a tool that connects your number by scanning a QR code, cheap and ready in minutes, or Meta's Cloud API, which requires verification and charges per message. This comparison reveals the underlying differences, where the risks lie, and when each path makes sense.

TL;DR

• Official API is the WhatsApp Business Platform (Cloud API), operated by Meta itself. The business is verified, active messages use approved templates, and there is no risk of being blocked for using the integration.
• Unofficial API is any solution that connects your number via the WhatsApp Web protocol, by scanning a QR code: Z-API, uazapi, WPPConnect, Baileys, and the WhatsApp Web mode of Evolution API.
• The unofficial option is cheaper and quicker to set up, but Meta does not authorize this use. Your number can be restricted or banned, and the integration breaks when WhatsApp Web changes.
• For customer service, sales, and billing in an operation that cannot afford downtime, the official API is the choice. The unofficial API is only viable for testing, personal use, or very low volumes, accepting the risk of losing the number.

What is the Official WhatsApp API?

The official API is the WhatsApp Business Platform, currently served by the Cloud API hosted by Meta. A business connects a number to a WhatsApp Business Account (WABA) within Business Manager, undergoes verification, and uses the API documented by Meta itself. The complete guide is available at WhatsApp Cloud API: The Complete Official API Guide.

The practical rules are:

1. Messages initiated by the business use approved templates (marketing, utility, or authentication).
2. When a customer writes, a 24-hour window opens for free-form responses.
3. Meta charges per message delivered. As of October 1, 2026, service messages are also charged, with 1,000 free per number per month. The values in Brazilian Reais are detailed in service messages: billing has begun.

You don't need to abandon your cell phone: the coexistence mode allows you to use both the WhatsApp Business app and the official API with the same number.

What is an Unofficial WhatsApp API?

An unofficial API does not communicate with Meta as an integrator. It opens a WhatsApp Web session, as if it were another browser connected to your number, and transforms that session into an HTTP API. This is why the connection is made by scanning a QR code.

These include:

• Z-API and uazapi: commercial services that connect your number via QR code.
• WPPConnect and Baileys: open-source libraries that implement the WhatsApp Web protocol.
• Evolution API: an open-source project with two modes. The WhatsApp Web-based mode (Baileys) is unofficial; the mode connected to the Cloud API uses Meta's official API.

The question "Is Z-API official?" has a direct answer: no. Connecting via QR code is the simplest sign that the integration does not go through the official platform.

Side-by-Side Comparison

Criterion	Official API (Cloud API)	Unofficial API (QR code)
Operator	Meta	Tool provider, built on WhatsApp Web
Meta Authorization	Yes	No
Connection Method	Number linked to a verified WABA	QR code scan
Integration Blocking Risk	None	Exists and increases with volume and broadcasts
Stability	Does not depend on WhatsApp Web	Fails when WhatsApp Web changes or phone disconnects
Active Messages	Approved templates	Free text, uncontrolled
Message Cost	Charged by Meta, per message	No Meta charges
Buttons, Lists, and Flows	Official features	Limited or unstable
Verified Badge and Name	Available	No
Multi-agent and Multiple Integrations	Yes, without relying on a cell phone	Depends on active session

Where the Real Risk Lies

The risk of an unofficial API is not theoretical. The WhatsApp Web session was not designed for automation, and WhatsApp's terms do not authorize automated access by unofficial clients. In practice, three things happen:

1. Number blocking. High-volume broadcasts, instant serial responses, and many new contacts are precisely the patterns Meta looks for. We detail this in Blocked WhatsApp: The Official API is the Only Solution.
2. Silent downtime. A WhatsApp Web update or a dead cell phone battery can drop the session, and your bot stops responding without warning.
3. No recourse. If your number goes down, there's no Meta support to request a review for an integration it doesn't recognize.

The message cost that the unofficial API "saves" is usually less than the cost of a day of halted customer service or losing the number listed on your business cards, Google, and advertisements.

How Much Does Each Cost?

With the unofficial API, you pay the tool's monthly fee and nothing to Meta. With the official API, there are two costs:

• Platform (the tool that provides the inbox, chatbot, and reports).
• Meta's message fees, charged per message delivered. In Brazil, the reference is approximately R$ 0.32 for a marketing message and R$ 0.035 for a utility, authentication, or service message (with 1,000 free per number per month for these categories).

The point of attention is the markup: many platforms resell Meta's messages with a margin. It's worth asking if the price passed on is Meta's official rate. We explain how to identify this in markup on WhatsApp messages.

When Each Option Makes Sense

The unofficial API might be suitable when:

• it's for a test or prototype;
• the number is disposable and not tied to your brand;
• the volume is low, and losing the number won't halt your business.

The official API is the choice when:

• the number is your sales, customer service, or billing channel;
• you run ads that direct to WhatsApp;
• more than one person is handling inquiries;
• you need reliable templates, buttons, and reports;
• data privacy (like CCPA or other US state privacy laws) and auditing are important.

How to Migrate from Unofficial to Official

1. Disconnect the WhatsApp Web session from the unofficial tool.
2. Choose between migrating your number to the API or using coexistence mode and keeping the app on your phone.
3. Create or verify your Meta Business Manager and WhatsApp Business account.
4. Register and get approval for the templates you previously used as free text.
5. Reconfigure your chatbot, queues, and integrations on the official platform.

For SMB operations, the process typically takes 5 to 7 business days, with most of that time spent waiting for verification and template approval.

How Agathas Web Solves This

Agathas Web's Voyia is the platform for the official WhatsApp API: a multi-agent inbox, chatbot, segmented broadcasts with approved templates, AI integration using your own key, and reports. Meta's fees are passed on without markup, in Brazilian Reais, and coexistence mode is supported.

Plans start at R$ 149 per month per number, with no long-term commitment. The complete table, detailing what's included in each plan, is on the Voyia page. If you currently use an unofficial API and want to migrate without losing your number, our team will assist you with the migration.

Conclusion

The choice between an official and unofficial WhatsApp API is a choice between low cost with risk and predictable cost with security. For any number that supports sales or customer service, the risk of blocking with the unofficial API outweighs the message savings. If WhatsApp is already a revenue channel, the path forward is the official API with Voyia.