Marketing Messages API for WhatsApp: what Meta claims, what it needs and what to ask

The WhatsApp Marketing Messages API is a second route Meta offers for sending marketing templates. Same phone number, same approved templates, a different endpoint, and Meta’s promise that messages people are likely to read get delivered more often.

Mrinal Borah runs marketing for a tea brand in Guwahati (an invented example). Her festive campaign went to 22,000 opted-in customers and a couple of thousand came back undelivered with error 131049. Her provider’s account manager mentioned that “the MM API might help”. She had never heard of it, and she couldn’t tell from the dashboard which route her campaigns were using.

That gap is common. This page sets out what Meta’s own documentation says, as read on 13 October 2026.

What is the Marketing Messages API for WhatsApp?

It is an endpoint, /marketing_messages, that sits next to the normal Cloud API /messages endpoint and accepts marketing templates only. Meta’s overview, updated 30 June 2026, describes it as “an API for sending marketing messages on WhatsApp that optimizes delivery to reach more of the people most likely to find your messages relevant.”

It was formerly known as the Marketing Messages Lite API, and the changelog records it as generally available on 19 November 2025.

It is an addition to the Cloud API. Meta’s onboarding page says the two “are used together on the same phone number”: the Cloud API keeps handling utility, authentication and service messages and everything customers send you, while the new endpoint carries marketing. Onboarding “requires no new phone-number registration or template re-creation.”

How is it different from sending marketing templates through the Cloud API?

The template and the price list are the same. What changes is how Meta decides delivery, plus a set of extras that exist only on this route. Meta’s features page compares them directly:

	Marketing Messages API	Cloud API
Message types	Marketing templates only	Authentication, utility, service and marketing
Delivery decisions	Factors in whether a message is high engagement	”Message quality does not factor into per-user marketing message limits”
Message expiry (time-to-live) for marketing	Yes, from 12 hours to 30 days	Only for authentication and utility
GIF header, Android app deep links	Yes	No
Benchmarks and recommendations	Yes	No
Conversion metrics (website and app events)	Yes	No
Sent, delivered, read and clicked counts	Yes	Yes
Automatic creative optimisations	Yes, as a pilot	No

The time-to-live is the feature a non-technical owner will understand fastest. A “sale ends tonight” message that reaches a phone two days later, when it finally comes back online, does more harm than good. With an expiry set, WhatsApp stops trying.

If a request to the new endpoint carries anything other than a marketing template, Meta’s error table returns 131055, “Only marketing template messages are supported”. That’s why Meta published a routing guide on 24 September 2026 telling developers to keep an up-to-date map of each template’s current category, since a template approved as utility can be moved to marketing later. Our guide to message categories explains how Meta draws that line.

What does Meta claim about delivery?

Meta claims up to 9% more delivered messages for high-engagement marketing, measured in its own test. The features page says the API “factors whether a message is high engagement into delivery decisions, delivering up to 9% more messages versus Cloud API”, and defines a high-engagement message as one “that users expect, that is relevant and timely, and that is therefore more likely to be read and clicked.”

The test behind the number is described in a footnote: “Meta conducted an AB test with approximately 12 million delivered marketing messages sent by advertisers in India between January 1, 2025, and January 31, 2025. The test compared MM API for WhatsApp optimized delivery to standard Cloud API delivery for high engagement messages only”.

Read the footnote closely before you repeat the number.

It was run on Indian traffic, which makes it more relevant to an Indian sender than most vendor statistics. It is also Meta’s test of Meta’s product, from January 2025, and the wording is “up to”. And it covers high-engagement messages only. Meta doesn’t publish a figure for campaigns people tend to ignore, and nothing on the page suggests the route rescues those.

How does it interact with the per-user marketing limit?

Meta does not say the API lifts the per-user limit. WhatsApp caps how many marketing templates one person receives across all businesses, and reports a capped message as error 131049, as our 131049 explainer covers in full.

What Meta does say is narrower. On the Cloud API, message quality “does not factor into per-user marketing message limits”, and there is “no ability to increase delivery for high engagement messages”. On the Marketing Messages API, engagement is part of the delivery decision. Read together, the benefit goes to messages your customers tend to open. A list that hasn’t read your last five campaigns should expect the same failures on either route.

One line on the get-started page helps explain the mechanism. For the European Economic Area, the United Kingdom, Japan, South Korea, Nigeria, South Africa and Thailand, messages “will not receive delivery optimizations”, and Meta adds that per-user limits “are also not active in these countries”. India is not on that list. Meta treats the optimisation and the cap as a pair in those countries, and nothing on the page exempts India from either.

The sending habits that keep delivery healthy don’t change with the endpoint. They are in our guides to sending bulk WhatsApp messages without getting banned and messaging limits.

What does it require?

It requires an eligible account, a one-time acceptance of Meta’s terms, and an approved marketing template. Meta’s pages list:

