What did Meta remove from the Marketing API on October 27, 2026, and will it break my ad tools?
On October 27, 2026, Meta's v26.0 changes reached every Marketing API version: no Messenger Stories placement, no new poll ads, fewer delivery estimate fields. They had applied to v26.0 calls since July 29. Web-only creatives also can't go into Website and App campaigns, and delivery estimates no longer return the daily outcomes curve, estimated daily active users or budget guardrail. Root ?ids= requests and other old Graph API features stopped working the same day. A tool breaks only if it still uses one of these. Meta says the Messenger Stories change doesn't affect Ads Manager.
As of November 2026.
What changed
Meta's v26.0 changelog and its July 29 launch post list these items with an "all versions" date of October 27, 2026. That is 90 days after the v26.0 release. Calls made on v26.0 had them from July 29; older versions and unversioned calls were left alone until October 27.
| Before October 27 (v25.0 and older) | Now (all versions) | |
|---|---|---|
Messenger Stories placement (story in messenger_positions) | Could be set in manual placements | Deprecated. On v26.0 and later, Meta silently drops the value. Advantage+ placements need no change |
Poll ads (poll_spec and the poll type) | Could be created and edited | Creating a poll creative, or changing an ad into one, is rejected. Edits that don't touch the creative (status, budget, schedule) still work |
Web-only creatives (applink_treatment=web_only) | Could be attached in any campaign | Can't be attached to an ad in a campaign that uses Website and App conversion locations. Meta says to use automatic or another compatible destination |
Delivery estimate fields daily_outcomes_curve, estimate_dau, budget_guardrail | Returned by /delivery_estimate on ad accounts and ad sets | No longer returned, because the service behind them was deprecated. Meta says "No replacement API is available" |
| Legacy Graph API features | pretty, debug, date_format, root GET /?ids=..., ETag and 304 Not Modified | pretty and debug are ignored. date_format and root ?ids= requests return an error. No ETag or 304 responses |
| Commerce Order Management API (47 endpoints) | Available | Removed, with no replacement |
One more v26.0 change has no October 27 date: the Instagram Explore Feed placement. Meta says that beginning with v26.0 on July 29, the placement is no longer available: delivery to Explore stops and spend shifts to other eligible placements. On v26.0, creating or updating an ad set that names Explore returns an error. The changelog lists it under "v26.0+" only. Meta gives no date for older versions and doesn't say whether ad sets set up on older versions or in Ads Manager still deliver there.
Meta's 2026 list of out-of-cycle Marketing API changes has nothing else dated October 27.
Which Marketing API versions still work?
v26.0 and v25.0. Meta's versions page and versioning guide give these dates:
| Version | Released | Ends |
|---|---|---|
| v26.0 | July 29, 2026 | Not set |
| v25.0 | February 18, 2026 | Not set yet |
| v24.0 | October 8, 2025 | Expired October 6, 2026 |
Meta's versions table doesn't show a Marketing API v26.0 row yet, but its versioning guide says "The current version of the Marketing API is v26.0."
If a tool still calls an expired version, Meta's auto-upgrade sends calls to endpoints that didn't change on to the next version. Calls to endpoints that did change can fail. You can turn auto-upgrade off in your app's Marketing API settings. Meta says it supports the previous version for at least 90 days after a new release. For v25.0, that minimum passed on October 27, so Meta could set an end date at any time.
Who it affects
Only tools and scripts that call Meta's API and still use one of the items above. If you work only in Ads Manager, Meta says the Messenger Stories change is "API-only." It doesn't say whether Ads Manager changed for the other items.
For B2B advertisers, the tools to check are:
- Ad builders and bulk uploaders that set manual placements or create poll ads. The Messenger Stories change on v26.0 is silent, so a tool may think an ad set includes Stories when it doesn't. Meta doesn't say whether older versions now drop the value silently or return an error.
- Media planning and forecasting tools that show daily result curves or daily active users from delivery estimates. Those numbers are gone from the API. Meta doesn't say whether the estimates in Ads Manager changed.
- Reporting connectors and in-house scripts that look up many objects with one root
?ids=call, passdate_format, or cache with ETags. The first two now return errors. - App advertisers running Website and App campaigns with web-only creatives. If you don't advertise an app, skip this one.
- Shop and order tools that use the Commerce Order Management API. If you don't sell through Meta's shops, skip this one.
You can likely ignore all of this if your vendors already call v26.0 and you use Advantage+ placements instead of picking Explore or Messenger Stories by hand.
What to do now
- Check error logs from October 27 on. Look for failed ad or creative creation, placement errors, empty delivery estimate fields and failed
?ids=lookups. - Ask each vendor two questions: which Marketing API version do you call, and have you removed these fields? Start with reporting connectors, ad uploaders and lead sync tools.
- Search your own scripts for
messenger_positions,poll_spec,daily_outcomes_curve,estimate_dau,budget_guardrail,applink_treatment,date_format,?ids=andIf-None-Match. Meta's fixes: use per-object requests or supported batching instead of root?ids=, format dates in your own code, and expect full responses instead of 304s. - Review manual placements. Remove Messenger Stories and Instagram Explore, or switch to Advantage+ placements, which Meta says need no action for the Messenger change.
- Move to v26.0 now. Don't wait for v25.0 to get an end date, and don't count on auto-upgrade for endpoints that changed.
- Plan forecasts without the removed fields. There is no API replacement for the daily outcomes curve or estimated daily active users.
- If you run housing, employment or financial ads, set
targeting_automation.advantage_audienceto 1 or 0 when you create an ad set with narrowed targeting. Broad or default setups are unaffected. It's required on v26.0 and becomes required on all versions once v25.0 is deprecated.
Dates to watch
| Date | What happens |
|---|---|
| July 29, 2026 | Graph API and Marketing API v26.0 released. The changes above apply to v26.0 calls. Instagram Explore Feed placement ends for v26.0 |
| September 24, 2026 | Graph API v20.0 removed |
| October 6, 2026 | Marketing API v24.0 expired |
| October 27, 2026 | The v26.0 changes in the table apply to all versions, including unversioned calls |
| January 21, 2027 | Graph API v21.0 removed. Check tools that pull Page or lead data through the Graph API |
| Not set yet | Marketing API v25.0 expires. The explicit advantage_audience rule then applies to all versions |
Sources
- Version 26.0, Graph API and Marketing API changelog (Meta for Developers), checked November 4, 2026
- Introducing Graph API v26.0 and Marketing API v26.0 (Meta for Developers blog, July 29, 2026), checked November 4, 2026
- Versions, Graph API and Marketing API changelog (Meta for Developers), checked November 4, 2026
- Marketing API versioning (Meta for Developers), checked November 4, 2026
- 2026 Out-Of-Cycle Changes, Marketing API (Meta for Developers), checked November 4, 2026
