--- title: "WhatsApp Marketing Messages API (MM Lite): 2026 Guide" description: "WhatsApp Marketing Messages API explained: what it is, how it differs from Cloud API marketing templates, the 2027 sunset dates, eligibility and metrics." canonical: "https://omnichannels.ai/blog/whatsapp-marketing-messages-api/" language: "en" updated: "2026-11-06" publisher: "BroadNet Technologies" brand: "OmniChannels.ai" category: "whatsapp" primaryQuery: "whatsapp marketing messages api" keywords: ["mm lite whatsapp", "marketing messages lite api", "whatsapp cloud api marketing sunset", "whatsapp marketing_messages endpoint", "whatsapp delivery optimization", "whatsapp marketing template migration", "whatsapp max price marketing"] published: "2026-11-06" author: "OmniChannels.ai Editorial Team" reviewer: "BroadNet Messaging Solutions Team" readingMinutes: 9 answer: "The Marketing Messages API for WhatsApp is Meta's send-only API for marketing templates, the successor to sending marketing messages through Cloud API. It adds quality-based delivery, message validity (TTL), benchmarks and conversion metrics. Meta says Cloud API stops accepting marketing messages on 13 October 2027, so businesses that send promotions need to route them to the new endpoint. Utility, authentication and service messages stay on Cloud API." takeaways: ["The Marketing Messages API for WhatsApp (often called MM Lite) is a separate send endpoint for templates in the MARKETING category; everything else, including inbound messages, stays on Cloud API.", "Meta's documentation dates the change: general availability on 19 November 2025, new accounts created on or after 13 April 2027 cannot send marketing through Cloud API, and Cloud API marketing sending stops on 13 October 2027.", "Quality-based delivery, customisable message validity of 12 hours to 30 days, benchmarks, recommendations and conversion metrics are features of the new API; basic marketing formats such as media, carousel and flow templates work on both.", "Meta says the billing model is the same as Cloud API; businesses can optionally set a maximum price per delivered marketing message, and Meta then charges that amount or less.", "Some features are not active everywhere. Meta lists the European Economic Area, the UK, Japan, South Korea, Nigeria, South Africa and Thailand as having no delivery optimisations, and marketing messages to US numbers are not delivered."] faq: - q: "What is the Marketing Messages API for WhatsApp?" a: "It is Meta's API for sending marketing template messages on WhatsApp with extra optimisations. You send approved marketing templates to a dedicated marketing_messages endpoint instead of the standard messages endpoint. Meta describes it as the successor to marketing messages on Cloud API and says it uses the same billing model." - q: "What is MM Lite?" a: "MM Lite is short for Marketing Messages Lite, the name partner documentation and earlier articles use for this API. Meta's current documentation calls the product the Marketing Messages API for WhatsApp, and its status webhooks label such messages marketing_lite, so the names refer to the same product." - q: "When does Cloud API stop supporting marketing messages?" a: "Meta's overview page says Cloud API stops supporting marketing messages on 13 October 2027, when sending a marketing message through Cloud API returns an error. Accounts created on or after 13 April 2027 cannot send marketing through Cloud API at all. Check Meta's page, because dates and exceptions can change." - q: "Do I need to change how I send utility or authentication templates?" a: "No. Meta states that service, authentication and utility messages stay on Cloud API. The change affects templates whose category is MARKETING. The one trap is reclassification: if Meta recategorises a utility template as marketing, it must then be sent through the marketing endpoint." - q: "Is the Marketing Messages API cheaper than Cloud API?" a: "Meta says it uses the same billing model as Cloud API, and rates come from Meta's rate card for the recipient's market. The optional maximum price feature lets you cap what Meta charges per delivered marketing message. Do not assume savings; compare the delivered results and charges for your own campaigns in Meta's current pricing documentation." - q: "Does OmniChannels.ai support the Marketing Messages API?" a: "Ask our team. BroadNet is an official Meta Business Solution Provider and sends WhatsApp marketing templates today, but support for this specific API and its optimisations should be confirmed with us for your account before you plan a migration around it." sources: - title: "Marketing Messages API for WhatsApp: overview, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/marketing-messages/overview" - title: "Marketing Messages API for WhatsApp: features, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/marketing-messages/features" - title: "Marketing Messages API for WhatsApp: get started and geographic availability, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/marketing-messages/get-started" - title: "Route template messages, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/marketing-messages/route-template-messages" - title: "WhatsApp Business Platform pricing, Meta for Developers" url: "https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing" --- # WhatsApp Marketing Messages API (MM Lite): 2026 Guide Canonical: https://omnichannels.ai/blog/whatsapp-marketing-messages-api/ Language: en Publisher: OmniChannels.ai by BroadNet Technologies This guide is for marketing leads, CRM owners and developers who send WhatsApp promotions and have heard that Meta is moving marketing messages to a new API. It explains what the Marketing Messages API is, which dates matter, how it differs from sending marketing templates on Cloud API and what to do now. It follows Meta's developer documentation as of 6 November 2026; confirm details there before you commit to a plan. ## What is the Marketing Messages API for WhatsApp? The Marketing Messages API for WhatsApp is Meta's send-only API for marketing template messages. Meta describes it as the successor to marketing messages on Cloud API, with optimisations designed to reach the people most likely to find a message relevant. It is often called MM Lite, the name partners and earlier articles use for it. Three points define it: - **It is a separate endpoint.** Marketing templates go to `//marketing_messages` instead of `//messages`. - **It is for MARKETING templates only.** Meta says other categories go to the usual messages endpoint. - **It sits beside Cloud API.** You still use Cloud API to receive customer messages and webhooks, and to send service, utility and authentication messages. If you are new to the underlying pieces, start with [how to send WhatsApp marketing messages](/blog/how-to-send-whatsapp-marketing-messages/) and our guide to [WhatsApp template categories](/blog/whatsapp-template-categories-approval/). ## What are the key dates for the change? Meta's overview page gives four dates: general availability on 19 November 2025, a global announcement on 13 October 2026, a cut-off for new accounts on 13 April 2027 and the sunset of marketing on Cloud API on 13 October 2027. | Date | What Meta says happens | |---|---| | 19 November 2025 | The Marketing Messages API for WhatsApp becomes generally available after an open beta | | 13 October 2026 | Global announcement that Cloud API will stop supporting marketing messages | | 13 April 2027 | New messaging accounts created on or after this date cannot send marketing messages through Cloud API; earlier accounts keep access until the sunset | | 13 October 2027 | Sending a marketing message through Cloud API returns an error; service, authentication and utility are unaffected | Meta also notes that most integrations take about two weeks to move to the new endpoint. Treat that as an estimate for a simple integration; budget longer if you have several systems, approval steps or a provider between you and Meta. ## How is it different from marketing templates on Cloud API? The templates and phone numbers are the same, but the new API adds delivery and measurement features that Cloud API marketing messages do not have. Meta states that existing phone numbers and marketing templates can be reused. Meta's feature table compares the two. These rows are the ones that change day-to-day marketing work: | Capability | Marketing Messages API | Cloud API (marketing) | |---|---|---| | Quality-based delivery | Factors message engagement into delivery decisions | No; per-user marketing limits do not consider message quality | | Message validity (TTL) | 12 hours to 30 days, then undelivered messages expire | Limited to authentication and utility | | Creative optimisations | Pilot: automatic image and text adjustments | No | | Animated GIF header | Yes | No | | Android app deep links | Yes | No | | Benchmarks and recommendations | Yes | No | | Conversion metrics | App events such as add to cart, checkout initiated and purchase, via the Meta SDK or App Events API | No | | Basic formats (media, carousel, catalog, flow, list, reply) | Yes | Yes | | Basic and cost metrics (sent, delivered, read, clicked, errors, spend) | Yes | Yes | Meta quotes one performance figure for quality-based delivery: up to 9% more delivered messages. Its own footnote says this came from an A/B test of about 12 million delivered marketing messages sent by advertisers in India in January 2025. Do not expect that number in every market or for every list. ## Does it change what WhatsApp marketing costs? Meta says the Marketing Messages API uses the same billing model as Cloud API: you pay per delivered message, and the rate depends on the category and the recipient's market. Meta's pricing page adds one optional control for the new API. - **Maximum price.** From 2026 a business can set a maximum price for each marketing message delivery on the Marketing Messages API. Meta then charges that maximum or less. This does not apply to Cloud API, whose marketing messages are charged at the published rate. - **No volume tiers for marketing.** Meta applies volume tiers to utility and authentication only. - **Free entry point window.** Marketing messages sent inside a free entry point window, opened when a user replies to a Click to WhatsApp ad, are not charged. We do not print rates in articles. Use Meta's current rate card, our [WhatsApp pricing by country](/whatsapp-pricing/) and the [WhatsApp pricing calculator](/tools/whatsapp-pricing-calculator/). Our own terms for WhatsApp are that it is charged at Meta's rate with zero markup. For a wider cost picture, read [WhatsApp Business API pricing in 2026](/blog/whatsapp-business-api-pricing-2026/). ## Who can use it, and where are features limited? Meta's get-started page requires an active messaging account in an eligible country, an approved marketing template and a subscription to the messages webhook. Some optimisations are switched off in several regions. | Region | What Meta documents | |---|---| | European Economic Area, UK, Japan, South Korea, Nigeria, South Africa, Thailand | No delivery optimisations, per-user template limits are inactive, and click and conversion metrics are unavailable | | United States | Meta has not delivered marketing messages to US WhatsApp numbers since 1 April 2025 (error 131049); this applies to all Business Messaging APIs | | Cuba, Iran, North Korea, Syria, Venezuela and parts of Ukraine | Businesses cannot onboard and messages cannot be sent to these regions | | Russia and Belarus | Allowed with exceptions; delivery optimisations and click and conversion metrics do not apply | The practical result is that the main reason to adopt it early, quality-based delivery, depends on where your recipients are. If most of your audience is in the Gulf, check Meta's current geographic table before you plan around a delivery uplift. Meta may change the list. ## How do you send a marketing message with the new API? You send the same template to a different endpoint, and you route each template by its latest category. The request body follows the familiar template structure. The steps in Meta's documentation are: 1. In the App Dashboard, open WhatsApp, then Quickstart, find the module for improving ROI with marketing messages and accept the terms of service. 2. Send a test marketing template to your own number with a POST request to the `marketing_messages` endpoint on your phone number ID. 3. Keep a cached mapping of every template's ID, name, language and latest category, and send `MARKETING` templates to `marketing_messages` and all others to `messages`. 4. Subscribe to the template category update webhook and update the mapping when a completed notification arrives. Do not act on an impending notification. 5. After onboarding, set `disable_marketing_messages_on_cloud_api` to `true`. Cloud API then rejects marketing templates with error `131063`, and you refresh the category and retry through the marketing endpoint. 6. Make retries idempotent and retry only after a confirmed failure. Status webhooks for messages sent this way carry `marketing_lite` in the `pricing.category` field, so your reports can separate them. Use the [WhatsApp webhooks guide](/blog/whatsapp-webhooks-guide/) for event handling and [WhatsApp template examples](/blog/whatsapp-message-template-examples/) for template wording. ## Why does template reclassification matter now? Meta can change a template's category after approval, and a utility template that contains promotional content can become marketing. After the sunset, that template can only be sent through the marketing endpoint. Meta's categorisation documentation says utility templates must be non-promotional and tied to a user action or an essential update. Order and account messages must not promote, upsell or cross-sell. A "your order has shipped" template with a discount code appended is the classic case. Review your utility library now, remove promotional lines, and make your routing code read the current category instead of assuming it. ## How do you measure whether it works? Run a controlled comparison rather than trusting a headline uplift. Measure on the same audience, same template and same time window. 1. **Split.** Keep a comparable group on Cloud API while the old route still works, or compare matched campaigns before and after the switch. 2. **Compare delivered rate, not accepted rate.** Divide delivered messages by messages submitted. 3. **Compare read and click rates** using Meta's status webhooks and click metrics where available in your region. 4. **Calculate cost per delivered message and cost per conversion.** Use the delivered charge, not the submission count. 5. **Use your own conversion data.** If you cannot send app events, tag links with campaign parameters and count outcomes in your CRM. 6. **Watch frequency.** Quality-based delivery does not remove the need for [opt-in and relevance](/blog/opt-in-consent-multichannel-campaigns/); a rise in blocks hurts account quality whichever endpoint you use. Worked example with synthetic numbers: a Riyadh electronics retailer sends 100,000 marketing templates and Meta delivers 90,000 on the old route. Another 100,000 on the new endpoint deliver 92,000. The delivered rate rose from 90% to 92%, which is 2,000 more messages reaching customers. Whether that is worth anything depends on the click and purchase rates of those extra recipients, so compare cost per purchase, not delivery alone. ## Who should migrate first? Everyone who sends marketing templates will have to move by Meta's sunset date, but the urgency differs. | Situation | Suggested priority | |---|---| | New WhatsApp account planned for 2027 | Build on the Marketing Messages API from day one, since accounts created on or after 13 April 2027 cannot use Cloud API for marketing | | Large promotional volume to markets where optimisations are active | Pilot early and measure | | Mostly utility and authentication traffic | Low urgency, but audit for reclassification risk | | Heavy use of Click to WhatsApp ads | Check how free entry point windows and billing appear in your reports | | Using a provider or CRM | Ask the provider for its migration date and what it supports | ## What mistakes should you avoid? - **Assuming one endpoint for everything.** Route by category and keep it current. - **Treating the 9% figure as a promise.** It is a regional test result. - **Forgetting the unsupported markets.** US numbers do not receive marketing messages, and optimisations are off in several regions. - **Leaving promotional text in utility templates.** Reclassification will push those onto the marketing endpoint and into marketing pricing. - **Ignoring frequency and consent.** Delivery optimisation does not replace permission. - **Waiting for the last month.** Plan testing, approvals and reporting changes well before October 2027. ## How OmniChannels.ai helps BroadNet is an official Meta Business Solution Provider, and OmniChannels.ai sends WhatsApp marketing templates with media, variables and buttons through [campaigns](/platform/campaigns/), with delivery reports and a CSV export. WhatsApp is charged at Meta's rate with zero markup. We do not claim support for the Marketing Messages API in this article: ask our team about your account and timeline, and we can review your template categories with you. [Book a demo](/demo/) to talk it through.