WhatsApp webhook pricing object: type, category and billable (2026)
The pricing object rides on status webhooks and says how Meta classified a message: billable (being deprecated), pricing_model PMP, type (regular, free_customer_service, free_entry_point or free_group_customer_service), category such as marketing, utility, authentication or service, and an optional subtype of paid_exempt. Since 1 October 2026, regular marks every charged message, service messages included.
easyCoexistence connects your WhatsApp Business app number to Meta's Cloud API through Coexistence and passes the status webhooks that carry this object to your server, so your own system can tally usage.
The pricing_model on current webhooks, per-message pricing; CBP appears only on webhooks sent before 1 July 2025.
Delivered service messages per business phone number per month inside Meta's free tier, from 1 October 2026.
The type of a charged message, including service messages delivered after the number's free tier is used.
The subtype on service messages that are free because the organization is an eligible government or non-profit.
Tiering details in webhooks; Meta points to the pricing_analytics field for volume tier information.
Where does the pricing object appear?
Only on statuses, and only on some of them: Meta includes it with the sent status and with one of delivered or read, and a v24.0 example in Meta's reference shows it missing from sent because it came on the delivered webhook instead. Failed statuses never carry it. So treat pricing as a property of the message, keyed by its wamid, and record it once whichever status brings it. Meta's own examples of the object for a service message, before and after the number's monthly free tier runs out:
// Service message delivered while the number is within its free tier
"pricing": {
"billable": false,
"pricing_model": "PMP",
"type": "free_customer_service",
"category": "service"
}
// Service message delivered after the number's free tier has been used
"pricing": {
"billable": true,
"pricing_model": "PMP",
"type": "regular",
"category": "service"
}What do the type values mean since 1 October 2026?
type is the field that answers whether Meta charges. Its meaning shifted on 1 October 2026, when Meta started charging per message for service messages and for utility templates sent in reply to a customer. Code written before that date may read free_customer_service as a reply in the open window; it now means a one-to-one service message within the number's monthly free tier. billable still appears but Meta says it will be deprecated, and asks you to read type and category together.
| Through 30 Sep 2026 | From 1 Oct 2026 | |
|---|---|---|
| regular | A billable message | Billable, now including utility replies to customers and service messages past the number's monthly tier |
| free_customer_service | A utility template or non-template message sent in an open window | A one-to-one service message within the number's monthly tier |
| free_group_customer_service | Group utility or non-template message in an open group window | A group service message within the number's monthly tier |
| free_entry_point | Sent in an open free entry point window | Unchanged |
Which categories can a message have?
category names the rate Meta applied when it charges, and it is the field to group by when you reconcile against Meta's invoice, together with the country of the customer's number, since rates vary by market. One message has one category and only one charge: a non-template message with promotional content is still a service message, never an extra marketing charge. The values Meta lists:
How do you count charges from webhooks?
Webhooks tell you which messages are billable and at which category, not what they cost. To build a usage view that matches Meta's billing, count by message and by category, then apply Meta's published rates for each market, or read Meta's pricing_analytics field, which gives per-message breakdowns and tiering.
- Deduplicate on the wamid, since pricing can ride on more than one status and retries repeat webhooks.
- Count a message as charged when type is regular; group by category and the recipient's country.
- Ignore failed messages: Meta charges for delivered messages only.
- From v24.0, expect no conversation object except inside a free entry point window, where its id is unique per window.
What does it mean for AI replies on a Coexistence number?
Every reply your AI or an automation sends through the API is a non-template message, so its category is service: within the number's monthly free tier it shows free_customer_service, and after that, regular. Templates your AI sends with send_template carry their own category. Meta's Coexistence guide adds one difference that matters for cost: messages the owner types in the WhatsApp Business app are not subject to the customer service window and do not affect Cloud API pricing.
Meta bills messages to the business's own WhatsApp Business Account, per message, by category and country; easyCoexistence never marks them up, and AI usage is billed by your AI provider on your own key.
Common mistakes
- Counting the pricing object every time it appears. It can come on more than one status of the same message; count once per wamid.
- Reading billable alone. Meta is deprecating it and asks you to use type and category together.
- Keeping the pre-October reading of free_customer_service. Since 1 October 2026 it marks a service message inside the number's monthly free tier.
- Expecting amounts in the payload. The object names the category; rates come from Meta's rate cards or pricing_analytics.
Meta's charges stay on your own WhatsApp Business Account and are never marked up. US$ 9 down to US$ 0.75 per number per month, falling as you add numbers, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Which account pays for a message?
The WhatsApp Business Account that sent it. When several accounts send on one number, Meta attributes each charge to the account that sent that message, with its own payment method and spend limits.
What is marketing_lite?
The category and type of pricing for messages sent through Meta's Marketing Messages API for WhatsApp, a separate sending path for marketing templates with its own pricing options, such as a maximum price per delivery.
When did per-message pricing replace conversations?
On 1 July 2025. Webhooks sent before that date can show pricing_model CBP, conversation-based pricing; later ones show PMP. Code that still groups charges by conversation id needs updating.
Does the free tier reset every month?
Yes. Meta gives each business phone number 1,000 delivered service messages per month, with no roll-over, reset at midnight in the WhatsApp Business Account's time zone.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on