Choosing a WhatsApp API in 2026: 10 options, real prices, and when to use each

Search for "WhatsApp API" and you get two different kinds of product in one list. They work differently, they cost differently, and they carry different risks. Most "best of" lists mix them up. The short version Need templates, marketing to opted-in lists, or Meta's backing? Use Meta's Cloud API, directly or through Twilio or 360dialog. Want to use a number you already have, at a flat monthly price? A linked-device API does that. It needs no Meta approval, but it is not an official integration. Want to run it all yourself? Evolution API is open source. You pay with your own servers and time. Two kinds of WhatsApp API Official (Meta Cloud API) Linked device How it connects A WhatsApp Business account, set up through Meta Pairs a normal WhatsApp account, the way WhatsApp Web does Approval Meta onboarding and business verification None How you pay Per delivered message, by country and message type A flat monthly fee per number Message templates Required to message someone first, or after 24 hours Not used Risk Supported by Meta Not official. WhatsApp can restrict a number that looks abusive Skipping Meta's approval is the reason linked-device APIs exist. What you give up is the official status: WhatsApp can restrict a number it thinks is abusive. The official options Checked on 16 October 2026, from each provider's pricing page. Provider What it charges Meta's message fees Who it fits Meta Cloud API No platform fee Per delivered message, by the customer's country and the message category. The first 1,000 service messages a month for each number are free Teams that can handle Meta's onboarding themselves Twilio $0.005 per message, sent or received Passed through, on top of Twilio's fee Teams already on Twilio for SMS or voice 360dialog From €49 a number a month (€99 Premium, €500 Scale) Added on top. 360dialog says it adds no markup Teams that want a flat fee per number on the official platform What you actually pay on the official route depends on where your customers are and what kind of message you send. Meta's pricing page has the per-country rates. The linked-device options These figures come from each vendor's pricing page, checked on 16 October 2026. Prices change, so check the page before you choose. API 1 number 5 numbers Free tier AI replies WasenderAPI $6 / month $30 / month (Plus, 6 numbers) None, 3-day trial Not listed Green-API $12 / month $60 / month 3 chats You supply the model ChatRail $15 / month $79 / month (Team) 1 number, 500 messages a month, no expiry 10,000 a month included on Core + AI ($29) Maytapi $24 / month (billed yearly) $120 / month 5 conversations a month Not listed Whapi.Cloud $35 / month ($29 billed yearly) $175 / month 5 conversations a month, 150 messages a day Not included (bot integrations listed) UltraMsg $39 / month $195 / month None, 3-day trial Not listed Evolution API Free to license Your servers Self-hosted You bring the keys Which one I'd pick If you... Use Why Send marketing to opted-in lists, or need templates Meta Cloud API, directly or through Twilio or 360dialog It's the official platform. Nothing else is built for large opted-in marketing Already use Twilio for SMS or voice Twilio One account and one bill Want the official platform at a flat fee per number 360dialog From €49 a number a month, plus Meta's fees Want the cheapest hosted connection to your own number WasenderAPI $6 a month. You build limits, retries and AI yourself Want to run it on your own servers Evolution API Open source. You run Node, Postgres and Redis Need WhatsApp Channels or a number-warming tool Whapi.Cloud Mature and feature-rich Want a free tier and SDKs in many languages Green-API From $12 a number. Free tier is 3 chats Want your number protected, with AI replies built in ChatRail From $15 a month. 10,000 AI replies a month on Core + AI What the pricing pages don't tell you "Unlimited messages" is about the vendor, not WhatsApp. Several linked-device APIs say there's no message cap. WhatsApp still restricts numbers that get reported. The fastest way to get reported is a bug that messages one customer over and over. In ChatRail, I stop the 11th message to the same person within five minutes and return an error saying why. Whatever you use, put a limit like that somewhere. Self-hosting is free to license, not free to run. Evolution API is good software. But linked-device libraries break when WhatsApp changes its web protocol, and your messages stop until you upgrade. If you self-host, that's your job, at whatever hour it happens. Official isn't the same as cheap or expensive. With Meta's Cloud API there's no platform fee, but every marketing message costs money, and the rate depends on the country. For a support inbox that mostly answers customers, it can cost very little. For a shop sending order updates to thousands of people, compare it with a flat monthly fee. Bans come from behaviour. An unofficial API doesn't get a number banned by itself. Unwanted bulk messages and reports do. Messaging people who expect to hear from you lowers the risk. Nothing removes it. What I didn't check I compared public pricing and feature pages. I didn't run every API against the same workload, and I can't speak to each vendor's uptime or support. Where a page leaves something out, the tables say "not listed" instead of guessing. The full table, with media, groups, webhooks, MCP and no-code tools for every linked-device API, is on chatrail.dev/compare. If you've used any of these in production, I'd like to hear what the pricing page didn't tell you.