WhatsApp Marketing Messages API: What to Do Before 13 October 2027
Meta will stop supporting marketing messages on the WhatsApp Cloud API on 13 October 2027, according to its own documentation, and HighLevel told its accounts on 19 October 2026 to move marketing sends to its MM Lite connection before then. Service, utility and authentication messages stay where they are; promotions, offers and announcements have to move to Meta’s Marketing Messages API.
This is what the dates are, what the move gains and does not cost, and the seven steps we would use to do it without a gap in your campaigns.
What is ending on 13 October 2027?
Meta’s documentation says plainly: the WhatsApp Cloud API will stop supporting marketing messages on 13 October 2027. After that date, a marketing template sent through the Cloud API returns an error. Marketing messages have to go through Meta’s Marketing Messages API (MM API) instead.
Only marketing is affected. Meta states that authentication, utility and service messages stay on the Cloud API, so order confirmations, one-time codes and replies inside a customer’s open conversation keep working as they do today. Promotions, offers, re-engagement and announcements are the category that moves.
HighLevel, which connects WhatsApp to its CRM, workflows and campaigns, put out an “action needed” notice on 19 October 2026 telling every account to move marketing sends to its MM Lite connection before that date. If your business messages customers on WhatsApp through HighLevel, or through any other platform, this is a dated migration, not an optional upgrade.
What are the dates to put on the calendar?
Meta publishes the timeline on its Marketing Messages API overview page. Four dates matter.
| Date | What happens |
|---|---|
| 19 Nov 2025 | Marketing Messages API for WhatsApp becomes generally available |
| 13 Oct 2026 | Global announcement that the Cloud API will stop supporting marketing messages |
| 13 Apr 2027 | Accounts created on or after this date cannot send marketing messages on the Cloud API; older accounts still can |
| 13 Oct 2027 | Sending marketing messages on the Cloud API produces an error |
The second row matters for new business. A WhatsApp account you create after 13 April 2027 starts on the new API with no choice, so any onboarding checklist for a new client should assume MM API from the first day. The last row is the hard stop for everyone else.
What do you gain by moving early?
Meta lists three things. The first is delivery optimization: the API uses engagement signals to prioritize messages to people likely to find them relevant. The second is measurement, including performance benchmarks against similar businesses and tailored recommendations. The third is creative: animated GIF headers, message time-to-live, and automatic creative optimizations that Meta still describes as a test.
Read the delivery claim carefully. HighLevel’s changelog says Meta’s A/B test, covering about 12 million delivered messages from advertisers in India in January 2025, found “up to” 9% higher delivery for high-engagement messages. That is a ceiling measured on one market and one month, not a promise for a Mexico City restaurant or a Miami charter broker. HighLevel notes the gain comes from reaching likelier readers, not from sending more.
Time-to-live is the feature we would use first. A message with an expiry stops being eligible for delivery after its window, so a Friday-night offer cannot arrive on Monday. For any business that sends dated promotions, that removes an embarrassing failure without extra work.
Does it change what you pay?
Not by itself. Meta says the MM API uses the same billing model as the Cloud API, and its overview page gives no new prices. Your invoice stays the final source for what each message costs.
There is a second, separate pricing feature to know about. Meta’s pricing page describes a max price setting, a cap on what you will pay per delivery that works as a bid, not a budget. It entered open beta on 1 October 2026 and general availability is listed for Q2 2027. The page also says that at general availability, fixed published rates for marketing messages will apply only on the Cloud API, and that a template sent with a max price to the Cloud API endpoint returns error 131061. If your agency or software vendor mentions bidding, that is the feature they mean. It is optional, and the page lists no Mexico rates, so do not quote one to a client.
What do HighLevel accounts have to do?
HighLevel’s notice says activation takes a few minutes per sub-account, existing phone numbers and templates carry over without re-approval, and campaigns keep running during the switch. The steps, from its changelog:
- In the sub-account, open Settings, then WhatsApp, and click the MM Lite banner.
- Click Enable MM Lite. You are sent to the WhatsApp account interface.
- Open the Requests tab and click Respond.
- Click Continue on the prompt about improving ROI with the Marketing Messages API.
- On the access request screen, confirm the permissions and click Finish.
HighLevel’s help article lists what you need first: an active WhatsApp setup, access to the connected Facebook Business Manager, a WhatsApp Business Account under the correct business portfolio, and permission to approve business-level access requests. That last item is where agencies stall. The person who can click Finish is often the client’s owner, not the marketer.
Why not wait until next autumn?
HighLevel’s own advice is to act now, because current Cloud API campaigns lack delivery optimization, conversion tracking and certain creative formats. Meta gives its own practical reason: it says most integrations take about two weeks to confirm live on the new endpoint, and that utility messages Meta reclassifies as marketing must also be routed to the MM API.
That second point is the one that surprises people. A confirmation that carries a discount code, or a reminder that ends with an upsell, can be treated as marketing. If your workflows mix the two, the safest way to find out is to test them on the new connection well before the cutoff, not to learn it from an error on 13 October 2027.
There is also a quiet risk in leaving it to the last month: every agency and software vendor will be doing the same migration at once, and the approval step depends on a business owner’s availability. Twelve months is enough time only if someone owns the task.
How we would run the migration
For clients we manage inside GoHighLevel systems, this is the order we would follow. It is a plan, not a record of something we have already completed for a client.
- List every WhatsApp send. Campaigns, workflow steps and automated follow-ups, each tagged marketing or utility.
- Find the mixed ones. Any utility message that carries an offer gets split into two messages or moved to the marketing list.
- Start with the highest-volume sub-account. HighLevel recommends this, and it is where delivery changes show up first.
- Get the approver on a call. The owner who can approve Business Manager access does the click-through with us, in ten minutes.
- Add expiry to dated offers. Set a time-to-live on every promotion with an end date.
- Compare for a month. Same audience, same template, delivery and click counts before and after, using the account’s own reports.
- Write the result down. One line per account in the client file, so the 2027 deadline is closed, not remembered.
This is the kind of recurring, rules-based task an agent can track and draft, with a person approving each change, which is how we approach agentic marketing in general. Our AI marketing work keeps that approval step in every automated workflow.
What does this mean for Mexico and Latin America?
We have no verified figure for how many businesses in Mexico message customers on WhatsApp, so we will not invent one. What we can say from experience is narrower: for the restaurants, clinics, hotels and real estate offices we talk to in Mexico City and Miami, WhatsApp is where customers expect to be answered, and a stalled campaign there is a visible failure.
The practical consequence is that the migration belongs on the same list as your website and your search visibility. If you want a quick read on how machines see your site today, the free AI Visibility Checker takes a minute, and the thinking behind that work is in can AI agents use your website.
Want your business found on Google and in ChatGPT? Ciao Bella engagements start at $5,000 a month, no setup fee. See how we work.
Verified 22 October 2026 against Meta’s Marketing Messages API for WhatsApp overview and pricing pages, HighLevel’s changelog entries on the MM Lite launch and the 19 October 2026 action-needed notice, and HighLevel’s MM Lite help article
Building on the web since 1999 · South Florida and Mexico City
Frequently asked questions
When does WhatsApp stop supporting marketing messages on the Cloud API?
Meta’s documentation says on 13 October 2027. Accounts created on or after 13 April 2027 cannot send marketing messages on the Cloud API at all. After the October date, sending one produces an error.
Do my order confirmations and customer replies have to move too?
No. Meta says authentication, utility and service messages stay on the Cloud API. The exception is a utility message that Meta reclassifies as marketing, which has to be routed to the Marketing Messages API.
Will I need to get my WhatsApp templates approved again?
HighLevel says existing phone numbers and templates carry over without re-creation or re-approval, and that campaigns keep running during the switch. Meta also says the upgrade uses a similar technical schema and your existing numbers and templates.
Will marketing messages cost more on the new API?
Meta says the Marketing Messages API uses the same billing model as the Cloud API and gives no new prices on its overview page. Your invoice is the final source. A separate, optional max price setting entered open beta on 1 October 2026.
Is the 9% delivery improvement guaranteed?
No. HighLevel reports it as “up to” 9% for high-engagement messages, from Meta’s A/B test of about 12 million delivered messages sent by advertisers in India in January 2025. Results in other markets and for other audiences will differ.
Sources
- Meta — Marketing Messages API for WhatsApp: overview Cloud API stops supporting marketing messages 13 Oct 2027; timeline (19 Nov 2025, 13 Oct 2026, 13 Apr 2027); service, utility and authentication stay; same billing model; benefits; migration steps and reclassified utility messages.
- Meta — Marketing Messages API for WhatsApp: pricing Max price as a per-delivery bid cap; open beta 1 Oct 2026, general availability Q2 2027; error 131061 on the Cloud API endpoint; no Mexico rates listed.
- HighLevel — Action needed: move your WhatsApp marketing to MM Lite before October 2027 (19 October 2026) Deadline guidance, five activation steps, templates and numbers carry over, start with highest-volume sub-accounts.
- HighLevel — Marketing Messages API for WhatsApp (MM Lite) is now live Up to +9% delivery for high-engagement messages; A/B test of about 12M delivered messages, India, 1–31 Jan 2025; GIF headers and deep links; creative optimizations in pilot.
- HighLevel Help — MM Lite explained: faster, simpler WhatsApp marketing at scale Requirements (active setup, Business Manager access, correct portfolio, approval permission); marketing-only scope; time-to-live.