The risk is not the software.It is the number.
Unofficial WhatsApp APIs work by signing in as a linked device and automating the WhatsApp Web session. That is what WhatsApp's terms prohibit, and it is the number that pays for it, not the tool. The official Cloud API does the same work through an interface Meta supports.
What an unofficial WhatsApp API actually is
Whatever the marketing says, they all do the same thing underneath. Knowing the mechanism is what makes the rest of this page obvious.
- 1It opens the WhatsApp Web protocolThe same one the browser client speaks. Nothing about it is a private API or a special integration.
- 2It pairs itself as a linked deviceYou scan a code, exactly as you would to use WhatsApp in a browser. From then on the library holds that session.
- 3It drives the session programmaticallyMessages are read off the socket and pushed back through it. This is why it installs in minutes and needs no account, review or approval.
- 4The session lives on your serverThose credentials are full account access, and they are a known target. There is nothing equivalent to revoke.
What the terms say, and why anti-ban claims cannot work
WhatsApp's terms prohibit automated and bulk use of the consumer client. A linked device is the consumer client, so the prohibition covers the mechanism itself rather than any particular library.
That is the part worth sitting with. A tool advertising anti-ban protection is claiming to control something outside of it, because what is prohibited is not the code sending the message. Rewriting the library, rotating the session or slowing the sends changes the implementation, not the category.
It is also why months of uptime is not evidence of safety. It is evidence that nothing has happened yet, which is a different statement and a much weaker one.
What it costs when it goes wrong
The failure is not that automation stops. It is that the number stops, and for most businesses the number is closer to a phone line than to a piece of software.
Every conversation on that number becomes unreachable, and the people in them are told nothing. They simply stop getting replies.
Vans, storefronts, cards, invoices, a website, years of past messages. None of that can be recalled.
Threads, and the contact list that only existed inside them.
One that was never told this was the mechanism underneath what they bought.
What the official route actually costs you
This is the honest part, and it is short. The official API is more restricted, and the restrictions are real rather than something a provider can lift.
Outside 24 hours from the customer's last message, only a template Meta has approved will deliver.
Anything that opens a conversation is submitted to Meta first. Usually minutes, sometimes a day.
Not available through the API on a Coexistence number, on any provider.
In exchange the number cannot be banned for the mechanism, because the mechanism is the one Meta publishes.
Moving off one without losing the number
The objection to the official API used to be real: it meant migrating the number, which killed the WhatsApp Business app on it. Coexistence removed that, so the move is smaller than most people expect.
- 1Stop the unofficial sessionLog the linked device out from the phone. The number itself is untouched by this.
- 2Connect through Meta's own flowEmbedded Signup, then a code scanned in the WhatsApp Business app. Two to three minutes, and the app keeps working.
- 3Point the webhook at what you already builtYour existing handler mostly survives. What changes is the payload shape and that delivery now comes from Meta directly.
- 4Rebuild anything that used groupsThis is the one genuine rewrite, and it is worth knowing before you start rather than after.
Official Cloud API throughput on a Coexistence number, set and guaranteed by Meta.
How long a customer reply keeps free text sending open on the official API.
Credentials the official route holds on your server, because there is no session to pair.
Frequently asked questions
Is my number already at risk if I use one of these?
The exposure exists for as long as the session is running. Nothing triggers at a fixed date, which is why a long run of uptime is not reassuring. Moving to the official API on the same number is possible without losing the app.
Can I move to the official API without changing my number?
Yes. Coexistence connects the number you already use, and the WhatsApp Business app keeps working on the phone throughout. Nothing migrates.
What can the official API not do?
Group chats are excluded on Coexistence numbers. Free text only works within 24 hours of the customer's last message, and outside that window messages must use a template Meta has approved.
Does the official route cost more?
Meta charges its own messaging fees either way, billed to you directly. The difference is a flat monthly fee per number rather than the risk of losing the number.
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free Trial7 days free. Nothing is charged until the trial ends.