Compare
Three ways to put WhatsApp behind an API. Here is the honest version.
Meta's official Cloud API, a self-hosted open-source library, or a hosted API like WALayer. Each is the right answer for someone. This page tells you which one is right for you, including when it is not us.
The three approaches
What each one asks of you, and what it gives back.
Meta's WhatsApp Business Platform
Official Cloud API
- Best for
- Brands sending high-volume transactional messages who need Meta's blessing: regulated industries, enterprises with compliance teams, and anyone for whom platform risk is unacceptable.
- The trade-off
- Business verification and template approval before you send, per-conversation pricing that grows with volume, business-initiated messages restricted to approved templates, and no API access to the groups, channels and communities surface.
Run a multi-device library yourself
Self-hosted open source
- Best for
- Teams with the engineering capacity to own the whole stack and a strong reason to keep it in-house: total control, no per-anything fees beyond your infrastructure.
- The trade-off
- You operate everything WhatsApp makes hard: cryptographic session state that corrupts if two processes touch it, reconnection, IP reputation, human-like send pacing, message deduplication, webhook delivery and library updates every time the protocol shifts. Same terms-of-service position as any unofficial approach.
Your number, our infrastructure
Hosted API: WALayer
- Best for
- Product teams who want their existing WhatsApp number behind a REST API in minutes: notifications, support automation, CRM sync, groups and channels, without operating session infrastructure.
- The trade-off
- Unofficial, like self-hosting: WhatsApp can rate-limit or ban a connected number, and no provider can promise otherwise. Our job is that everything on our side is fault-free, and that when WhatsApp acts we detect it, freeze sends, export your queue and guide recovery.
Side by side
The dimensions evaluators actually decide on.
| Dimension | Official Cloud API | Self-hosted open source | WALayer |
|---|---|---|---|
| Time to first message | Days to weeks: business verification, then template approval | Days: stand up the library, storage and webhooks yourself | Minutes: scan a QR or enter a pairing code, then call the API |
| Use your existing number | No, the number moves to the Business Platform | Yes, linked as a device | Yes, linked as a device, changeable at no cost |
| Message surface | Templates plus a 24-hour customer-service window | Everything the protocol supports, if you build it | 22 message types, groups, channels and communities, one endpoint |
| Approval flow | Meta reviews your business and every template | None | None: pair a number and send |
| Pricing model | Per conversation, category-dependent, grows with volume | Free software; you pay in infrastructure and engineering time | Flat price per connected number, fair-use messaging with no per-message fees |
| Terms-of-service position | Fully official | Unofficial: numbers can be rate-limited or banned | Unofficial: same risk, stated plainly, with detection and guided recovery |
| Who runs the hard parts | Meta | You: sessions, reconnection, pacing, dedupe, webhooks | WALayer: never lose a message, never duplicate one |
The terms-of-service row is not small print. WALayer and every self-hosted stack connect real WhatsApp accounts outside Meta's sanctioned channel, and a connected number can be rate-limited or banned. What we control is our side of the line: the four promises and how we protect your numbers when WhatsApp acts.
Compare FAQ
The questions evaluators ask next.
Skip Meta approvals. Skip message fees. Skip the dropped messages.
Free developer sandbox, ready in minutes. No approvals, no templates, no per-message fees.
3-day free trial · connect in under 5 minutes · cancel anytime.