WhatsApp Business API Cost per Month: What US Businesses Actually Pay
The WhatsApp Business API has no fixed monthly price. Your bill is Meta's per-message template fee plus whatever your provider charges, and the second half is where budgets go wrong. Here are the real monthly numbers at 1,000, 10,000, and 100,000 messages.
Short answer: the WhatsApp Business API has no monthly subscription of its own, so your monthly cost is Meta's per-message template fee plus your provider's charge. For a US business sending 10,000 utility templates a month, Meta's share is $34. Through a usage-priced provider like Twilio at $0.005 a message you land around $84 a month. Through a flat-rate platform you pay Meta's $34 plus a fixed plan and nothing per message.
That gap between $34 and $84 for the exact same 10,000 messages is the whole story of WhatsApp budgeting. Meta charges everybody the same. What separates a cheap month from an expensive one is the layer sitting between you and Meta, and almost nobody models that layer at the volume they will actually reach in six months.
Why there is no flat WhatsApp Business API price
The API itself is not a product you subscribe to. Meta gives you the Cloud API for free, hosts it, and bills you when a template message is delivered. There is no seat cost, no minimum, and no monthly platform charge from Meta. What you pay depends on three variables: how many template messages you send, which category those templates fall into, and which country the recipient's number belongs to.
Since July 1, 2025 the billing model has been strictly per message. The older system, where Meta charged for a 24 hour "conversation" and handed you the first 1,000 conversations free each month, is gone. It still shows up in vendor calculators and in a depressing number of blog posts, so if a quote you are reading talks about conversations, it is running on retired arithmetic and the number will be wrong.
What a US month actually looks like
Meta does not publish US dollar figures in its developer documentation. Twilio does publish a US rate card, which makes it the reliable public benchmark. Checked in July 2026, a delivered utility or authentication template to a US number carries a Meta pass-through fee of $0.0034, and Twilio adds $0.005 of its own on every message in and out.
| Messages per month | Meta fees | Cloud API direct | Twilio | Flat-rate platform |
|---|---|---|---|---|
| 1,000 | $3.40 | $3.40 plus engineering | $8.40 | $32.40 |
| 10,000 | $34.00 | $34.00 plus engineering | $84.00 | $133.00 |
| 100,000 | $340.00 | $340.00 plus engineering | $840.00 | $639.00 |
Notice what happens between the second and third rows. At 10,000 messages the usage-priced provider is the cheaper option by a comfortable margin. At 100,000 it costs $200 more, and the gap keeps widening because one column grows with every message and the other does not. The crossover sits somewhere around 60,000 messages a month. If you want to find your own crossover point rather than trusting three sample rows, the WhatsApp pricing calculator runs the same math against your volume and template category.
The Cloud API column is not really $34
Going direct to Meta genuinely costs $3.40 per 1,000 messages in fees and nothing else. It is also the option that quietly costs the most for most teams, because the fee is only the part that shows up on an invoice.
Somebody has to build template submission and category handling, contact storage, opt-out tracking, rate limiting against Meta's 80 messages per second ceiling, retry logic for failures, webhook handling for delivery receipts, and reporting your marketing lead will ask for in week two. Then somebody has to maintain it every time Meta changes something, which is often. At 10,000 messages a month you are choosing between roughly $100 of software and several thousand dollars of engineering time. The WhatsApp Cloud API page walks through exactly what you would be building.
Direct integration makes sense when you have engineers with spare capacity, an unusual workflow no platform supports, or volume high enough that the per-message provider fee genuinely dwarfs a developer's salary. For everyone else it is a false economy.
Half your monthly messages might be free
Three exemptions come straight from Meta's own wording, and a support-heavy business can knock a serious chunk off its bill with them.
- The 24 hour customer service window. When a customer messages you first, a 24 hour window opens and all non-template messages inside it are free of Meta fees. Every reply your team sends that day costs nothing beyond your provider fee.
- Utility templates inside an open window. If a service window is already open, utility templates delivered into it are free too. The shipping update sent in the same conversation where the customer just asked about their order is a $0 message.
- Free entry point conversations. A chat started from a click to WhatsApp ad or a Facebook Page call to action opens a free entry point window, and Meta's wording is that all messages are free for 72 hours.
The practical consequence is that response speed is a billing decision, not just a service one. Let a window close and you need a paid template to reopen contact. Our guide to the WhatsApp 24 hour customer service window covers how the timer actually behaves.
The US line item that does not exist
If you are budgeting for American customers, delete the marketing template row entirely. Meta paused delivery of marketing category templates to US phone numbers on April 1, 2025, with no published resume date. A marketing template can pass review, sit approved in your account, and still never arrive: the Cloud API returns error 131049 and Twilio surfaces it as 63049.
US rate cards show no charge for marketing templates as a result, which reads like free promotional messaging and is nothing of the sort. Nothing is delivered, so nothing is billed. Budget your US volume on utility, authentication, and service messages, and put marketing spend against the countries you can actually reach. There is more detail in can you send WhatsApp marketing messages in the US.
What to check before you sign anything
Providers quote very differently, and headline per-message rates hide most of the variance. Four questions cut through it.
Is there a markup on Meta's fee? Some resellers add a percentage on top of the pass-through rather than a flat per-message charge. That compounds against you at volume. Ask for the Meta fee and the provider fee as two separate lines.
Are inbound messages billed? Twilio charges its $0.005 on messages your customers send you as well as messages you send. For a support team that flips the effective cost of a conversation, since a busy thread might be twenty inbound messages.
What is metered as an add-on? Link shortening, click tracking, and scheduling are billed separately by some providers. Twilio's Messaging Engagement Suite is $0.015 per message with the first 1,000 free monthly, which is three times the base message fee for features many platforms include.
What happens at your projected volume, not your current one? This is the one that catches people. A $0.005 fee is invisible at 1,000 messages and is $500 a month at 100,000. If messaging is one line in a wider software budget, it deserves the same forecasting you would give any other recurring SaaS spend you track, because it is one of the few that scales directly with how well your business is doing.
A realistic monthly budget
For a mid-sized US ecommerce business sending order confirmations, shipping updates, and delivery notices to around 8,000 customers a month, plus answering roughly 1,500 inbound support conversations, the month looks like this: about 24,000 utility templates at $0.0034 is $81.60 to Meta, minus the portion delivered inside open service windows, which in practice trims 10 to 20 percent off. Support replies inside the window cost nothing to Meta. Add a flat platform plan and the whole channel runs at well under $250 a month.
That is the number worth holding onto. WhatsApp is not expensive at the message level. It gets expensive when a per-message provider fee rides along with every one of those messages, and when marketing templates that will never be delivered sit in a US forecast. Fix those two things and the monthly cost is predictable enough to plan around.
For the per-message view rather than the monthly one, see what it costs to send 1,000 WhatsApp messages, and for the full category-by-category structure of Meta's billing, WhatsApp Business API pricing.