A WhatsApp API provider, often called a WhatsApp Business API provider, is a company that lets your software send and receive WhatsApp messages. There are two families, and most "best provider" lists mix them up. Official providers such as Twilio, 360dialog, Infobip and Wati connect you to Meta's WhatsApp Business Platform: a business number, approved templates, and Meta's per-message fees plus the provider's own. Linked-number APIs such as WasenderAPI, Whapi.Cloud, Unipile and the Swarmhit Raw API connect an existing WhatsApp number as a linked device, the way WhatsApp Web does, and charge per number with no Meta fee. The best provider is the one whose family fits your messages: broadcasts to opted-in customers on one side, one-to-one conversations from a person's own number on the other.
We read each provider's own pricing page and Meta's partner documentation in November 2026. Meta's per-message rates by country are in our WhatsApp Business API pricing guide.
What is a WhatsApp API provider?
On the official side, Meta sells access to the WhatsApp Business Platform through partners, and its documentation names three kinds:
| Partner type | What Meta says it can do | Who pays Meta |
|---|---|---|
| Solution Partner (often called a BSP) | A full range of WhatsApp Business Platform services, with a credit line it can extend to clients and its own invoicing | The partner, who invoices you |
| Tech Provider | The same services, alone or with a Solution Partner, but no credit line | You, with your own payment method, on top of the partner's bill |
| Tech Partner | A Tech Provider that is, or can become, a Meta Business Partner | You, as with a Tech Provider |
You can also skip partners and use Meta's Cloud API directly. Meta then charges only its per-message fees, and everything else, the inbox, the template management, the retries, is yours to build.
Linked-number APIs are not on that list. They are not Meta products: they run a WhatsApp session for a number someone already owns, scanned in with a QR code or a pairing code. That is why they cost so much less per message, and why WhatsApp's own terms apply to them in full. WhatsApp's terms forbid "bulk messaging, auto-messaging, auto-dialing" and allow it to suspend accounts, so these APIs fit a person's own conversations, not campaigns to lists.
Which WhatsApp API providers are worth comparing?
These providers cover most of what developers and sales teams actually choose between:
| Provider | Family | How it charges | Entry price, as listed | Best for |
|---|---|---|---|---|
| Meta Cloud API | Official, direct | Meta's per-message fees only | No platform fee | Teams that will build their own tooling |
| Twilio | Official partner | $0.005 per message in or out, Meta's fee passed through | Pay as you go | Developers already on Twilio for SMS or voice |
| 360dialog | Official partner | Per number per month, Meta's fees added at cost | €49 per number a month | Flat platform cost per number |
| Infobip | Official partner | Per message by country and type, custom pricing through sales | From €0.000909 per message | Enterprises with many channels and markets |
| Wati | Official partner | Plan with seats, template messages extra | $59 a month billed annually | Teams that want an inbox, not an API |
| WasenderAPI | Linked number | Plan by number of sessions | $6 a month for 1 number | Lowest price for a few numbers |
| Whapi.Cloud | Linked number | Per number, unlimited messages | $40 a month list, $29 shown with a discount | WhatsApp-only products, groups and channels |
| Unipile | Linked number | Per connected account, any channel | $55 a month for up to 10 accounts | Products that also need LinkedIn, email or Instagram |
| Swarmhit Raw API (early access) | Linked number | Per connected account, each band at its own rate | $3.90 per account, down to $2.50, 15 accounts minimum | The lowest price per number, with LinkedIn and email on the same API |
| Swarmhit Smart API (WhatsApp in early access) | Linked number, with the outreach engine | Per connected account, each band at its own rate | $16.90 per account, down to $6.90, 2 accounts minimum | Sales follow-ups in sequences with LinkedIn and email, paced and stopped on reply |
Entry prices are only a starting point. On the official side the larger cost is Meta's per-message fee, which goes from a fraction of a cent for a utility message in India to more than 13 cents for a marketing message in Germany. On the linked side, the cost grows with the number of numbers, not with the number of messages.
How do the official providers compare?
Meta Cloud API. The cheapest route on paper, since Meta adds no platform fee. You register the business, verify the number, write and submit templates, handle webhooks and build any inbox your team needs. It suits engineering teams that would build all of that anyway.
Twilio. Twilio adds $0.005 to every message, inbound or outbound, passes Meta's per-template fee through, and charges $0.001 for a message that ends in a Failed status. On 10,000 outbound marketing messages to US numbers, that is $50 on top of Meta's $250, before any replies, which are billed too. The case for Twilio is one API and one bill for WhatsApp, SMS and voice, with its developer tooling. The case against is that the fee grows with every message, including the replies you want.
360dialog. Three plans per number per month, €49 Regular, €99 Premium and €500 Scale, with Meta's fees added on top and, according to the page, no markup on them. The price stays flat however many messages a number sends, which makes 360dialog cheaper than a per-message fee as soon as a number is busy. The higher plans add faster support, business verification within 48 hours, migration help and more throughput.
Infobip. Infobip publishes per-message rates by country and message type, from €0.000909 to €0.190003 on a page updated November 9, 2026, and builds custom pricing through its sales team. It fits companies that already buy SMS, email and voice from one enterprise vendor across many markets.
Wati. Wati is an inbox and automation product on top of the API, priced at $59, $119 and $279 a month billed annually, with 3 to 5 users included, and template messages charged on top. It suits support and sales teams that want to work in an interface rather than write code.
All of them use the same Business Platform, with the same rules: approved templates for anything outside the 24-hour customer service window, Meta's message categories, and its per-message rates by market.
How do the linked-number APIs compare?
The first four rows below sell raw endpoints: connect a number, send and receive messages, get webhooks. The last row is a different product, the Swarmhit Smart API, which adds the outreach engine on top. Prices per number a month, at list price:
| Provider | Price per number | Minimum | 50 numbers a month |
|---|---|---|---|
| WasenderAPI | $6 on the 1-number plan, $4.50 on the 10-number plan | 1 number | Not listed, largest plan is 10 numbers |
| Whapi.Cloud | $40 list, $29 shown with a discount | 1 number | $2,000 at list price |
| Unipile | $5.50 from 11 accounts ($55 covers the first 10), down to $3.50 | $55 a month | $275 |
| Swarmhit Raw API (early access) | $3.90, down to $2.50 with volume | 15 accounts | $195 |
| Swarmhit Smart API, engine included (WhatsApp in early access) | $16.90, down to $6.90 with volume | 2 accounts | $845 |
Per number, the Swarmhit Raw API is the lowest of the raw endpoints, $3.90 against $4.50 to $6 on WasenderAPI, $5.50 on Unipile and $40 on Whapi.Cloud, and it goes down to $2.50 with volume. WasenderAPI sells plans from 1 to 10 sessions with no daily message cap, which suits a single number. Whapi.Cloud prices every number the same, with unlimited messages and a free developer sandbox capped at 150 messages a day. Unipile and the Swarmhit Raw API price per connected account across channels, so a team that also connects LinkedIn accounts or mailboxes pays one bill for all of them. Unipile bills every account at the rate of the band its total falls in. The Swarmhit Raw API bills each band at its own rate, $3.90 per account up to 50 and down to $2.50 at volume, so adding numbers never reprices the ones you already have; the full grid is on the Raw tab of the pricing page, and the Unipile review covers Unipile in depth.
Price is only half of it. A linked number keeps working only while its session does: WhatsApp signs a linked device out when the phone has not been used for 14 days or the device itself has been idle for 30, and a number that sends like a robot can be banned. Ask any provider how it reports a dropped session, how you show the QR code to the number's owner again, and whether a send retried after a timeout can go out twice. The open-source libraries these services build on, from Baileys to whatsmeow, are compared in our guide to the unofficial WhatsApp API.
Which WhatsApp API provider should you choose?
Start from who sends and to whom, not from the price:
- Notifications, receipts or promotions to opted-in customers, from one brand number: an official provider. Choose 360dialog for a flat cost per number, Twilio if you already run SMS on it, Infobip for an enterprise contract across markets, Wati if the team wants an inbox, or the Cloud API directly if you will build the rest.
- One-to-one conversations from a person's own number, such as a rep following up a deal after a call: a linked-number API, priced per number, sending messages that read like the ones the person would type.
- WhatsApp as one channel among LinkedIn and email in a product or an agent: a provider that covers all three on one API, so one integration and one bill cover the whole conversation.
The cost comparison for a 20-rep team, official templates against linked numbers, is worked through in our WhatsApp Business API pricing guide.
What breaks when you pick the wrong provider?
A per-message fee on a chatty channel. A support team that answers every customer on Twilio pays $0.005 on each inbound and outbound message, plus Meta's fees. The fix is to model replies, not only outbound messages, before you sign, and to compare against a flat per-number plan.
Templates rejected or moved to marketing. On the official side, a sales follow-up is a marketing template, and Meta can move a utility template to marketing in its recurring reviews, at a higher rate. Read Meta's category rules before you budget, and subscribe to the template_category_update webhook.
A broadcast on a linked number. Sending the same message to hundreds of people who never wrote to the number is what WhatsApp's terms forbid, whichever provider sends it. Keep linked numbers for the conversations their owner would have anyway, and move volume to the Business Platform.
A number locked to one provider. Changing provider later means moving the number to another WhatsApp Business Account, which Meta supports and which 360dialog's top plan sells as migration help. Ask how the provider handles it before the number is printed on your packaging.
Where do the Swarmhit Raw API and Smart API fit?
Both are in the linked-number family. The Swarmhit Raw API, in early access, gives your code one endpoint per WhatsApp action: link a number with a QR or pairing code, send text, files and voice messages, read chats, groups and reactions, with signed webhooks and a client_id so a retried send goes out once, on the same paths as its LinkedIn and email actions.
The Swarmhit Smart API is the level above, with the engine included, which is why it costs more per number than raw endpoints. A rep's WhatsApp number joins the same sequence as their LinkedIn account and email mailboxes, the engine paces each number, and a reply on any channel stops the follow-ups. It is built for deal follow-ups from people's own numbers, not for broadcasts. WhatsApp is in early access on both, and the WhatsApp channel page shows what each covers, with the WhatsApp playbook for how sales teams use it.
FAQ
What is the WhatsApp Cloud API?
It is Meta's own hosted API for the WhatsApp Business Platform: Meta runs the servers, and your code calls its endpoints to send templates and messages and receive webhooks. You can use it directly, paying only Meta's per-message fees, or through a provider that adds tooling, support and billing. Every official provider in this guide sends through the same Business Platform.
Can I keep my existing WhatsApp number?
On a linked-number API, yes: that is the point, the number keeps working on the phone. On the official side, Meta's coexistence lets a number already on the WhatsApp Business app, version 2.24.17 or later, be onboarded to the Cloud API through a Solution Partner or Tech Provider and keep using the app for one-to-one chats, with up to six months of history synced. Group chats are not synced, and broadcast lists become read-only.
What is the difference between the WhatsApp Business app and the API?
The Business app is for a person chatting from a phone, with a profile, labels and quick replies. The API is for software: it sends and receives through code, at volume, with webhooks. Official providers sell API access to the Business Platform, with templates and Meta's fees, while linked-number APIs drive a regular WhatsApp or WhatsApp Business account the way WhatsApp Web does.
What is the best WhatsApp API provider?
It depends on the family you need. For broadcasts and notifications to opted-in customers, an official provider: 360dialog for a flat €49 per number a month plus Meta's fees, Twilio for one API across SMS and WhatsApp, Wati for an inbox. For one-to-one conversations from a person's own number, a linked-number API priced per number, such as the Swarmhit Raw API, WasenderAPI, Whapi.Cloud or Unipile, or the Swarmhit Smart API when the number has to run in sequences with LinkedIn and email.
Is Twilio good for the WhatsApp API?
Twilio is a solid choice if you already use it for SMS or voice and want one API and one bill. It adds $0.005 to every WhatsApp message, inbound or outbound, on top of Meta's fee, which it passes through, plus $0.001 for a message that fails. For a busy number that sends and receives a lot, a flat per-number plan such as 360dialog's usually costs less.
Can I use the WhatsApp API without a provider?
Yes. Meta's Cloud API can be used directly, with no platform fee: you pay only Meta's per-message rates, with your own payment method. You then build the parts a provider would give you, such as template management, an inbox, webhook handling and retries. Providers exist for teams that would rather pay a fee than build and run those parts.
What is the cheapest WhatsApp API?
Per number, linked-number APIs are the cheapest, with no Meta fees: the Swarmhit Raw API costs $3.90 per number a month, down to $2.50 with volume, from 15 accounts, against $4.50 to $6 on WasenderAPI, whose single-number plan suits one number. On the official side, the Cloud API used directly adds nothing to Meta's per-message rates, but every message and every reply is billed.
What is the difference between a BSP and a Tech Provider?
Both offer WhatsApp Business Platform services. A Solution Partner, often called a BSP, has a credit line from Meta and invoices its clients for Meta's fees. A Tech Provider has no credit line, so its clients add their own payment method and Meta bills them directly, while the provider bills its own services separately.
Can a linked-number WhatsApp API get my number banned?
It can. Linked-number APIs are not Meta products, and WhatsApp's terms forbid bulk messaging, auto-messaging and auto-dialing and allow it to suspend accounts. The risk comes from how the number is used: a person's own conversations, at a human pace, look like normal use, while the same message sent to hundreds of strangers looks like spam to WhatsApp, whichever provider sends it.




