// whatsapp api · 30 july 2026
What WhatsApp API
really costs you.
The single most common surprise in a first WhatsApp bill is that the number of messages sent has very little to do with the amount charged. Understanding why makes the difference between a predictable channel and an unpleasant invoice.
// the unit
You are billed per conversation, not per message.
Meta's billing unit is a 24-hour conversation window, not an individual message. Once a window opens between your business and a customer, messages of that category inside those 24 hours do not each add a charge.
This has an immediate practical consequence: sending someone six messages over an afternoon may cost the same as sending one. Businesses that batch their notifications into a single daily digest to save money are often optimising something that was never being charged per item.
It also means a low message count is no guarantee of a low bill. Ten thousand customers contacted once each is ten thousand conversations. One thousand customers contacted ten times each, within the window, is one thousand.
There is one important exception in the other direction: per-message charging applies to certain categories in certain markets, and Meta has been steadily moving the model. Always confirm the current rate card for India before building a forecast on it.
// the multiplier
Category is where the real money is.
Every conversation is classified, and the categories are priced very differently:
Utility — transactional messages about something that already exists: an order confirmation, a delivery update, an appointment reminder, a payment receipt. This is the cheapest category. On WABAPI, utility messages start from ₹0.20.Authentication — one-time passcodes and verification codes. Priced separately, and typically the highest-volume category for any business doing logins over WhatsApp.Marketing — promotions, offers, re-engagement, anything designed to create demand rather than service it. Substantially more expensive than utility, and the category most likely to attract blocks.Service — conversations the customer starts. These behave differently again and are where good support practice quietly saves money.The expensive mistake is having genuinely utility messages classified as marketing, usually because the template was written with a promotional flourish. A line like “and don't forget our monsoon sale!” appended to a delivery notification can move that template into the marketing category permanently.
// estimating
How to estimate your bill before you commit.
Work it out in this order, and you will be close enough to make a decision:
1. Count conversations, not messages. For each use case, how many distinct customers will you open a window with per month? That is your conversation count.2. Split by category. Order updates and reminders are utility. OTPs are authentication. Campaigns are marketing. Be honest here — wishful classification is the main source of forecast error.3. Apply the current rate per category for India from your provider's rate card, and add them up.4. Add the platform fee, if any. This is where providers differ most. A subscription platform such as WhatsBizAPI charges a flat fee and gives you the inbox, chatbot builder, campaign tooling and coexistence mode. A credit model such as WABAPI has no monthly fee at all — you buy credits and pay only for what you send.The crossover is genuinely a matter of volume and how many people work the channel. Below a few thousand conversations a month with nobody sitting in a shared inbox, pay-per-message is usually cheaper. Once several staff are handling conversations daily, the platform earns its fee back on the tooling alone.
// the hidden ones
The costs that are not on the rate card.
Template rejections. Every rejected template is a delay, and a campaign that misses its window has a real commercial cost even though Meta charged you nothing.Quality rating damage. If enough recipients block or report you, your number's quality rating falls, your messaging limits get cut, and in the worst case the number is restricted. Recovering is slow and there is no way to pay to fix it. Aggressive marketing to a poorly consented list is expensive in a way the invoice never shows.The number itself. Historically, moving a number onto the API meant losing the ordinary WhatsApp app on it — a genuine operational cost for a small business where staff use that phone. Coexistence mode removes that trade-off, letting the API and the phone app run on the same number.Integration. The API is not the project. Getting conversations to appear in your CRM, orders to trigger the right template, and delivery receipts to reconcile without duplicates — that is the actual work.// summary
The short version.
Count conversations rather than messages. Classify categories honestly, because that is where the cost multiplies. Keep your utility templates strictly utility. Protect your quality rating as if it were unrecoverable, because in practice it nearly is.
If you want this modelled against your own numbers, send us your rough monthly volume and message mix and we will work out which model is cheaper for you — including when the answer is the one we earn less from. Message us on WhatsApp or email support@noesistech.com.
// next step
Tell us what is actually broken.
A short message is enough to start. The first scoping call is free, and you will be talking to the person who would write the code.