WhatsApp API Pricing 2026: Per-Message Rates vs a Flat Licence

What does WhatsApp API pricing cost in 2026?

Meta's rate card charges per delivered message, by category and destination country. Twilio's September 2026 pricing page lists utility and authentication messages starting at $0.0034 per message, and Twilio adds its own $0.005 handling fee. The first 1,000 Service messages per business number each month are free.

The primary source, quoted. Twilio's Help Center notice on Meta's October 2026 pricing change reports that Meta “will charge on a per-message basis for all Service messages, consistent with how Meta charges for template messages,” effective 1 October 2026. The same notice covers utility templates sent in reply inside an open 24-hour window.

Why a July-dated page understates the bill. That notice also records Meta “hasn't been charging for these messages since November 1, 2024.” A pricing page written in July 2026 was written while Service messages were still free, so it omits a line item that now applies to a support inbox. July is a before-and-after marker, not a current price.

The spread inside “per message.” Conecxt's provider audit of 7 October 2026 lists India marketing templates at ₹0.8631 against ₹0.1150 for utility, authentication and service — roughly 7.5 times the rate. Marketing and support are different products with different meters.

The rate you can use. $0.0034 plus $0.005 is $0.0084 per blended US/Canada utility message, before any platform subscription. That is arithmetic on two published inputs, not a quoted invoice.

Is WhatsApp API pricing still per conversation?

No. The 24-hour conversation window still decides what you may send, but it is no longer the billing unit. Sendr's report of 8 October 2026 states that Meta retired conversation-window billing on 1 July 2025, and that template messages are now charged per delivered message. A budget built on conversation counts misreads the meter.

The window survives as a rule. Twilio's WhatsApp key-concepts documentation states that an inbound message opens a 24-hour customer service window for free-form replies, and that outside it “you may only send a message using an approved template.” Repricing does not move that rule.

The allowance, precisely. Manychat's WhatsApp pricing guide, updated 29 October 2026, states: “Each WhatsApp Business phone number includes 1,000 free service messages per calendar month… After you use the 1,000 free messages, additional messages are charged, starting with the 1,001st message.” It applies per number, resets monthly and does not carry over.

What to budget in. Delivered messages split by category and country, the free allowance consumed in that period, and any provider handling fee. A single blended figure hides those variables and will be wrong in at least one direction.

How do metered, per-number and flat-rate WhatsApp pricing models compare?

Metered pricing charges per message. A per-number platform fee swaps the meter for a subscription but still passes Meta's per-message charges through it. Only a flat licence stops charging per message, and only when the sending work runs on hardware you already own.

The rule that decides the row. Any per-message markup, however small, keeps a meter running. A per-number fee is a fixed cost on top of a variable one. Neither is flat-rate, and “no markup on Meta's fees” is a different claim from “no per-message charge.”

The two inputs. Twilio's pricing page, current as of September 2026, gives Meta's utility rate starting at $0.0034 and Twilio's $0.005 handling fee. Twilio also states: “Twilio's message handling fee for WhatsApp is $0.005, inbound or outbound.” Read that literally — a customer's reply is a billable event.

Short verdicts, one trade-off each.

• Twilio — for teams already on Twilio infrastructure who want a metered, pay-as-you-go gateway. Trade-off: inbound replies are metered at the same $0.005.
• 360dialog, respond.io, Wati, Gupshup — business solution providers that pass Meta's rates through and charge their own subscription or per-message layer on top. Trade-off: the platform fee and the meter both remain, and those prices are set by the vendor, not by Meta.
• SocialMate — for founders, agencies and developers who want to stop paying per message and keep the data local, on their own number. Trade-off: not the official Business API, and no tool can guarantee against bans.

At what volume does a flat-rate WhatsApp API alternative beat per-message pricing?

At a blended $0.0084 per US/Canada utility message, $10 a month buys about 1,190 messages and $99 a year covers about the first 980 a month. Above those volumes the meter keeps running and a flat licence does not.

The arithmetic, shown once. Both inputs are published: $0.0034 is Meta's utility rate and $0.005 is Twilio's handling fee (Twilio pricing page, September 2026). SocialMate Pro is $10 per month, or $99 per year — $8.25 a month equivalent.

