How much does the official WhatsApp API cost? The 3 costs (2026)

The cost of Official WhatsApp API adds three layers: the fee that Meta charges per template message delivered (varies by category, country and volume), the monthly fee for the BSP or platform that provides access to the API and, often, a setup fee. Customer-initiated service is free within a 24-hour window. Below, each decomposed layer — and the scenario in which a extension at no cost per message delivers the same result for a fraction of the cost.

Tier 1: Meta's per-message rate

Since July 1, 2025, Meta charges the API per template message delivered, and no longer for a 24-hour conversation. The current model is described in the official pricing documentation for the WhatsApp Business Platform for developers (Meta, consulted in Jul/2026) and works like this: each active message sent from an approved template is classified into a category, and each category has a price per country — Brazil has its own table.

Category	What is it	Example	How it is charged
Marketing	Promotional content sent by the company	Offer, launch, cart recovery	Per message delivered — it is the most expensive category in the table
Utility	Transactional message linked to a customer action	Order confirmation, delivery status	By message delivered; Free if sent within an open fulfillment window
Authentication	Account Verification Codes	Login OTP	By message delivered, with volume discount ranges
Service	Responses within the 24-hour window opened by the customer	Service, questions, support	Free and unlimited

There is also a free rule that changes the advertiser's account: messages exchanged within the 72-hour window opened by click ads for WhatsApp on Facebook and Instagram are not charged^[1].

We prefer not to reproduce the entire table here: Meta reviews the values ​​periodically — always consult the official developer pricing page. Verified reference values (with source and date) are in how much does it cost to send bulk messages on WhatsApp. What doesn't change is the logic: marketing is expensive, utility and authentication cost less, and service within the 24-hour window is free.

Tier 2: the BSP or platform monthly fee

In practice, almost no one operates the "raw" API. Even with the Cloud API hosted by Meta, you need an interface to serve, send messages and integrate — and that's where BSPs (Business Solution Providers) and service platforms come in. This second layer appears in four billing models, alone or combined:

• Fixed monthly fee by the platform, regardless of volume;
• Billing per attendant, the active "seat" per month;
• Markup per message: a percentage added to the Meta fee for each shipment;
• Setup rate to set up the account, verify the company and approve the first templates.

Price surveys published by Brazilian providers such as Umbler and SocialHub (Jul/2026) show entry plans in the region of a few hundred reais per month and corporate contracts that exceed thousands — the distance between one extreme and the other is enormous. Before signing, ask the question that separates a good proposal from an expensive one: "Is the rate per message you send the same as the Meta table or is there a markup?"

Layer 3: costs that do not appear in the budget

• Integration and development. Connecting the API to your ERP, e-commerce or CRM requires developer hours — in-house or contracted.
• Templates. Every active message outside the window requires a template pre-approved by Meta. Writing, submitting and redoing disapproved templates consumes the team's time.
• Dedicated number. A number registered with the API stops working in the app and on WhatsApp Web. The migration is not a five-minute rollback test.
• Training. The team now works through a new platform, not through the WhatsApp they already know.

The formula to calculate your bill

With the official Meta table open, the estimate is a multiplication:

Monthly cost ≈ (marketing messages × marketing fee) + (utility outside the window × utility fee) + platform monthly fee + markup and diluted setup.

The blind spot in most budgets is marketing volume. Four campaigns per month for a base of 2,000 contacts are 8,000 messages charged in the most expensive category in the table — before any monthly fee. That's why operations sending promotional messages via the API see their invoice grow in the same proportion as the contact base, while pure service operations (customer calls, company responds) almost only pay for the platform.

When the official API pays off

Honesty: there are operations where the API is the right choice and an extension like Zapext does not fit the bill. It's worth paying the bill when you need:

• Transactional notifications at scale — confirmations, tracking and charges triggered by the system, thousands per day, in the utility category (cheap or free in the window);
• Chatbot integrated into systems, checking orders, stock or invoice in real time;
• Large service teams, with dozens of attendants, SLA and formal supervision;
• Verified account badge and official templates, a common requirement in banks, healthcare and large retailers;
• Massive promotional send with formal opt-in: API is the only path authorized by Meta for high-volume active messaging^[2].

In these scenarios, the cost per message is the price of operating within the rules — and it usually pays for itself.

When a no-cost extension per message resolves

Now reverse the picture: your operation is human service, follow-up of proposals, sales funnel and specific campaigns for a base that already knows your company. In this profile — that of most SMEs — the API charges a lot for resources that you don't use. An extension that runs on top of WhatsApp Web, like Zapext, costs R$29/month on Starter and R$59/month on Plus (with 4 users), at no cost per message: CRM Kanban for the funnel, quick responses, scheduling, chatbot based on rules without AI, sending messages with gradual sending and, in Plus, webhooks for HubSpot, RD Station and Google Sheets. More than 3,000 companies use it, with a 7-day guarantee.

Honesty goes both ways: the extension does not have a verified badge, does not use official templates and does not replace the API for transactional notification at scale. And sending aggressive promotional messages to a common number violates WhatsApp's messaging policy and risks banning^[2] — that's what gradual shipping is for, and that's why we maintain a guide to bulk messaging without blocking.

API or extension: the decision ruler

Your reality	Best cost path
Customer initiates most conversations; team of 1 to 4 people	Extension — low fixed cost, no per-message fee
Thousands of automatic notifications per day, integrated into the system	Official API — cheap or free utility in the window
Occasional campaigns for your own base, a few times a month	Extension with gradual shipping
sending promotional messages in high volume with formal opt-in	Official API — single authorized path
Requirement for verified seal or formal compliance	Official API

Want the full comparison, feature by feature and cost by cost? See extension for WhatsApp Web vs official API. And if your question is volume of campaigns, the bulk message sending shows how gradual shipping works in practice.

Sources

1. [1] Click-to-WhatsApp Ads on Facebook and Instagram — Meta for Business (2024). accessed 2026-05-19.
2. [2] WhatsApp Business Messaging Policy — WhatsApp (2024). accessed 2026-05-19.