A QR tool or a phone feels cheap until the number is held (banned) and you lose the chat by swapping numbers. Official Meta Cloud API is not that unofficial route.

Official vs unofficial WhatsApp API: why numbers get banned

Sending from a phone, or from a tool that asks for a WhatsApp Web QR, feels cheap up front. Many owners only see the risk when the number is held (banned): you swap numbers, lose the thread, and start over.

People call both a “WhatsApp API”. The routes are not the same.

Official Cloud API and unofficial routes

Cloud API / WhatsApp Business Platform sends messages through Meta. The number sits on a WABA (the WhatsApp Business Account on Meta’s side), and you connect with Embedded Signup or a Tech Provider. Templates, policy, and conversation rates are Meta’s.

Unofficial routes usually ride a WhatsApp Web session, an emulator, or a phone left on. The fee is often flat and cheap at first, but Meta does not treat this as Business Platform. Sessions drop, limits show up overnight, numbers get banned, and chats live on someone else’s box.

If a vendor cannot show a WABA, a phone_number_id, and Graph webhooks, it is almost certainly not Cloud API.

How it compares on a customer-care desk

Aspect	Official Cloud API	Unofficial
Number	Stays on your business WABA	Easy to “move phones”, and easy to lose
Broadcast	Meta-approved templates	Often free-text blasts (against policy)
Team inbox	Several people, assignment, logs	Usually one phone or one session
Cost	Platform plan + Meta conversation charges on the WABA	Cheap flat fee; Meta’s bill often skipped
Bans	Still possible if the copy breaks policy	Web or phone sessions die much faster

Official is not a spam pass. Forced templates, dirty lists, or misleading copy can still get a number held (banned) by Meta. What changes: you follow Meta’s written rules, not a QR loophole.

When a QR scan or a phone is still fine

Testing ten of your own numbers, or a shop that does not need several agents yet, is reasonable.

It usually breaks when volume grows, shifts rotate, or a complaint needs a log, and the Web session dies at peak hour.

Where Wapedia sits

The Wapedia inbox and API run on WhatsApp Cloud API. Numbers connect through Embedded Signup. You get inbox, template campaigns, a keyword chatbot, and webhooks.

Wapedia is a Meta Tech Provider: software that connects your shop to Cloud API. WhatsApp conversation charges come from Meta to your WABA; the Wapedia plan covers the inbox and platform features. This is not mass-sending via QR or a phone, and it is not WhatsApp Calling.

Myth: “Customer care stays free forever.” Reality: the platform subscription is separate from Meta conversation rates. Details: Cloud API costs.

Connect a number: how to connect. Public signup is closed. Early access via pricing or halo@wapedia.id. API docs: quickstart.