• $10.00 ÷ $0.0084 = about 1,190 messages
• $8.25 ÷ $0.0084 = about 980 messages per month
• 10,000 messages a month at $0.0084 = $84.00 metered — ManySetter works the same 10,000 utility templates through Twilio at $84 to US/Canada — against $8.25 a month on annual flat

This compares pricing models. It does not predict your bill. Your rate depends on category, destination country and provider, and the calculation uses Meta's cheapest major category — so the real crossover usually arrives sooner than 1,000 messages, not later.

The third-party version of the argument. WSAPI, 25 March 2026, states that at Meta's US rate of $0.0034, “$5 buys about 1,500 messages. Under roughly 1,500 template messages a month, Meta direct costs about the same or less. Above that, a flat price wins.” That is a competitor making the structural case, not an endorsement of SocialMate.

The ceiling nobody mentions. A flat licence has its own limit. 10,000 messages a month is about 333 a day, inside Pro's safe starting cap of 500 a day per account. Higher volume means High-Volume Mode, which scales to 5,000 a day per account only after 72 hours of warming. Warming is not optional, and no volume is risk-free.

When the official API is the better buy. Say it plainly: a business sending a few hundred utility messages a month will usually pay less through the official API than through any licence, and it gets the official channel's durability. Below the crossover, do not buy a licence to save money you are not spending.

Which WhatsApp API costs do comparison pages leave out?

Inbound replies metered by the provider, per-number platform fees packaged under a “no Meta markup” claim, and the free allowance you will not actually consume evenly across a month. Twilio's own documentation states its $0.005 handling fee applies inbound or outbound, so a support inbox pays on replies as well as sends.

Inbound is the hidden line. Most comparisons quote the outbound rate. For a support inbox where customers reply before you answer, inbound can be the larger half of the bill, and it appears nowhere in a headline “per message” figure.

“No markup” still means a subscription. A provider can pass Meta's rates through honestly and still charge a recurring per-number fee. That is a legitimate model. It is not a flat rate, and the meter continues underneath it.

The allowance is monthly, not average. Manychat's guide, updated 29 October 2026, confirms the 1,000 free Service messages reset each calendar month with no carryover. A spike in week one is not offset by a quiet week four.

The honest conclusion. Flat-rate means the vendor has stopped pricing your volume at all. That is only economically possible when your volume costs the vendor nothing — which is what running the automation on your own machine achieves. See what Pro includes.

What does the official WhatsApp API require besides money?

A Meta Business Portfolio, a WhatsApp Business Account, an approved phone number, approved templates and the 24-hour customer service window. Repricing removes none of them, and each one sets lead time before a single message is delivered.

The hierarchy. The official API is organised as Meta Business Portfolio → WhatsApp Business Account (WABA) → phone number, with templates and numbers living inside the WABA. Every billing change layers on top of that structure.

The window is the governing constraint. Twilio's key-concepts documentation states that outside the 24-hour window “you may only send a message using an approved template.” This is the rule that shapes what an automation can do, independent of price.

Meta has moved the meter before. Per Twilio's Help Center notice, Meta has not charged for Service messages since 1 November 2024, and since 1 July 2025 has not charged for utility templates sent in reply inside an open 24-hour window. Both become billable on 1 October 2026. Assume further movement. The structure beneath the pricing has not moved at all.

Why it matters for consent-first messaging. If your automation sends messages to people already waiting on you — an order confirmation, a booking reminder, a return update — the portfolio, WABA, template and window are permanent overhead on work that is routine. That is the durable case, not the per-message rate.

What does a flat-rate alternative change, and what does it not?

A flat licence removes per-message billing and Meta approval. It also changes the platform you build on: not the official Business API, independent of Meta, and still exposed to bans. Both halves are part of the price.

What changes. SocialMate is a self-hosted desktop app that runs on your machine using your own WhatsApp number. Free is $0 forever, no card, 200 messages a day on one account. Pro is $10 per month or $99 per year and starts at a safe 500 messages a day per account, scaling to 5,000 after 72 hours of warming via High-Volume Mode. There is no per-message fee at any tier, in either direction. One licence includes one device; add seats for more concurrent machines. WhatsApp accounts are unlimited on Pro.

