Meta today set a hard end date for one of the most common uses of its WhatsApp developer platform. Marketing messages sent through the WhatsApp Cloud API will stop working on October 13, 2027, and businesses that want to keep sending promotional templates must move that traffic to a separate product, the Marketing Messages API for WhatsApp. The notice, a Meta for Developers blog post by Sascha Noll, gives businesses just under two years and lists three migration steps. It says little about pricing, error handling or the earlier cutoff that Meta's own documentation sets for new accounts.

In Short

Meta is closing one of the two doors businesses use to send promotional WhatsApp messages, and from October 13, 2027 those messages will only go through a newer door built for marketing. Any company or software vendor that sends offers, newsletters or sale alerts over WhatsApp through the older Cloud API is affected. Their systems need to switch to the new marketing door before the date, while service, login-code and order-update messages can stay where they are.

What Meta said

The post, published today on the Meta for Developers blog under the tags Developer Tools, Marketing API and WhatsApp, is short. Its headline reads "Sunsetting Marketing Messages on the Cloud API: Upgrade to the Marketing Messages API for WhatsApp before October 2027." The operative sentence sits in a section titled "Marketing messages on Cloud API sunset October 13, 2027."

"To consolidate all WhatsApp marketing message delivery on the Marketing Messages API for WhatsApp, marketing messages on WhatsApp sent through the Cloud API will sunset on October 13, 2027," according to Meta.

That is the whole of the policy change in the post. The rest is a description of the replacement product and a migration checklist. Meta describes the Marketing Messages API for WhatsApp as "our next-generation marketing solution built to help deliver the right message to more of the right people," and says it "offers richer features to help drive better outcomes for both businesses and people."

Two dates matter, and they are easy to conflate. The post itself went out on October 21, 2026, according to its URL and the page's own timestamp. The sunset - the point at which the Cloud API stops carrying marketing messages - is October 13, 2027. That leaves 357 days between announcement and cutoff, by PPC Land's own count.

The headline wording adds a small ambiguity. It asks businesses to upgrade "before October 2027," which on a literal reading means by the end of September 2027, while the body gives October 13, 2027 as the actual sunset. The body date is the one Meta's documentation repeats.

What is being sunset, and what is not

Only one message category is affected. WhatsApp's business platform sorts template messages into categories, among them marketing, utility and authentication. The post speaks only of "marketing messages on WhatsApp sent through the Cloud API." It does not say that the Cloud API itself is being retired.

The linked documentation is more explicit. Meta's Marketing Messages API overview page, which the post links as its main resource, states that service, authentication and utility messages remain on the Cloud API. In practice this means a business sending order confirmations, delivery updates or one-time passcodes is not asked to change anything for that traffic. A business sending promotions, abandoned-cart nudges or newsletter-style templates is.

The split creates a two-API arrangement for many companies. The same phone number and the same business account will send marketing templates through one endpoint and everything else through another. Meta's routing documentation, linked from the post, names them: marketing templates go to /<PHONE_NUMBER_ID>/marketing_messages, while all other supported categories go to /<PHONE_NUMBER_ID>/messages.

The replacement product

Meta lists three claimed benefits in the post, each in its own bullet:

  • "Opportunity to boost business results like improved click through rates with automatic creative optimizations and performance-enhancing features built for marketing."
  • "Enhanced customer experience and engagement: MM API for WhatsApp helps deliver more relevant and timely marketing messages to customers with features like time-to-live, richer media formats, and more."
  • "Upgrade easily, with consistent reliability and security: MM API is easy-to-use, reliable, and secure. Businesses can use existing phone numbers and marketing message templates."

The first two bullets carry asterisks. The footnote reads: "Geographic restrictions on some optimization features apply." The post gives no list of those restrictions in its own text; it links to a separate page.

No performance figures appear in the post. It says "many businesses are already enjoying the benefits" without a count of adopters, and it does not quantify the click-through rate improvement it mentions. Meta's overview page does describe the test behind its delivery claims: an A/B test with approximately 12 million delivered marketing messages sent by advertisers in India between January 1 and January 31, 2025, comparing optimized delivery with standard Cloud API delivery for high-engagement messages only, analyzed with a t-test at a 95% confidence level. The overview page does not publish the resulting lift in the passages PPC Land reviewed.

The features themselves, as listed on the overview page, are automatic delivery optimization, measurement insights including benchmarks against similar businesses, automatic creative optimizations such as image animation and filtering (described as in testing), richer media formats including GIFs, and a message time-to-live setting that lets a business set an expiration so a time-sensitive promotion is not delivered late.

