Official vs. Unofficial WhatsApp API: A UK Business Guide (2026)

Businesses researching official vs. unofficial WhatsApp API solutions almost always face the same choice: a tool that connects a number by scanning a QR code, which is inexpensive and ready in minutes, or Meta's Cloud API, which requires verification and charges per message. This comparison shows what changes under the hood, where the risk lies, and when each approach makes sense.

TL;DR

• The official API is the WhatsApp Business Platform (Cloud API), operated by Meta itself. The business is verified, proactive messages use approved templates, and there is no risk of being blocked for using the integration.
• The unofficial API is any solution that connects the 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 API is cheaper and quicker to set up, but Meta does not authorise this use. The number can be restricted or banned, and the integration breaks when WhatsApp Web changes.
• For customer service, sales, and billing operations 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 Meta-hosted Cloud API. The 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: complete guide to the official API.

The rules that apply in practice:

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

You don't need to give up your mobile phone: the coexistence mode allows you to use the WhatsApp Business app and the official API on 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 this session into an HTTP API. This is why the connection is made by scanning a QR code.

These types include:

• Z-API and uazapi: commercial services that connect the 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 Authorisation	Yes	No
Connection Method	Number linked to a verified WABA	QR code scan
Blocking Risk from Integration	None	Exists and increases with volume and broadcasts
Stability	Does not depend on WhatsApp Web	Breaks when WhatsApp Web changes or mobile disconnects
Proactive Messages	Approved templates	Free-form 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 mobile 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 authorise automated access by unofficial clients. In practice, three things happen:

1. Number Blocking. High-volume broadcasts, rapid-fire instant replies, and numerous new contacts are precisely the patterns Meta looks for. We detail this in WhatsApp blocked: the official API is the only solution.
2. Silent Downtime. A WhatsApp Web update or a mobile phone with a flat battery drops the session, and the bot stops responding without warning.
3. No Recourse. If the number goes down, there's no Meta support to request a review for an integration it doesn't recognise.

The message cost savings from an unofficial API are usually less than the cost of a day of halted customer service or losing the number featured on business cards, Google, and advertisements.

How Much Does Each Cost?

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

• Platform (the tool that provides the inbox, chatbot, and reports).
• Meta Messages, charged per delivered message. 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 the latter).

The key point to note is markup: many platforms resell Meta's messages with a margin. It's worth asking if the price passed on is Meta's standard 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 a test or prototype;
• the number is disposable and not linked to your brand;
• the volume is low, and losing the number wouldn't halt your business.

The official API is the choice when:

• the number is your primary channel for sales, customer service, or billing;
• you run adverts that direct to WhatsApp;
• more than one person is handling enquiries;
• you require reliable templates, buttons, and reports;
• UK GDPR (Data Protection Act 2018) 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 the number to the API or using coexistence mode and keeping the app on your mobile 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-form text.
5. Reconfigure your chatbot, queues, and integrations on the official platform.

For SME operations, the process typically takes 5 to 7 business days, most of which is spent waiting for verification and template approval.

How Agathas Web Can Help

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

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

Conclusion

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