What the anti-ban engine does. Randomised delays and jitter, Safe/Balanced/Fast pacing profiles, per-number rate limits, session warming, a real typing indicator and read receipts before replying, an adaptive throttle that slows sends as risk climbs, a duplicate-content guard, live risk scoring including cold-outreach detection, and risk-based auto-resume for cooled accounts. On the desktop app the connection leaves from your own residential IP — the network WhatsApp already associates with your number. That removes a risk factor. It does not remove risk.

An operator note. The 500/day Pro starting cap is a ceiling, not a target. High-Volume Mode is earned over 72 hours of warming, not switched on day one.

What it does not change. SocialMate is not the official WhatsApp Business API and is not affiliated with, endorsed by or partnered with WhatsApp or Meta. Bans are always possible on any route; the anti-ban engine reduces risk rather than eliminating it. Automating WhatsApp may conflict with WhatsApp's terms. Consent is not optional — this is messaging for people who already ordered, booked or asked, never a bought or scraped list.

How do developers connect n8n and MCP to a flat-rate WhatsApp setup?

The local HTTP API runs on Free for read endpoints and plain text send. Pro adds media, groups, polls, scheduled messages, the smart queue, unlimited webhooks and the named tunnel. The webhook catalogue is 35 events, of which 9 are free. Native n8n and MCP surfaces let your own LLM act on WhatsApp without a per-message meter.

n8n is a native node, not a recipe. The community node n8n-nodes-socialmate ships with a scope-aware credential, an action node and a trigger node, and every operation is usable as an n8n AI-Agent tool. The strongest operation is Get AI Context: one call returns a role-mapped, token-windowed transcript, so an agent gets recall that survives restarts and the first message of a thread. SocialMate supplies the memory; your LLM is the brain.

MCP is an open protocol surface. SocialMate ships a native MCP server exposing 44 WhatsApp tools, so Claude Desktop, Claude Code, Cursor and Cline can send, read, manage contacts and groups, queue batches of personalised messages and fetch conversation memory. The local API server is off by default: enable it in API & Integrations, create an API key, then point the client at npx -y socialmate-mcp. Every tool call passes the same anti-ban, key-scope and tier gates as the API, so an agent cannot bypass a limit.

What is not shipped. AI replies, summaries and triage generated by SocialMate remain coming soon. The AI-agent story is hands and memory your own model controls — SocialMate runs no model. Agent Memory stores what your model learned; it does not generate it.

Cost note. Neither surface is billed per call or per message. The meter does not follow you into the API. Full reference at /docs.

Will automating WhatsApp get my number banned?

It can. Bans are possible on every route, official or self-hosted, and no tool — SocialMate included — can guarantee otherwise. What changes between routes is the number of risk factors, not the presence of risk.

What the official channel risks. A WABA number is subject to Meta's quality rating, template pausing and policy review. Those are real enforcement mechanisms even inside the approved channel. Paying Meta does not make you immune to them.

What the self-hosted route risks. A personal number running automation is exposed to WhatsApp's terms-of-service enforcement. SocialMate's anti-ban engine — pacing profiles, per-number limits, session warming, duplicate-content guard, adaptive throttling — reduces the risk profile. It does not eliminate it, and the honest framing matters: “structurally safer” is a claim; “ban-proof” is not one anyone can make.

The practical rule. Keep safety-critical numbers on the official channel, or run the self-hosted route on a separate number you can afford to lose. That is the honest trade. WhatsApp account disabled covers what self-hosting can and cannot change.

