Marketing API v24.0 expires October 6: check the tools connected to your ad account
Version v24.0 expires on October 6, 2026, and calls to it stop working. Ads Manager is unaffected — the risk sits with the integrations, reports and bulk uploaders connected to your account.
Marketing API v24.0 reaches the end of its life on October 6, 2026. The version was released on October 8, 2025, and after the expiry date calls to it stop working — requests carrying that version number fail with an error. Your ad account and Ads Manager keep running as before. What breaks are the third-party services that reach into your account through the API and are still pinned to v24.0.
What changed
- The date. Meta's official versions page lists Marketing API v24.0 as released on October 8, 2025, with an expiry date of October 6, 2026.
- What happens after it. Calls to that version stop working: a request with v24.0 in its URL fails with an error. Not "degraded", not "a few fields missing" — an error in response.
- Why the date was visible in advance. Marketing API and Graph API follow a versioning cycle: the previous version is supported for at least 90 days after a new one ships. The expiry date is published alongside the version, so there is no reason to count on an extension.
- Current versions. Marketing API v25.0 was released on February 18, 2026, and Meta has not announced its expiry date yet (TBD). Graph API v26.0 was released on July 29, 2026.
- A breaking change on the way to v25.0. The v25.0 changelog states it verbatim: "Creation, duplication, and updates to Advantage+ shopping campaigns and Advantage+ app campaigns is no longer allowed." Those campaigns can no longer be created, duplicated or edited through the API — the new Advantage+ structure is the way forward.
- A small change that complicates debugging. v25.0 also announced the deprecation of the
metadata=1parameter: it stops returning field descriptions. - The next date is October 27, 2026. The Graph API v26.0 changelog says that by then the fields
daily_outcomes_curve,budget_guardrailandestimate_dauare removed from Delivery Estimate responses, with no replacement. From the same date, creatives withapplink_treatment=web_onlystop working in Website and App campaigns across all Marketing API versions.
What it means for your business
If you run ads by hand in Ads Manager, nothing changes for you on October 6: budgets, ads, billing and stats all stay where they are. This date is about programmatic access to the account.
And almost everyone who has outgrown a single account has programmatic access in place. CRM integrations, ad bulk-creation tools, reporting services and dashboards, bulk uploaders and Google Sheets connectors all reach the account through the API. You granted each of them access at some point, and each sends requests with a specific version number in the URL.
The worst part is how this looks from the outside. There will be no warning in Ads Manager, because the failure happens on the service's side. You find out from indirect signs: a report stops updating and keeps showing yesterday's or last week's numbers, a dashboard goes empty, queued ads never get created, leads never arrive in the CRM. It is easy to write this off as an ordinary service glitch and wait for it to fix itself.
One more thing worth planning for: moving to v25.0 is not just a new number in the URL. If your service used to create or duplicate Advantage+ shopping and Advantage+ app campaigns, it will not be able to after the move — that is Meta's rule, not a limitation the vendor introduced. And the fact that v25.0 has no announced expiry date only means it will be announced later, together with the next version.
What to do now
- List everything connected to your account: CRM, bulk ad creator, reporting service, dashboard, bulk uploader, Google Sheets export. Without that list there is nothing to check.
- Ask each vendor which Marketing API version their service runs on and whether it has been moved off v24.0. It is a single support question, and the answer should be specific: a version number.
- After October 6, check by hand: did yesterday's numbers refresh in the report, did the scheduled ads get created, did the leads reach the CRM. Compare the service's numbers against Ads Manager for the same day — a mismatch is easier to spot than an empty chart.
- If your scripts were built to order or you maintain them yourself, raise the version number in the request URL and test on a small-budget campaign. While you are in there, find every place that creates or duplicates Advantage+ shopping and Advantage+ app campaigns, and drop any dependency on
metadata=1. - Put October 27 on the calendar. If your reports or forecasts rely on the Delivery Estimate fields
daily_outcomes_curve,budget_guardrailorestimate_dau, Meta offers no replacement, so that logic will have to be rebuilt on other data. If Website and App campaigns use creatives withapplink_treatment=web_only, those need reworking. - Revoke access for services you no longer use — that is our own advice, not part of Meta's change, but fewer integrations means fewer places that can fail silently.
If you do not know which services are connected to your account, start there: without a list of integrations, there is nothing to verify and nothing to fix.
What this means for you
Your account and Ads Manager will not stop working on October 6: budgets, ads and billing are untouched.
The risk sits with the third-party services connected to your account. If a vendor has not moved them off v24.0, your reports will quietly stop updating or your ads will stop being created, and Ads Manager will give you no warning.
One question to your vendor today costs less than a week of advertising without data.