WhatsApp Cloud API or WaAPI: which one fits your project?
The unofficial messaging API — built for teams that don’t have a quarter to wait.
Send, receive, chats, groups and channels without business verification, template pre-approval or per-message invoices. And an honest look at where Meta’s official API is the better pick.
Live in minutes · Flat monthly rate · Unlimited messages
Side by side
Meta’s Cloud API vs. WaAPI
Both get messages out. They differ in setup, cost model and what you can automate — and the official API wins two of these rows.
|
Meta Cloud API
Official · hosted by Meta
|
WaAPI
Independent · flat rate
|
|
|---|---|---|
| Setup | Meta business portfolio, WhatsApp Business Account, number registration and display name review | Scan a QR code or enter a pairing code |
| Business verification | Not needed to start. One of three ways to get past 250 recipients per 24 hours. Required for an Official Business Account | Not required |
| Message templates | Required outside the 24-hour window. Each template must be approved first (review takes up to 24 hours) | Not required |
| Pricing | API access is free. You pay per delivered message, by category and country. Since 1 October 2026 this includes replies inside the 24-hour window | Flat $10 per connected number a month |
| Sending limits | Better for high volume to new contacts 250 unique recipients per 24 hours for new accounts, then 2,000, 10,000, 100,000 and unlimited | No message cap. Send protection by default: 60 new conversations a day per number, can be switched off |
| Existing number | A number in use in the app must be deleted there first. Exception: coexistence for WhatsApp Business app numbers through a solution partner | Use the number as it is. It is linked like an extra device |
| Groups | Groups API since October 2025: Official Business Accounts only, up to 8 participants | Create groups, manage participants, settings and invites |
| Channels | No Channels API in the Cloud API documentation | Create, list, subscribe, search |
| Communities, polls, status posts | Reactions are supported. Nothing documented for communities, polls or status posts | Supported |
| Calls | Calling API since July 2025. Calls started by the business are billed | Start, accept and reject calls, create call links (beta) |
| Risk of restriction | Lower risk Official channel. Automation is allowed within Meta's policies | Independent service. WhatsApp can restrict numbers that automate — see the limits below |
| Developer tools | Graph API | REST API, webhooks, SDKs for PHP, Laravel, Python and Node.js, n8n node, MCP server with 139 tools |
As of October 2026. Sources, Meta’s documentation: Pricing · Non-template messages · Messaging limits · Templates · Phone numbers · Groups · Calling
How per-message costs add up against a flat rate: per-message vs. flat-rate pricing.
Why go unofficial
Enterprise-level capability. None of the friction.
Ship this week
No Business verification, no template review, no provider onboarding. Pair a number, call the API, done.
Flat rate, forever
One monthly price per connected number. Send one message or a million — the invoice doesn’t change.
Consumer-grade features too
Groups, channels, communities and presence indicators — all first-class here, plus an MCP server for your AI agent.
No new number needed
Use your own number
Personal or business, it doesn’t matter: connect the number that already runs the app. No Meta Business account, no new SIM card, and as many numbers as you need on one subscription.
-
1
Create an instance
Sign up and create an instance in your dashboard. One instance is one connected number.
-
2
Link your number
Scan the QR code with your phone, or enter a pairing code instead. The number is linked like an extra device.
-
3
Call the API
Copy your API token and send your first message with one POST request. Incoming messages arrive by webhook.
Who picks an alternative
If one of these sounds like you, you’re in the right place
Indie founders
Your side project just got traction. You don’t have a month to spend on business-verification paperwork before your next release.
Agencies
You ship multiple client projects. One auth model, one API surface, one bill — not a compliance review per client.
SaaS teams
You need a messaging primitive to plug into existing tooling — not a compliance program or a provider onboarding.
Honest answer
When Meta’s Cloud API is the better choice
WaAPI is not for every project. Pick the official API if one of these applies to you.
High volume to new contacts
You message thousands of people who never wrote to you. The official tiers rise to unlimited unique recipients a day; WaAPI’s send protection allows 60 new conversations a day per number.
You need the official channel
Your compliance team only signs off on Meta’s own platform, where automation is allowed within Meta’s policies.
A verified business profile
You want an Official Business Account. It requires Meta’s business verification, which WaAPI deliberately skips.
Limits
Limits and sending safely
There is no cap on how many messages you send. What gets numbers restricted is contacting many people who never wrote to you — so send protection is on by default for every new number.
What counts as a new conversation: a person who has never written to your number and whom you have not messaged in the last 7 days. Replies to people who wrote to you first and messages to groups and channels never count, and a follow-up within those 7 days doesn’t count twice.
Need more? Spread new contacts across several numbers, or switch send protection off for a number after confirming the warning — at your own risk.
Alternative pricing, simple
Unlimited messages. Media, groups, channels, SDKs and MCP included. Cancel anytime.
- No per-message fees
- No per-user fees
- No setup fee
- Cancel anytime
See why our customers are excited
Trusted by developers worldwide to elevate their apps
Overall we are very happy with the reliability and general service.
Dan M.
CTO
Good and affordable. Uptime is good compared to similar services.
Ranjid E.
CEO
Great tool to send marketing campaigns, would recommend for anyone in need of a reliable service.
Daniel M.
Senior Backend Developer
FAQ: unofficial, explained
The trust and compliance questions people ask before choosing between the official API and WaAPI.
-
No. WaAPI is an independent service. It is not affiliated with, endorsed by or sponsored by the messaging platform or its operators.
-
Yes, that risk comes with any unofficial API: the platform can restrict numbers that send automated messages, above all to people who never wrote to them. Send protection is on by default and keeps new conversations within a safe range; our guide on restrictions explains the rest.
-
Yes. Any number that runs the app — personal or business — can be linked by QR code or pairing code. You don’t need a new number.
-
No. There is no business portfolio, no business verification and no template review. You sign up, link your number and use the API.
-
Yes. The building blocks are the same — send a message, receive a webhook, manage chats — so moving means swapping the HTTP calls, not rethinking your product. Keep in mind that a number already in use in the app has to be deleted there first, unless a solution partner connects it through coexistence.
-
WaAPI is a tool. How you use it is your responsibility — respect opt-outs, obey anti-spam laws, and follow the platform’s Terms of Service. The same principles apply to any messaging integration, official or not.
-
Yes. Outbound webhooks are signed with your secret, retried with exponential backoff, include a request ID for idempotency, and can be filtered per event.
-
Yes. One subscription, many numbers — each exposed as a separate instance with its own webhook, token scope and API surface.
Skip the quarter. Ship the feature.
3-day free trial · No credit card · Cancel anytime.
WaAPI is not affiliated with, endorsed by or sponsored by the messaging platform or its operators. All referenced product names and trademarks belong to their respective owners.