Option	Pricing model	Per-message fee	Inbound metered?	Who holds the data	Meta verification required	Ban / account risk
Twilio	Metered — Meta's fees passed through plus a per-message handling fee	$0.005 per message, inbound or outbound (Twilio pricing page, Sept 2026)	Yes — same $0.005 handling fee	Twilio and Meta cloud	Yes	Official channel. Enforcement still applies via quality ratings, template pausing and policy review.
360dialog	Per-number platform licence, Meta fees passed through	Vendor-set platform fee; Meta's per-message rates still apply	Meta send fees apply	360dialog and Meta cloud	Yes	Official channel. A number can be restricted for template quality or policy breaches.
respond.io	Subscription, Meta rates passed through	Vendor subscription on top of Meta's rates	Meta send fees apply	respond.io and Meta cloud	Yes	Official channel. Account restrictions follow quality and policy enforcement.
Wati	No-code plan plus vendor rate card	Vendor rate card applies	Vendor and Meta send fees apply	Wati and Meta cloud	Yes	Official channel. Template quality and opt-out enforcement apply.
Gupshup	Self-serve API billed per message	Vendor per-message rate over Meta's	Vendor and Meta send fees apply	Gupshup and Meta cloud	Yes	Official channel. Quality rating and policy enforcement apply.
SocialMate	Flat licence per device, priced per machine not per message	None at any tier	No — inbound and outbound are not metered	Your own machine, local storage; nothing routed through SocialMate servers	No — your own number, no Meta Business verification	Not the official API; bans are always possible. The anti-ban engine reduces risk, it does not eliminate it.

How to price your WhatsApp messages before choosing a route

1. Pull the two published rates From your provider's pricing page, record Meta's per-message rate for your exact category and destination country, and the provider's own per-message handling fee. Check whether the fee applies inbound as well as outbound.
2. Build your real monthly mix Count delivered messages by category — marketing, utility, authentication, service — and subtract the 1,000 free Service messages per number, which reset monthly with no carryover.
3. Ask for the platform fee in writing Request the recurring per-number or per-seat charge separately from the per-message fee, and confirm whether failed or rejected messages are billable.
4. Test the crossover against your cap Divide the flat licence price by your blended rate. Then check that volume fits inside the flat plan's daily cap after warming — a crossover above your cap is not a saving.

Frequently asked questions

How much does one WhatsApp utility message cost in the US?

A blended $0.0084 through Twilio: Meta's utility rate starting at $0.0034 plus Twilio's $0.005 handling fee, per Twilio's pricing page as of September 2026.

Are WhatsApp Service messages still free?

Only up to 1,000 per business number per calendar month. Per Twilio's Help Center notice, Meta moves Service messages to per-message billing on 1 October 2026. The allowance resets monthly and does not carry over.

Is WhatsApp API pricing per conversation or per message?

Per message. Sendr's 8 October 2026 report states that Meta retired conversation-window billing on 1 July 2025. The 24-hour window still governs what you may send, but it is no longer the billing unit.

At what volume does a flat licence beat per-message pricing?

On sourced US/Canada utility rates, around 980 to 1,190 messages a month — where $99 a year or $10 a month equals the metered cost. Marketing templates shift the crossover lower.

Does a flat licence mean unlimited sending?

No. SocialMate Free allows 200 messages a day on one account; Pro starts at a safe 500 a day and scales to 5,000 after 72 hours of warming through High-Volume Mode. Warming is required, and no volume is risk-free.

Does “no markup on Meta's fees” mean flat-rate?

No. A provider can pass Meta's rates through and still charge a recurring per-number fee. A markup-free meter is still a meter.

Do I need Meta business verification to use SocialMate?

No. SocialMate is a self-hosted app running on your machine with your own WhatsApp number, so there is no Business Portfolio, WABA or template approval. It is not the official API and is independent of Meta.

What happens if my WhatsApp number gets restricted?

Bans are possible on any route, official or self-hosted. SocialMate's risk-based auto-resume can bring a cooled account back, but a restriction is a real outcome. Keep business-critical numbers on the official channel or on a number you can afford to lose.

Is there a per-message fee for SocialMate?

No, at any tier. The local HTTP API runs on Free for read endpoints and plain text send; Pro adds media, groups, polls, scheduled messages, the smart queue and the named tunnel. Nothing is charged per message.

Is SocialMate affiliated with WhatsApp or Meta?

No. SocialMate is independent — not affiliated with, endorsed by, or partnered with WhatsApp or Meta. “WhatsApp” and “Meta” are referenced for identification only.

Where does my WhatsApp data live with SocialMate?

On your machine. Chats and contacts stay in local storage and nothing is routed through SocialMate's servers. Free keeps a live cache; Pro adds full history, unlimited full-text search and a one-shot backfill.

Can I try SocialMate before paying?

Yes. The 7-day Pro trial is opt-in from inside the app, asks only for an email, needs no card, and drops back to Free automatically at expiry with nothing deleted. Free is $0 forever.