Official vs unofficial WhatsApp API: what actually changes

The difference between the official WhatsApp API and an unofficial library is not code quality: it is authorisation. The official one is Meta’s Cloud API, where automating is the intended use and every conversation you start is billed. The unofficial one automates WhatsApp Web, is free and requires approval for nothing — and it violates the terms, which exposes the number to a block with no warning and no reliable appeal.

The comparison below goes criterion by criterion and includes the two lines where the unofficial route wins. A comparison where one side takes everything is not a comparison.

Time to first message

A tie, with one caveat. The unofficial route is up in minutes: install, scan the QR code, send. The official API contracted directly with Meta takes weeks to months; through a provider that already cleared the paperwork, also minutes.

Cost per message

The unofficial route wins, by a wide margin. It charges nothing per message. On the official API, Meta bills every template you initiate, priced by category and country. For high notification volume, the difference is orders of magnitude.

It is the most honest line in this comparison, and the reason budget-constrained projects choose the unofficial route with good reason.

Block risk

Here the gap is the widest of all. Automating WhatsApp Web violates the terms on its own — regardless of what you send. The block arrives with no warning, and the remedy is a review request with no timeline and no guarantee.

On the official API there is no ban for automating: Meta knows software is on the other side. What exists is the number’s quality rating, which drops when too many people block or report — and that applies to both routes.

Stability

The unofficial route depends on a WhatsApp Web session. It breaks when the app updates, when the server restarts, and when Meta changes something on their side — with no notice and no changelog.

This is not hypothetical: we ran a cluster of unofficial instances for years. In one reboot of two servers, 41 instances went into reconnecting and never came back on their own — and nobody noticed that day, because the failure is silent: the service stays up, answering, without a session. That is what moved our customers to the Cloud API.

A WhatsApp Web session does not survive a reboot. You find that out the day you need to restart the server — or the day it restarts by itself.

What you can send

• Unofficial — text and media to any number, with no approval, including groups.
• Official — text, media, interactive messages, location, contacts and reactions; an approved template to start a conversation; and no group support at all.

Groups are the one capability where the unofficial route does something the official API does not and will not: there is no group endpoint in the Cloud API. Anyone depending on groups needs to know that before deciding.

Content approval

On the unofficial route it does not exist. You write and you send. On the official API, every message that starts with you is a template reviewed by Meta, with a category and writing rules.

That is a real process cost — and it is also what stops your customer base receiving, on the same channel, whatever a desperate company would blast out.

Who answers when it breaks

• Unofficial — the project community. No SLA, no channel, nobody to escalate to.
• Official — the provider, and Meta behind them. Somebody is contractually responsible.

The summary, by profile

1. Prototype, internal use, low volume, disposable number: the unofficial route is hard to argue against.
2. A store notifying customers on the same number it supports them on: official, because the number that falls is the business.
3. An operation that depends on groups: neither solves it well; the unofficial route solves it with risk.
4. High notification volume on a tight budget: run the official API arithmetic first, because it may not close.

Anyone who has decided to migrate will find the walkthrough, including keeping the same number, in migrating to the official WhatsApp API.

Frequently asked questions

Is an unofficial WhatsApp API illegal?

It is not a crime; it is a breach of the platform’s terms. The consequence is not legal, it is operational: the number gets blocked, with no warning and no appeal timeline.

Is using an unofficial API only to receive messages safe?

It is the same mechanism. What constitutes the breach is automating WhatsApp Web, not the direction of the message.

Can I use both at once?

Not on the same number: a number is registered in one place only. On different numbers, yes — and that is the design used by people migrating gradually.

Is the official API slower to send?

No. The latency difference is irrelevant for notifications; what caps volume is the number’s sending tier, which rises as quality holds.