Optimization of WhatsApp marketing messages is not new to Meta's pitch. In June 2024, Meta presented marketing message optimizations for WhatsApp at its Conversations event in Sao Paulo, citing a Brazilian financial technology company that saw a 30% reduction in cost per page view and a 20% increase in click-through rate in testing. At the time, Meta said the feature would soon reach businesses using the WhatsApp Business Platform through partner integrations. Today's sunset turns what was an optional upgrade path into the only route for marketing traffic.

Migration steps

The post sets out three steps under the heading "Here's how you can get started":

  1. "Accept the Marketing Messages API for WhatsApp terms."
  2. "Confirm your integration is live on the Marketing Messages API for WhatsApp endpoint."
  3. "Check your reclassified traffic. Utility messages reclassified as marketing must route to the MM API for WhatsApp. Your integration should recognize the classification and route accordingly."

Meta also gives one effort estimate: "Most integrations take about 2 weeks on average."

Reclassification is the hard part

The third step is the one with technical depth, and the post compresses it into two sentences. Meta can change a template's category after approval when its content does not match the category guidelines. A template submitted as utility that contains promotional content can be moved to marketing. Once that happens, under the new regime, sending it through the Cloud API endpoint will no longer work.

The routing page linked from the post spells out what Meta expects from integrations. Systems are told to route each send by the template's latest category rather than its original one, to subscribe to the template category update webhook, and to update their stored mapping only when a completed notification arrives, using the new_category field. A separate correct_category field in "impending" notifications is described as monitoring information only, not a routing signal.

The same page asks integrations to persist the Messaging account ID, template ID, template name, language and latest category, and to fall back to the Message Templates API when a mapping is missing. Retries are to happen only after a confirmed failure and must be idempotent, so a message that was in flight during a category change is not sent twice.

For businesses that have historically leaned on the utility category for messages with a promotional edge, this is the practical exposure. Every reclassification becomes a routing event, and an integration that does not listen for it will send marketing traffic to the wrong endpoint.

Error behavior

The blog post does not say what happens to a marketing message sent through the Cloud API after October 13, 2027. Meta's overview page does: "After this date, sending marketing messages on Cloud API will produce an error." It does not name the error code for the post-sunset failure.

The routing documentation does describe one error that applies earlier, during migration. Once a business has fully onboarded, it can set disable_marketing_messages_on_cloud_api to true. With that flag set, the /messages endpoint rejects marketing templates with error 131063, and the integration is expected to refresh the template's category and retry through /marketing_messages. The reverse also applies: if an appeal changes a marketing template to utility, /marketing_messages rejects it and the send must go back to /messages.

An earlier cutoff for new accounts

The most consequential date for some businesses is missing from the blog post. Meta's overview page sets an intermediate deadline: "Any new Messaging account created on or after this date will not be able to send marketing" messages on the Cloud API, with the date given as April 13, 2027. Accounts created before then can continue to send marketing messages on the Cloud API until October 13, 2027.

That means a business that opens a WhatsApp Messaging account in spring 2027, or a software vendor that provisions new client accounts after that date, will have no Cloud API marketing window at all. The post's single date, October 13, 2027, does not reflect this.

Where optimizations do not apply

The post's footnote on geographic restrictions links to a page on Meta's developer site whose URL path still uses the name "marketing-messages-lite-api," an earlier label for the product. That page lists several regions where the features Meta advertises are absent:

  • In the European Economic Area, the United Kingdom, Japan, South Korea, Nigeria, South Africa and Thailand, there are no delivery optimizations and no click and conversion reporting metrics, and the metrics are not available in Ads Manager or the Insights API. The page notes that per-user marketing template limits are not active in these markets, so the lack of delivery optimization does not affect delivery.
  • In Russia and Belarus, businesses can use the product, but delivery optimizations, click and conversion reporting and features such as max pricing are unavailable in specified cases.
  • In the United States, Meta does not deliver marketing messages to WhatsApp users at all, a restriction that applies to all Business Messaging APIs and that the page dates to April 1, 2025, with error code 131049. US business phone numbers can still use the product to message users outside the US.

For businesses whose customers are mainly in Europe or the UK, this changes the trade. They are required to migrate by the same date as everyone else, but the main reasons Meta gives for the new product - optimization and better click-through rates - do not apply in their markets. What remains for them is chiefly time-to-live and richer media formats.

What the post leaves out

