The official WhatsApp Cloud API is the formally supported route: an approved dedicated number, pre-approved templates, and billing per delivered message. The unofficial API connects through your own number by QR code, is live in minutes, and runs flat-rate — with no Meta support and a ban risk you have to manage.

Which is right depends on four things: volume, budget, how fast you need to ship, and how much risk you can carry. Here is each criterion side by side, then a decision table.

Side by side

Choose official when

• You operate at high volume and need a formal guarantee behind it.
• You want the verified badge and an official brand presence.
• You are in a regulated industry with strict compliance requirements.
• Losing the number would be unacceptable, not merely inconvenient.

The approval process and the per-message bill are what you pay for that robustness. Both are real costs, and for a serious operation both are usually worth it.

Choose unofficial when

• You want to start now, with no approval queue and no template review.
• You want predictable cost — a subscription, not a meter.
• You need full flexibility in what a message contains.
• You are automating support and opt-in notifications for people who already know you.

This is the usual path for validating a product, automating support, or notifying customers who asked to be notified.

Quick decision table

About that ban risk

It deserves a straight answer rather than a disclaimer. The risk is real and manageable, and it comes from how you send, not from the technology.

What triggers bans: bulk sending to people who never opted in, byte-identical message bodies fired at machine speed, and a cold number that jumps to high volume overnight.

What keeps a number stable: opt-in lists, personalized content, pacing that resembles a human, and warming a new number gradually. Teams doing that run unofficial numbers for years.

What it cannot give you: a guarantee. If your business would be materially damaged by losing a number for a week, that is the argument for official — not the price.

Running both

These are not mutually exclusive, and treating them as a permanent either/or is the most common mistake. A common shape:

• Official instance for marketing campaigns and anything that needs the badge or a template.
• Unofficial instance for support and internal alerts, where volume is high, content is free-form, and per-message billing would be paying a premium for nothing.

WAME runs both on the same platform, chosen per instance, behind the same SDK and the same webhook format — which is what makes running both practical rather than a second integration.

Next

• WhatsApp API pricing — exactly what Meta bills and what is free
• WhatsApp API endpoints — the surface you would build against
• Documentation — every endpoint and parameter

Frequently asked questions

What is the difference between the official and unofficial WhatsApp API?+

The official WhatsApp Cloud API is Meta's own product: it needs registration and approval, runs on a dedicated number, requires pre-approved templates to message anyone outside the 24-hour service window, and is billed per delivered template message. The unofficial API connects through your existing number by QR code, the way WhatsApp Web does, starts in minutes, imposes no template approval, and normally costs a flat monthly fee. It has no Meta support and carries a ban risk.

Is the official WhatsApp API free?+

No. Since July 1, 2025 Meta bills per delivered template message, with rates that vary by category and by the recipient's country. Service messages — your replies inside the 24-hour window a customer opens by messaging you — are free, and so are the first 72 hours of conversations that start from a Click-to-WhatsApp ad. But the model overall is pay per use.

Which WhatsApp API is cheaper?+

For small and mid volume, and for anything text-heavy, the unofficial API is usually cheaper because it is a flat subscription rather than per-message billing. At very high volume with mostly Utility-category traffic, Meta's volume discounts narrow the gap, so it is worth modelling both against your actual message mix.

How real is the ban risk on the unofficial API?+

Real, and driven by sending behaviour rather than by the technology. Bans follow bulk sending to people who never opted in, identical message bodies at machine speed, and sudden volume spikes from a cold number. Sending to opted-in contacts, personalizing content and pacing to a human rhythm keeps stability high. It is a risk you manage, not one you eliminate.

Which one should I choose?+

Choose official when you need a formal guarantee from Meta, a verified business badge, regulated-industry compliance, or you operate at a volume where losing a number would be unacceptable. Choose unofficial when you want to start immediately with predictable cost and full flexibility for support and opt-in notifications. Many teams run both, on separate instances, for different jobs.

Keep reading

wa.me links explained: click to chat on WhatsApp, with a generator

wa.me is WhatsApp's official click-to-chat shortener. Build a link with https://wa.me/<number in international format, digits only>, prefill a message with ?text=, and open a chat without anyone saving a contact. Includes a live generator and the wa.me/message and wa.me/c variants.

WhatsApp API endpoints: the reference you can hold in your head

The WAME WhatsApp API uses https://us.api-wa.me with the pattern /{key}/... where {key} is your instance key and doubles as authentication — no auth header. Endpoints group into instance, messages, groups, contacts and webhooks. Full list with curl examples.

WhatsApp API pricing: what Meta actually charges you for

Meta bills the WhatsApp Cloud API per delivered template message, not per 24-hour conversation — that changed on July 1, 2025. Marketing, Utility and Authentication are paid; Service replies inside the customer's 24-hour window are free. Rates vary by recipient country.