Tutorials, changelogs, and developer tips for building with the WhatsApp HTTP API.
Featured
Wassenger now runs on Meta's official Cloud API, not the unofficial WhatsApp Web protocol older reviews describe. That changes what a real alternative looks like. Here is a feature-by-feature comparison against both official and unofficial options, and a name mix-up worth clearing up first.
Business Verification is not a formality you wait out. It requires a registered legal entity, a document proving it, a matching address, and a website that agrees with all three. If any of those does not exist yet, here is what actually works instead.
Not a comparison table. A verdict. Here are the specific situations where a session-based API beats Meta's Cloud API outright, the ones where it does not, and how to tell which situation you are actually in.
Twilio charges $0.005 on every WhatsApp message, inbound and outbound, on top of Meta's own fees. At real volume that tax adds up to hundreds of dollars a month for nothing you can point to. Here is the actual math and what to do about it.
360dialog is a Meta Business Solution Provider, so an alternative here means something bigger than swapping vendors: it means deciding whether you need Meta's official platform at all. Here is how to make that call properly, and what each direction actually costs.
Maytapi charges $24 per phone per month with no bundled tiers, so ten numbers costs $240. Here is what that looks like against providers that price by session count instead of by number, and what actually changes when you switch.
Green API's free Developer plan is one of the better ways to prototype a WhatsApp integration. The trouble starts when you outgrow it: per-instance billing, ruble-denominated pricing, and limits that only reveal themselves in production. Here is what to move to and how.
UltraMsg charges $39 per instance, and one instance is one WhatsApp number. That model is fine at one number and brutal at ten. Here is the arithmetic, the alternatives that bundle sessions instead, and what you give up by leaving.
WasenderAPI is a good, cheap, developer-focused WhatsApp API, and it is our closest competitor. Here is a straight comparison of pricing, features and trade-offs, including the cases where we would tell you to stay put.
Whapi.Cloud is a good product with one expensive characteristic: $35 per number per month. Here is where that price is worth paying, where it is not, what you lose by leaving, and exactly how to migrate if you decide to.
WAHA got considerably better in 2026, so half the reasons people used to look for an alternative no longer apply. Here is what actually still pushes teams away from it, which options are worth evaluating, and an honest case for staying put.
From version 2.4.0, Evolution API instances must activate against a licensing server before serving traffic. If that changed your calculation, here are the alternatives, what migrating actually involves, and an honest look at the infrastructure you were maintaining anyway.
whatsapp-web.js works by driving a real browser, which is why it costs about a gigabyte of RAM per session and falls over under load. Here are the WebSocket-based libraries, self-hosted wrappers and managed APIs that do the same job without Puppeteer, and when the browser is actually worth keeping.
Baileys is a library, not a service, and that distinction is the whole reason people go looking for an alternative. Here is what you actually end up building around it, which other libraries and wrappers are worth considering, and how to tell when maintaining it stops being worth the money you save.
Verification queues, template approvals, per-message billing and the free service window closing in October 2026. If Meta's platform is not working for you, here is every real alternative, what each one costs, and which complaint each one actually solves.
The official on-premises WhatsApp API shut down in October 2025. Self-hosting now means running the WhatsApp Web protocol yourself. Here is what that actually involves, which open source projects are worth deploying, what it costs once you count engineering time, and whether it genuinely solves your GDPR problem.
Twilio, 360dialog, Whapi, 2Chat, WasenderAPI, WAHA, Evolution API and more, compared on what actually differs: pricing model, approval requirements, feature coverage and risk. Includes the cases where we are not the right answer.
Working code for sending WhatsApp messages from Node.js, Python and curl, plus the parts most tutorials skip: phone number formatting, media uploads, retry logic, rate limiting, and receiving replies.
n8n plus a WhatsApp API gets you a working automation in an afternoon, no code required. Here is how to wire the two together, three workflows worth building, and the mistakes that turn a clever automation into a banned number.
Polling for new WhatsApp messages is a waste of everyone's time. Here is how webhooks work, what events you actually get, how to verify signatures so nobody can forge a message into your system, and how to build an endpoint that survives retries and traffic spikes.
A WhatsApp MCP server lets Claude read and send messages on your own number through natural language. Here is how the protocol works, the two ways to connect, working configs for Claude Desktop, Claude Code and Cursor, and the security decisions worth making before you wire it up.
Volume is not what gets numbers banned. Blocks and reports are. Here is how WhatsApp's enforcement actually works in 2026, a realistic warm-up schedule, the operating rules that keep numbers alive, and what to do in the first hour after a restriction lands.
Meta's rate card is only the first layer of your WhatsApp bill. Here is the full 2026 picture: per-message rates by country, BSP markups, the free windows that close in October, hidden costs nobody warns you about, and three worked examples.
There used to be three ways to reach WhatsApp programmatically. One died in October 2025. This is a working engineer's comparison of what is left: Meta's Cloud API and the session-based alternatives, with the trade-offs laid out honestly.
You can send WhatsApp messages from code without ever opening Meta Business Manager. Here is exactly how session-based APIs work, what you give up, what you gain, and the real price you pay in ban risk, compliance exposure and lost features.