MM Lite API: WhatsApp Marketing Moves Off the Cloud API by October 13, 2027

Meta will stop accepting WhatsApp marketing messages on the Cloud API on October 13, 2027. From that date every marketing template has to go through the Marketing Messages API for WhatsApp, which most CRM vendors call the MM Lite API. Accounts created on or after April 13, 2027 lose the Cloud API route for marketing six months sooner. Service, utility and authentication messages are not affected.

HighLevel announced the change to GoHighLevel users on October 19, 2026. We checked its post against Meta’s own Marketing Messages API overview and getting-started guide on October 20, 2026. Meta confirms the date and adds two things HighLevel’s post leaves out: the April 2027 cutoff for new accounts, and the fact that marketing messages to US users are not delivered at all.

What is changing with WhatsApp marketing messages, and when?

Date	What happens	Source
November 19, 2025	Marketing Messages API for WhatsApp becomes generally available after an open beta.	Meta overview
April 1, 2025 (still in force)	Meta stops delivering marketing messages to WhatsApp users in the United States, on every API (error 131049).	Meta getting-started guide
October 13, 2026	Meta announces the end of marketing messages on the Cloud API.	Meta overview
October 19, 2026	HighLevel tells GoHighLevel users to move to MM Lite.	HighLevel changelog
April 13, 2027	WhatsApp accounts created on or after this date cannot send marketing messages through the Cloud API.	Meta overview
October 13, 2027	Cloud API stops supporting marketing messages for everyone. Sends return an error.	Meta overview

Meta’s wording is direct: “Cloud API will stop supporting marketing messages on October 13, 2027,” and after that date “sending marketing messages on Cloud API will produce an error.” Meta also says the Cloud API stays available for other traffic and gets no new marketing features.

Which WhatsApp messages does the Cloud API sunset affect?

Only messages sent with a Marketing category template. Meta lists service, authentication and utility messages as unaffected. In a CRM, that usually means:

Message you send from your CRM	Category (typical)	Affected?
Promotion, offer, newsletter, re-engagement	Marketing	Yes, must move to MM Lite
Appointment confirmation, order or payment update	Utility	No
One-time passcode	Authentication	No
Replies inside the 24-hour customer service window	Service	No

One catch worth checking: Meta can reclassify a utility template as marketing if its content reads like promotion. Meta’s migration checklist tells businesses to check reclassified traffic, because reclassified templates must also route through the Marketing Messages API.

What does the MM Lite API add over the Cloud API?

Meta and HighLevel list the same core features, all exclusive to the Marketing Messages API:

• Engagement-based delivery. Meta uses engagement signals to decide which marketing messages to deliver.
• Formats: GIF headers, Android app deep links, and time-to-live expiry dates so a time-limited offer is not delivered late.
• Reporting: clicks and conversions after the message, plus cost per template, per click and per delivery.
• Automated creative tweaks (pilot): Meta tests crops and filters on your header image and keeps the best performer.

Meta says the API has a similar technical schema and the same billing model as the Cloud API, and works with existing phone numbers and templates.

How much should you trust the “up to 9% more delivery” figure?

HighLevel’s post repeats Meta’s figure of up to 9% higher delivery. Meta’s footnote explains where it came from: an A/B test of about 12 million delivered marketing messages from advertisers in India, between January 1 and January 31, 2025, comparing high-engagement messages only. Low-engagement campaigns were not part of the test. Use it as an upper bound, not a forecast.

What does this mean if your customers are in the US, UK or EU?

This is the part most announcements skip, and it changes the decision for many businesses.

• United States. Meta’s getting-started guide says: “Starting April 1, 2025, Meta does not deliver marketing messages sent to WhatsApp users in the United States (error code 131049).” It applies across all business messaging APIs, so moving to MM Lite does not make US marketing possible. A US business number can still market to users in other countries.
• EEA, UK, Japan, South Korea, Nigeria, South Africa, Thailand. Messages sent from or to numbers in these markets do not get delivery optimization or click and conversion metrics. You still have to move by the deadline, but the headline benefits largely do not apply.
• Everywhere else (for example India, Brazil, Mexico, Indonesia): the full feature set applies, and moving early gives you the reporting sooner.

If your WhatsApp list is all US numbers, you are probably not sending marketing templates successfully today. Check your failed-message reports for error 131049 before planning any WhatsApp marketing.

How do you switch to MM Lite in GoHighLevel?

HighLevel’s changelog gives five steps, run once per sub-account:

1. In the sub-account, go to Settings > WhatsApp. A banner asks you to activate MM Lite.
2. Click Enable MM Lite. You are sent to the WhatsApp account screen.
3. Open the Requests tab and click Respond.
4. When the prompt about the Marketing Messages API appears, click Continue.
5. On Review LeadConnector’s access request, check the permissions and click Finish.

HighLevel says templates, numbers, workflows and campaigns keep running through activation and that sub-accounts using the WhatsApp Business App (coexistence) can be onboarded too. It suggests starting with the sub-accounts that send the most marketing.

Before you click: list which sub-accounts send marketing templates to non-US numbers. Those are the only ones where the switch changes anything you can measure. For agencies, that list is also the client update you owe each account.

What if your CRM is not GoHighLevel?

The deadline is Meta’s, so it applies to any CRM or messaging tool that sends WhatsApp marketing through the Cloud API, whether the vendor built the connection or you did. Meta’s own checklist for businesses that have not migrated:

1. Accept the Marketing Messages API for WhatsApp terms.
2. Confirm your integration is live on the Marketing Messages API endpoint. Meta says most integrations take about two weeks.
3. Check reclassified templates and route them to the Marketing Messages API.

Ask your CRM vendor or WhatsApp provider in writing which API your marketing templates use today and when they will move. If you are choosing a CRM partly for WhatsApp, the CRM comparison matrix and our GoHighLevel WhatsApp guide cover the per-message costs and the 24-hour window.

What to do this month

If you…	Do this
Send WhatsApp marketing to non-US customers from GoHighLevel	Enable MM Lite on those sub-accounts now; you get click and conversion reporting from day one.
Only message US customers	No urgent action. Check for error 131049 failures and use WhatsApp for service and utility messages.
Run an agency with many sub-accounts	Make a list of sub-accounts with marketing sends, migrate the highest-volume ones first, and finish well before April 13, 2027 for any new client accounts.
Use another CRM or your own integration	Ask the vendor which API marketing templates use; budget about two weeks per Meta’s estimate.

If you want a second pair of eyes on which of your GoHighLevel sub-accounts this touches, our GoHighLevel implementation team can check it on a free 30-minute call.

Sources

• HighLevel changelog, Action needed: move your WhatsApp marketing to MM Lite before October 2027, published October 19, 2026.
• Meta for Developers, Marketing Messages API for WhatsApp overview (sunset section, timeline and footnote), read October 20, 2026.
• Meta for Developers, Marketing Messages API: get started (geographic availability, US restriction), read October 20, 2026.
• Meta for Developers, WhatsApp changelog, read October 20, 2026.