WhatsApp API alternatives, compared honestly
Six categories of product, what each is genuinely good at, and the cost nobody puts on their pricing page. We are one of these, and the page says where we are the wrong answer.
Organised by category rather than by vendor, on purpose. Individual feature lists change weekly, and a page claiming a named competitor lacks something is wrong within a month. What changes slowly is the architecture each category is built on — and the architecture is what produces the trades below.
The short version
| Cloud API direct | BSP / SMB inbox | Your own number | |
|---|---|---|---|
| Meta approval needed | Yes | Yes | No |
| Template pre-approval | Yes | Yes | No |
| Per-conversation fee to Meta | Yes | Yes | No |
| Team answers from their own phone | No | No | Yes |
| Green tick possible | Yes | Yes | No |
| Time to first message | Days | Days | Minutes |
| Formal appeals process | Yes | Yes | No |
| Suited to millions/day | Yes | Yes | No |
| Suited to conversations | Workable | Yes | Yes |
| Keeps existing chat history | No | No | Yes |
Meta Cloud API, direct
Meta’s own API. You verify a business, move a number onto the platform, and send over HTTP. Everything else in the official column is built on this.
- The only fully sanctioned route, with a real policy and appeals process
- Very high volume, tiered by a quality rating you can see
- Green tick verification is possible
- No intermediary taking a margin
- Per-conversation pricing that varies by country and category
- Templates must be approved before you can start a conversation
- The number leaves the WhatsApp app — nobody answers from a handset
- You build the inbox, the routing and the reporting yourself
Pick this if: You have engineers, high volume, and messages whose wording rarely changes.
Official BSPs and resellers
Business Solution Providers sit on top of the Cloud API and sell access with better tooling, support and often multi-channel reach.
- Same sanctioned footing as going direct, with less plumbing
- Usually SMS, email and voice in one account
- Enterprise support, contracts and uptime commitments
- Mature SDKs and long-standing documentation
- Meta’s conversation fee plus the provider’s margin
- Still templates, still approval, still a number that leaves the app
- Onboarding is measured in days, sometimes weeks
- Priced and designed for scale — small senders feel it
Pick this if: You want the official route and would rather buy the tooling than build it.
Official-API inboxes for SMBs
A shared inbox, broadcasts and light automation, built on the official API and sold to businesses rather than to developers.
- Shared inbox, assignment and canned replies out of the box
- Approachable for non-technical teams
- Ecommerce integrations, often Shopify-first
- Broadcast tooling that stays within policy
- Conversation fees underneath the subscription — two bills, one of them variable
- Template approval is still in the loop for anything proactive
- Agents answer in a web console, not from their own WhatsApp
- APIs are usually thinner than a developer-first product’s
Pick this if: A non-technical support team that wants an official number and a web console.
Open-source helpdesks
A customer support platform you host yourself. WhatsApp arrives through a provider you connect, so this is an inbox rather than a route to WhatsApp.
- No per-seat licence, and the data stays on your own servers
- Genuinely extensible — it is your deployment
- Several channels in one place
- You still need a WhatsApp provider underneath, and pay for it
- You run it: upgrades, backups, uptime
- WhatsApp-specific concerns — pacing, warm-up, ban survival — are not its subject
Pick this if: You have ops capacity and data residency requirements that decide the question.
Unofficial APIs on your own number
Your existing WhatsApp account connected as a linked device, the same mechanism as WhatsApp Web. No Meta onboarding, no templates.
- Your team keeps answering from their own phones
- No per-conversation fee to Meta, and no approval queue
- Live in minutes, and the number keeps its history
- Anything a normal account can send — voice notes, groups, replies
- No green tick, and no formal appeals process if it goes wrong
- Nothing between you and a ban except the vendor’s restraint and yours
- Vendor quality varies enormously — this is the category to be careful in
- Not built for millions of notifications a day
Pick this if: Your WhatsApp is a conversation rather than a broadcast, and a team answers it.
Build it yourself
The open-source libraries the unofficial category is built on. Free, and yours.
- No licence cost and complete control
- No third party holding your message content
- Excellent for a single number and a clear use case
- You own reconnection, session storage and every protocol change
- Pacing, warm-up, quiet hours and ban survival are all yours to build
- One number is a weekend; twenty numbers is a product
- The day it breaks, it breaks in production and there is nobody to ask
Pick this if: One number, an engineer who enjoys this, and tolerance for the odd bad week.
Where we are the wrong answer
- You need the green tick. Only the official platform issues it. If verification matters to your brand, that decides it.
- You send millions of notifications a day. That is what the Cloud API is engineered for and we are not.
- You need a contractual appeals path. An unofficial route has no formal recourse if an account is restricted, and for a regulated business that is usually disqualifying.
- No third party may hold message content. Then you want the libraries, self-hosted, and the work that comes with them.
Questions worth asking any vendor
- Does it pace sends, or will it let me send a thousand messages in a minute?
- Can it tell me the difference between accepted and delivered?
- Does a sequence stop when somebody replies — across the flow, not the step?
- What happens on the day my number is banned?
- Can my team answer from their own phones, or only from a console?
- Can I export everything and leave?
Most of those are answered on our FAQ. The longer arguments are in API versus your own number and the capability comparison.
Written September 2026. Products change; if something here is out of date or unfair to your product, tell us and we will correct it.