WhatsApp Max Price: What Meta Documented for Marketing Messages (and What It Did Not)

WhatsApp max price is not a new India rate card. It is a delivery cap on the Marketing Messages API: you tell Meta the most you will pay per marketing delivery, and Meta charges that amount or less. The October 2026 Cloud API rate-card update is a different document. This page is the max-price document — what Meta wrote, the bid math for INR WABAs, and the three facts it still has not published.

Primary: Set a max price for marketing messages (BETA) (updated 31 August 2026). Companion: Updates to pricing. October Cloud API card: 1 October 2026 pricing update. Cost guide: WhatsApp API pricing.

Start here if you are in a hurry

• WhatsApp max price lives on the Marketing Messages API, not on ordinary Cloud API /messages sends.
• You express the cap as bid_amount per 1,000 deliveries in the WABA currency’s smallest unit (paise for INR).
• India example Meta publishes: ₹0.87 per delivery → bid_amount 87000.
• Optional bid_country_multiplier_overrides scale that bid by destination ISO country (Meta’s sample uses IN: 1.2).
• bid_spec was replaced by optimization_spec on 18 June 2026; bid_spec stopped working after 31 July 2026.
• From Q2 2027 Meta says max price becomes required in eligible geographies. It has not named those geographies.
• Ominiflow Cloud API traffic still bills the published category × country card (India marketing ₹0.86 — verify live). Max-price campaigns are an MM API choice, not a silent change to every template you send today.

What WhatsApp max price actually is

Meta’s sentence is short: set a maximum price per marketing message delivery; when a max price is set, Meta charges that max price or lower. You can set the cap at, below, or above the published marketing rate depending on the job:

• At the card — hold delivery close to today’s campaigns while locking a ceiling.
• Below the card — accept lower delivery to reach cheaper cohorts.
• Above the card — pay more to push delivery in peak windows (festive, flash sale).

A second tool — reach estimation — is meant to show delivery and cost at different caps before you commit volume. Meta flags the whole feature as early-stage: performance varies while the delivery system learns.

This is not a replacement for utility, authentication, or (from 1 October 2026) service billing. Those stay on the Cloud API rate card. Mixing the two invoices in one spreadsheet is how finance loses the plot.

Cloud API vs Marketing Messages API

The sentence most vendor pages skip is in Meta’s GA line: when max price is generally available, fixed, published rates for marketing messages will only apply on the Cloud API.

If you POST a template that has optimization_spec (or the retired bid_spec) to Cloud API /messages, Meta returns: marketing templates containing that object are not supported there — send them to the Marketing Messages API instead.

Ominiflow is a Cloud API BSP. Broadcasts, cart flows, and COD templates on the platform bill the published card unless you separately enrol a WABA on MM API. Ask on the invoice which endpoint sent the traffic before you treat a “max price” slide as your 2027 cost model.

India bid math

bid_amount is the max price per 1,000 deliveries, in the smallest unit of the WABA currency. For an INR WABA that unit is paise.

1. Pick the per-delivery ceiling you will actually pay (example: ₹0.87).
2. Convert to paise: 87.
3. Multiply by 1,000: 87000.

That 87000 sits next to bid_strategy: LOWEST_COST_WITH_BID_CAP — currently the only strategy Meta documents.

Set the bid on the template. Meta’s own warning: scaling every send with per_message_bid_multiplier instead of raising the template bid_amount can deliver worse than the equivalent template-level bid, even when the effective cap is the same. Use the per-message multiplier for one-off adjustments, not as a bulk workaround.

The country multiplier Meta documented (and did not explain)

Inside optimization_spec you may pass bid_country_multiplier_overrides: a map of ISO 3166-1 alpha-2 codes to multipliers. Unlisted countries use 1.0. Constraints Meta lists: up to 50 entries; each multiplier > 0 and ≤ 10; keys must be valid country codes.

Meta’s sample includes "IN": 1.2, "MX": 0.8. Its A/B test recipe also treats India and Saudi Arabia differently: test arm C is 1.5× the rate card globally, but 1.2× for India and Saudi Arabia.

What the page does not say: why India’s suggested test multiple is 1.2 rather than 1.5; whether 1.2 is a delivery-system prior or a policy hint; whether Q2 2027 “eligible geographies” include India. A multiplier is a lever. It is not a reason. Treat the sample as syntax, not a recommended India bid.

Three things Meta has not published

1. Which geographies become mandatory in Q2 2027. “Eligible geographies” is the entire GA sentence. There is no ISO list, no “Rest of Asia Pacific” footnote, no India yes/no.
2. What the floor looks like when the cap is required. Today you can omit optimization_spec and stay on the card. GA says max price becomes required in those unnamed geos. Required at what default? Card? Zero delivery until you bid? Not written.
3. How Cloud API marketing and MM API marketing coexist on one WABA after GA. Published rates “only apply on the Cloud API” implies two marketing meters. It does not say whether a single template can still be sent both ways, or whether festive volume must move to MM API to remain deliverable.

Until those three exist on the developer site, any “WhatsApp will become an ads auction in 2027” slide is a hypothesis. The documented split is: Cloud API keeps a card; MM API grows a cap.

Who can use it in 2026

• Active WABA onboarded to the Marketing Messages API for WhatsApp.
• Country eligible for MM API (Meta’s eligibility list — not the Cloud API country card).
• Limited Beta: sign the testing legal agreement; Solution Partners allowlist end-businesses (raised from 5 to 15 during beta).
• Error 100 if you send without signing that agreement.

Meta’s test recipe: four arms, ~10,000 send requests each, similar audience and window — no max price; at card; 1.5× card (1.2× IN/SA); 0.9× card. Ramp a new max-price template slowly. That is the same pacing advice as ordinary template warm-up.

What Indian teams should do now

• Do not rebuild Cloud API automations (COD, shipped, OTP) for max price. Those are not marketing-MM-API jobs.
• Separate the marketing budget line from utility. October 2026 already bills in-window utility; max price is a 2027 marketing-path question.
• If you already sit on MM API, update create/retrieve/update calls to optimization_spec (the bid_spec grace period ended 31 July 2026).
• Ask your BSP which endpoint sends festive broadcasts. If the answer is Cloud API /messages, your 2026 cost model is still the published card — Ominiflow pricing, Meta at cost.
• Re-read the live max-price page before any Q2 2027 contract clause. This article is a reading of the 31 August 2026 text, not a rate guarantee.

Related reading

• WhatsApp API pricing update October 2026 — service billing, standalone markets, authentication-international
• WhatsApp API pricing cost guide — two invoices: Meta + BSP
• WhatsApp free entry point window — 72-hour CTWA exception (not max price)
• Tech Provider vs Solution Partner — who invoices API usage

FAQ