Meta ends marketing messages on the WhatsApp Cloud API on October 13, 2027
Meta will stop carrying marketing messages on the WhatsApp Cloud API on October 13, 2027, so promotional templates must move to the Marketing Messages API (MM API). Service, authentication and utility messages stay on Cloud API. Accounts created on or after April 13, 2027 cannot send marketing messages through Cloud API at all.
Marketing templates are moving from Cloud API to the MM API
Meta has set October 13, 2027 as the date its WhatsApp Cloud API stops carrying marketing messages. Meta's Marketing Messages API documentation says that after that date, "sending marketing messages on Cloud API will produce an error", while marketing messages continue on the Marketing Messages API for WhatsApp (MM API). According to PPC Land, the announcement came in a Meta for Developers blog post written by Sascha Noll dated October 21, 2026, with the stated aim of bringing every WhatsApp marketing send onto the MM API. We could not open the blog post itself, so its date and author rest on PPC Land's report.
Only one category is affected. Promotions, offers, newsletters and abandoned-cart nudges count as marketing templates and must move. Service, authentication and utility messages stay on Cloud API, so the Cloud API is not being shut down as a whole. One wrinkle, again per PPC Land: if Meta reclassifies a template submitted as utility into marketing, that traffic must move to the new API too.
A second, earlier date applies to new accounts
Meta's Marketing Messages API documentation sets an intermediate cutoff that, according to PPC Land, the blog post does not mention. Messaging accounts created on or after April 13, 2027 cannot send marketing messages through Cloud API. Accounts created before that date keep Cloud API marketing access until October 13, 2027. A business or vendor that opens new accounts after April 13, 2027 therefore starts on the MM API from day one.
The two APIs sit side by side. PPC Land reports that marketing templates go to the /<PHONE_NUMBER_ID>/marketing_messages endpoint, while the other categories stay on /<PHONE_NUMBER_ID>/messages. Meta's three migration steps are to accept the MM API terms, confirm the integration is live on the MM API endpoint, and route reclassified traffic correctly. Meta puts the typical integration effort at roughly 2 weeks. Per Meta's documentation, billing follows the same model as Cloud API.
The case for switching is weaker in some markets
Meta lists automatic creative optimization, time-to-live settings and richer media such as GIFs as the benefits, and the post gives no performance figures. PPC Land reports that in the EEA, the UK, Japan, South Korea, Nigeria, South Africa and Thailand delivery optimizations are missing, as is click and conversion reporting. In its reading, companies selling mostly to European or UK customers are left chiefly with time-to-live and richer media, even though the migration date is the same.
Separately, PPC Land notes that WhatsApp users in the United States receive no marketing messages from Meta at all, a restriction it dates to April 1, 2025 (error code 131049). The practical point for anyone running promotions on WhatsApp is the calendar: the window is long, but every marketing template, every reclassification rule and every vendor contract touching Cloud API sends needs an owner before it closes.
PPC Land does not mention Türkiye, so this section is commentary
PPC Land's report does not mention Türkiye, and Türkiye does not appear in the list of regions it gives for missing optimizations. Meta's documentation page does not mention Türkiye either. That is all we can say from the sources. This section is therefore UNALSOFT commentary, not a fact drawn from the sources.
Our reading: if your business sends WhatsApp promotions through a provider or an integrator, the migration is largely their engineering work, and the useful questions to ask them are which of your templates count as marketing, what happens when Meta reclassifies one, and when they plan to move you. The unknowns are worth listing. Neither source gives Türkiye-specific availability or pricing detail, or an error code number for Cloud API sends after the sunset, and according to PPC Land the blog post offers nothing aimed at software vendors sending for many client accounts. We covered a different WhatsApp Business change in September; that article is independent of this calendar change.
The UNALSOFT view
We read this as a calendar problem more than a technology problem. The date is far enough away to feel optional, yet account creation after April 13, 2027 and Meta's reclassification of utility templates mean marketing traffic can end up on the wrong endpoint earlier than the headline suggests. The sensible first step is an inventory: which messages you send are promotional, who sends them, and what your provider's plan is. On the ad management side we treat the WhatsApp message flow as part of the campaign, so the template category, the endpoint and the offer copy are reviewed together. Because the sources carry nothing about Türkiye, this article proposes no local conclusion.
Is your WhatsApp marketing traffic ready for the new endpoint?
A short conversation is enough to map which of your campaigns and templates would be affected and what to ask your provider.