WhatsApp Marketing Messages API (MM Lite): 2026 Guide

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.

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 for event handling and WhatsApp 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; 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.

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, 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 to talk it through.