Several items a developer or marketer would need are not in the blog post:

  • Pricing. The post says nothing about cost. Meta's overview page states that the product uses "the same billing model as Cloud API," but neither page gives rates, and neither says whether optimization features affect what a business pays per message.
  • API versions. No Graph API or Marketing Messages API version numbers appear in the post or in the linked routing page.
  • The April 13, 2027 new-account cutoff, covered above, appears only in documentation.
  • Error codes for post-sunset Cloud API sends are not given anywhere PPC Land reviewed.
  • Adoption data. "Many businesses" is the only measure of uptake.
  • The test result. The documentation describes a 12-million-message test in India but the post gives no figure from it.
  • Business solution providers. The post does not address software vendors that send on behalf of many client accounts, though they will carry much of the integration work.

There is also a date inconsistency between the two Meta sources. The overview page's timeline lists October 13, 2026 as the date of the "Global announcement of sunsetting support for marketing messages on Cloud API." The blog post went up on October 21, 2026. The page does not explain the eight-day gap, and the blog post does not refer to any earlier announcement.

The overview page also places the product's general availability on November 19, 2025, "after months of open beta." The sunset therefore arrives a little under two years after general availability.

Linked resources

The post links the following pages, recovered from the PDF's link annotations because plain text extraction drops them:

  • Marketing Messages API for WhatsApp Overview (developers.facebook.com/documentation/business-messaging/whatsapp/marketing-messages/overview)
  • Onboarding Guide (developers.facebook.com/documentation/business-messaging/whatsapp/marketing-messages/onboarding)
  • The routing guidance referenced in the migration steps (developers.facebook.com/documentation/business-messaging/whatsapp/marketing-messages/route-template-messages)
  • Geographic availability of features (developers.facebook.com/docs/whatsapp/marketing-messages-lite-api/get-started)
  • Business Help Center article (facebook.com/business/help/817676234423253)
  • Direct Support requests (business.facebook.com/direct-support/)

Why this matters for marketers

WhatsApp has become a direct-response channel in markets such as Brazil, India, Indonesia and Mexico, and the business messaging stack underneath it has been moving steadily. Meta brought marketing messages to Messenger in July 2025 through the Marketing API, describing that product too as an upgrade designed to eventually replace an older version. The same month, it opened the WhatsApp Business Calling API for voice calls inside existing threads. In June 2026 it took its Business Agent global across WhatsApp, Messenger and Instagram.

The sunset follows a pattern PPC Land has tracked in Meta's developer platform this year: capabilities are consolidated or withdrawn on fixed dates, and the work falls to integrators. When Meta released Graph API v26.0 in July, it blocked 47 commerce endpoints with no replacement and extended Ads in WhatsApp Status. The difference here is that a replacement exists and the timeline is long. A sunset of this kind sets a fixed date after which calls fail, and preparing for it is a question of engineering capacity rather than of whether the function survives.

The business stakes sit in the reclassification step. Meta's terms for the WhatsApp Business API have been a point of regulatory friction: WhatsApp barred general-purpose AI chatbots from its business API in January 2026, and in June the European Commission ordered Meta to restore access for rival assistants through interim measures. Those cases concern a different part of the terms, but they show how much depends on the rules Meta sets for which traffic goes where. Moving every marketing template onto a dedicated API, with Meta deciding the category and the routing following that decision, gives Meta a cleaner separation between promotional and transactional traffic on WhatsApp.

Whether that separation changes what businesses pay is the open question the post does not answer. Meta says the billing model is the same. It does not say the outcomes will be.

Timeline

Summary

Who: Meta, through a Meta for Developers blog post by Sascha Noll, affecting businesses and software providers that send WhatsApp marketing template messages through the Cloud API.

What: Marketing messages sent through the WhatsApp Cloud API will be sunset and must move to the Marketing Messages API for WhatsApp, which uses separate terms and a separate endpoint. Utility, authentication and service messages stay on the Cloud API. Utility templates reclassified as marketing must be routed to the new API.

When: Announced today, October 21, 2026. The sunset is October 13, 2027. Meta's documentation adds an April 13, 2027 cutoff for Messaging accounts created on or after that date.

Where: Globally on the WhatsApp Business Platform, although the optimization and click and conversion reporting features are unavailable in the EEA, the UK, Japan, South Korea, Nigeria, South Africa and Thailand, and marketing messages are not delivered to WhatsApp users in the United States.

Why: According to Meta, the change is meant "to consolidate all WhatsApp marketing message delivery on the Marketing Messages API for WhatsApp," which it presents as offering optimization, time-to-live and richer media. The post gives no pricing details, adoption figures or test results.