Choosing an API
Official vs. Unofficial WhatsApp API
'WhatsApp API' covers two structurally different products: Meta's official WhatsApp Business Platform, and unofficial APIs — Wasaas among them — that connect a regular WhatsApp number the way WhatsApp Web does. Neither is universally better. They fit different situations.
The two models, plainly
| Field | Type | Required | Notes |
|---|---|---|---|
| Connection | Official | No | Meta Business account, app review, a phone number registered to WhatsApp's Business Platform. No personal WhatsApp app involved. |
| Connection | Unofficial (Wasaas) | No | Scan a QR code from a regular WhatsApp number, the same mechanism as WhatsApp Web's Linked Devices. |
| Onboarding | Official | No | Business verification and app review — commonly days to weeks. |
| Onboarding | Unofficial (Wasaas) | No | Minutes — no verification queue. |
| Governing terms | Official | No | Meta's Business Platform terms; message-based pricing set by Meta. |
| Governing terms | Unofficial (Wasaas) | No | WhatsApp's ordinary consumer terms — the same automated spam enforcement any personal number is subject to. |
| Official support/SLA | Official | No | Backed by Meta's own platform guarantees. |
| Official support/SLA | Unofficial (Wasaas) | No | None — no unofficial provider can offer a Meta-backed guarantee, because none is a party to Meta's platform agreement. |
Where Wasaas fits
Wasaas is an unofficial, session-based WhatsApp API: it connects a regular WhatsApp number via QR code and exposes sending, receiving and chatbot flows through a REST API. It is not a WhatsApp Business Platform reseller and has no special relationship with Meta — see connecting without Meta approval for exactly what that connection model does and does not guarantee.
This category also includes open-source, self-hosted options
Libraries that implement the same linked-device protocol exist for self-hosting. Wasaas is a hosted version of that model — you get the API and dashboard without running or maintaining the underlying service yourself.
Is Wasaas a hacked or modified WhatsApp app?
No. "Unofficial" here describes which platform issues the connection, not whether the WhatsApp client itself has been altered. It helps to separate three distinct things people sometimes lump together as "unofficial WhatsApp API":
| Field | Type | Required | Notes |
|---|---|---|---|
| A. Linked-device / session-based (Wasaas) | Not modified | No | Uses WhatsApp's own Linked Devices feature — the same mechanism as WhatsApp Web — to connect a regular, unaltered WhatsApp account. Wasaas hosts that session and exposes it as a REST API. |
| B. Modified / reverse-engineered clients | Modified | No | Apps that patch or repackage WhatsApp's own client (sometimes called “mod” WhatsApp apps). Wasaas does not build, distribute, or run on top of a modified client — this category is unrelated to how Wasaas connects. |
| C. Meta's official Cloud/Business API | Official | No | A separate platform operated by Meta directly, requiring an app review and (beyond a capped free tier) Business verification. Covered in the comparison above. |
Wasaas is category A, not category B. That distinction matters because category B carries real risks Wasaas does not: it typically requires installing a repackaged APK from outside official app stores, can violate WhatsApp's terms in ways unrelated to sending volume, and offers no way to verify what the modified code actually does. Wasaas never asks you to install a different WhatsApp app — you keep using the genuine WhatsApp app on your phone, and Wasaas connects to it the same way a second linked device would.
When the official platform is the better fit
- You need a contractual delivery/uptime guarantee from Meta directly.
- You're sending template-based notifications to large numbers of people who haven't necessarily messaged you first, at a scale where Meta's own compliance tooling matters.
- Your organisation requires working through Meta's official Business Solution Provider ecosystem for procurement or compliance reasons.
When an unofficial API like Wasaas is the better fit
- You want to start sending and testing today, not after a verification queue.
- You're a developer building a REST integration, bulk campaigns, or chatbot flows for a business that already messages its customers on WhatsApp.
- You want a single monthly price with no per-message billing rather than Meta's message-based pricing.
The tradeoff runs the other way too: your number is bound by WhatsApp's normal terms and spam enforcement, and no unofficial provider can promise it will never be restricted for automated-looking behaviour.
Where to go next
- WhatsApp API without Meta approval — exactly what the QR-connection model does and doesn't cover
- WhatsApp chatbot flow API — build and manage bot logic programmatically
- WhatsApp API pricing — flat monthly plans, no per-message fees
- WhatsApp REST API documentation — the full endpoint reference