• A WhatsApp account that is “active and not restricted from messaging due to any violations”, with the account’s tax country and the owning business’s country outside sanctioned regions.
• Compliance with the WhatsApp Business Messaging Policies, including restrictions on some industries that vary by country. Meta says these requirements may change.
• A business phone number registered on the Cloud API. Numbers that aren’t on the Cloud API can’t use it.
• Acceptance of the Marketing Messages API Terms of Service. If you work through a provider, someone “with full control to the business portfolio” does this in WhatsApp Manager, under Overview, in the Alerts section, by clicking “Accept terms”. Businesses that integrate directly accept in the App Dashboard.
• At least one approved marketing template and a subscription to the messages webhook.

On ad accounts, the page is specific: “When a business registers for the MM API for WhatsApp, Meta creates linked read-only ad accounts and links each to the marketing templates under the business portfolio.” You don’t need to run ads, and Meta’s measurement page says “No action is needed on the part of the business or partner”. The ad accounts exist so that campaign numbers can appear in Meta’s reporting tools.

One more consequence of onboarding deserves attention before anyone clicks Accept. Meta says that once you’re onboarded, “message status events (delivery status, read, clicked) will automatically be shared with Meta as part of event activity”, used “solely to optimize the performance of marketing campaigns”, and that “Meta does not sell your or your subscribers’ data”. You can switch the sharing off in the WhatsApp Business account settings or per message. If your business has made privacy commitments to customers, show this paragraph to whoever owns them.

What does it cost?

Meta says the API has the “same billing model as Cloud API”. The platform pricing page, updated 30 September 2026, covers both routes in one rate card, and to Indian numbers the published marketing rate is ₹0.8631 per delivered message before GST. Our October 2026 cost guide has the full table.

The difference is an option called max price, which exists only on this route and is still marked beta. Meta’s page on it, updated 6 October 2026, says you can set the most you are willing to pay per marketing delivery and “Meta will charge that max price or lower”. In the API it is a bid per 1,000 deliveries, in paise for rupee accounts. Meta suggests three uses: the same as the published rate to lower costs at similar delivery, lower than the rate to reach more people cheaply, or higher than the rate “to increase delivery rates during periods such as holidays and peak sales periods.”

The rollout dates on that page matter for planning:

• Limited beta from 15 May 2026.
• Open beta from 1 October 2026, when any partner can enable it for all its clients.
• General availability “as of Q2 2027”, when, Meta writes, the max price feature “will become required in eligible geographies and fixed, published rates for marketing messages will only apply on the Cloud API.”

Meta itself calls max price “an early-stage feature” whose performance may vary. Its pages don’t say which geographies will be “eligible”, though the testing advice on the same page mentions India by name. Whether your provider adds a fee of its own for this route is something only the provider can tell you.

What can you measure?

You get the usual sent, delivered, read and clicked counts, plus three things the Cloud API doesn’t report. Benchmarks compare your read and click rates with “similar templates from other businesses in your region”. Recommendations suggest changes to a template. Conversion metrics tie website or app events such as add to cart and purchase back to the message.

Conversion reporting isn’t automatic for everyone. Meta lists “a Meta Pixel or Conversions API integration” as required for it, and says businesses already sending those events for ads get the reporting with no extra setup. If you run ads and marketing messages in the same portfolio, a purchase is credited to the last Meta touch before it, either the ad click or the message click.

Meta lists four places to see the numbers: WhatsApp Manager, the WhatsApp Business Management API, the “Marketing Messages” tab in Ads Manager, and the Marketing API’s Insights API. On 23 September 2026 it also documented a webhook that fires when a link in a marketing message opens a landing page in WhatsApp’s in-app browser.

The automatic creative optimisations need a decision from you. They let Meta adjust how your message looks, for example filtering a header image, reformatting text or pulling out a headline. Meta reports an average 13.9% rise in click-through rate from them in a test of over 50 million messages from about 200 advertisers between 1 December 2025 and 7 January 2026. Since 21 April 2026 they are disabled by default at the account level, and you opt in through the API or WhatsApp Manager. A brand with strict creative guidelines may want to leave them off.

What should you ask your provider?

Most Indian businesses reach WhatsApp through a provider’s dashboard, and Meta’s page says that in that case “your partner will take care of integrating” with the API’s sending functions. So the useful questions go to the provider:

1. Do my marketing campaigns go through the Marketing Messages API or the Cloud API today? Meta’s status webhook marks messages on this route with the category marketing_lite, so the provider can check.
2. Has anyone in my business accepted the Marketing Messages API terms? If so, who, and when?
3. Is message activity sharing switched on for my account, and can I turn it off?
4. Are automatic creative optimisations on or off for my templates?
5. Can I set an expiry time on a festive campaign?
6. Do you support max price, and what is your plan for Q2 2027 when Meta intends to make it required in eligible geographies?
7. Do you charge anything extra for this route?

A provider that can answer the first question in one line has thought about the rest.

For the wider picture of consent, list building and campaign timing, start with our WhatsApp marketing guide for India, and keep the glossary open for the terms.