WhatsApp API pricing in 2026

WhatsApp API pricing is confusing because there are two different bills hiding under one phrase.

There is Meta pricing. Then there are platform fees.

Meta pricing is the fee Meta charges for WhatsApp template messages. Platform fees are what your provider charges for WhatsApp infrastructure: API access, included messages, overage, connected numbers, webhooks, logs, tooling, inbox operations, Flows, workflow automation, and support.

This guide was last reviewed on June 7, 2026. Always verify live plan details on the current Kapso pricing page and current Meta rate cards before making buying decisions.

The simple model

When evaluating WhatsApp API pricing, separate two layers:

The most common mistake is comparing a provider’s platform fee as if it included Meta’s template fees. It usually does not.

Meta pricing

As of Meta’s May 21, 2026 pricing documentation, Cloud API and Marketing Messages API pricing works like this:

• Meta charges when a template message is delivered.
• Template rates vary by the recipient’s country calling code and the template category.
• The main categories are marketing, utility, and authentication.
• Non-template messages, such as text or media replies, are free inside an open 24-hour customer service window.
• Utility templates delivered inside an open customer service window are free.
• The 24-hour customer service window starts when the user messages the business and resets with each new user message.
• Free entry point windows are special cases. They can make messages free for up to 72 hours when the user enters from supported ads or Facebook Page entry points. Do not model that as the default service window.
• Utility and authentication messages can have volume tiers.

The rate card is not one global number. For example, in Meta’s USD rate card effective April 1, 2026:

Those are Meta fees. They are separate from your provider’s platform fees.

Platform fees

Providers charge differently for the platform layer.

Twilio’s public WhatsApp pricing uses a $0.005/message platform fee for inbound and outbound WhatsApp messages, plus Meta template fees.

Kapso uses plan-based included usage:

• Free: $0/month with 2,000 messages included.
• Pro: $25/month with 100,000 messages included.
• Platform: $299/month with 1,000,000 messages included.
• Pro overage: $0.002/message.
• Platform overage: $0.001/message.

That means you should compare two things separately:

1. Meta fees: delivered templates, category, country, service window, free entry point status.
2. Platform fees: per-message fee, included-message plan, overage, connected numbers, product capabilities.

The pricing update that changed the mental model

Older WhatsApp pricing was usually explained around 24-hour conversation categories. That mental model is no longer enough.

Meta’s July 1, 2025 pricing update moved WhatsApp from conversation-based pricing to per-message pricing. Twilio also notified customers that the update shifted from the old 24-hour conversation-based model to a model that charges per delivered template message.

The current operating rules are:

• Marketing, utility, and authentication template messages are priced when delivered.
• Non-template messages are free inside an open customer service window.
• Utility templates delivered inside an open customer service window are free.
• Free entry point windows are a special ads/Page-entry case and can last longer than the normal 24-hour customer service window.
• Conversation-based pricing is deprecated.
• Rates can vary by country and may include volume tiers.

Model each outbound message’s trigger context before sending: inside or outside the customer service window, template or non-template, template category, recipient country, and whether a free entry-point window is open.

Kapso pricing at a glance

As of the current Kapso pricing page:

Other notable limits:

• Free includes 1 connected phone number plus Kapso sandbox.
• Pro includes 3 connected phone numbers, then additional numbers are billed.
• Platform includes 50 connected phone numbers, then additional numbers are billed.
• Digital phone numbers are included, meaning Kapso-provided virtual numbers for WhatsApp setup where supported.

Overage model

Kapso’s published overage model is:

For connected numbers:

Treat included messages as included usage, not as a hard architectural boundary. Production teams should monitor usage and understand how overages are billed before they run high-volume campaigns or agents.

Kapso vs Twilio on high-volume WhatsApp

Kapso’s pricing page compares Twilio’s $0.005/message platform fee with Kapso’s included-message plans:

This table compares platform fees only. Meta template fees are separate and should be modeled from Meta’s current rate card.

What to calculate before choosing a provider

Before choosing a WhatsApp API provider, calculate:

1. Monthly inbound and outbound messages.
2. Percentage of messages sent inside the customer service window.
3. Template sends by category: utility, authentication, marketing.
4. Recipient countries.
5. Number of connected WhatsApp phone numbers.
6. Number of customers or tenants that need their own number.
7. Webhook and workflow volume, if your provider prices those separately.
8. Engineering time needed to build onboarding, logs, retries, and inbox operations yourself.

The last item is usually undercounted. WhatsApp infrastructure gets expensive when your team has to debug onboarding, templates, webhooks, and delivery without a coherent operating layer.

A practical buying rule

Use a broad CPaaS when WhatsApp is one of many channels and you mostly need programmable messaging.

Use a WhatsApp-focused platform when WhatsApp is the product surface: customer-owned numbers, embedded signup, webhooks, workflows, AI agents, templates, Flows, logs, and human handoff all matter.

Kapso is built for the second case.