Meta Marketing API v24.0 Reached End of Availability on November 10, 2026
Marketing API v24.0 was available until November 10, 2026. Here is what that means for tools and scripts that create Facebook and Instagram ads, how auto-upgrade works, and what to check now.

Meta's Marketing API changelog lists Marketing API v24.0 as available until November 10, 2026. Meta's versioning documentation says that once a version is unavailable, "any calls made to that version number may fail or be upgraded to the next available version." If you, your agency or one of your tools still sends requests to v24.0, this applies to you. This article explains what changed, who should pay attention, and what to check this week.
What changed
Meta releases the Marketing API in numbered versions, and versions get an end date. According to the version table in the Marketing API changelog, v24.0 was introduced on October 8, 2025 and was available until November 10, 2026.
The current version table looks like this:
- v27.0: introduced November 4, 2026, available until a date not yet announced (listed as TBD)
- v26.0: introduced July 29, 2026, available until TBD
- v25.0: introduced February 18, 2026, available until February 23, 2027
- v24.0: introduced October 8, 2025, available until November 10, 2026
The end of v24.0 came only days after v27.0 was released on November 4, 2026. Meta's versioning documentation explains the general rule: "When a new version of the Marketing API releases, Meta continues to support the previous version of the Marketing API for at least 90 days." Each version therefore has a window during which you can migrate, and v24.0's window has now closed.
What happens to calls made to v24.0
A deprecated version does not always mean a failed request. Meta's versioning page says that "Starting May 2024, Meta enables the auto-version upgrade feature for Marketing API endpoints that are not affected between versions." In Meta's words, this means that "if an endpoint is not affected, the platform will upgrade the call to the next available version, rather than directly failing the request."
There are two practical limits to that safety net:
- It only covers endpoints that are not affected by changes between versions. To check which endpoints are affected at each version, Meta refers developers to the Marketing API changelog.
- It can be switched off. Meta notes that you can disable the version auto-upgrade via the Marketing API Version setting under Marketing API App Product Page > Settings.
When a call is upgraded, Meta adds a response header, X-Ad-Api-Version-Warning, with the message that the call has been auto-upgraded because the requested version has been deprecated. That header shows that something in your stack is still pinned to an old version.
Who it affects
This matters most to teams that build or maintain their own integrations with the Marketing API:
- In-house scripts that create campaigns, ad sets and ads, or pull reporting data
- Agency tools that publish ads across many client ad accounts
- Reporting pipelines and dashboards that read insights through the API
- Third-party tools you pay for, which may or may not have moved to a newer version
If you rely on any external tool, it is worth asking the vendor which Marketing API version it uses.
What to do now
A short checklist for media buyers, ad ops leads and the developers who support them:
- Find every place that calls the API. List scripts, scheduled jobs, internal tools and paid tools. Look for request URLs that include a version string such as v24.0.
- Check response headers. Log the X-Ad-Api-Version-Warning header. If it appears, the call was auto-upgraded and the code should be updated to request a current version explicitly.
- Confirm your auto-upgrade setting. Open the Marketing API Version setting under Marketing API App Product Page > Settings and check whether auto-upgrade is enabled for your app. Decide on purpose whether you want it on.
- Read the changelog for the versions you skip. Moving from v24.0 to a current version can mean taking on the changes in each version in between. Review the Marketing API changelog entries for those versions, with extra attention to endpoints you use for creating ads.
- Test ad creation end to end. Create a small set of test ads in a paused state and compare the result in Ads Manager with what your script intended: placements, creative settings, budgets and tracking.
- Plan the next date. The changelog lists v25.0 as available until February 23, 2027. If you are moving off v24.0 now, move to the newest version you can test, not just the next one, so you are not repeating this work in a few months.
- Ask your vendors. For any paid tool that publishes or reports on ads, ask which version it calls and how it handles Meta's version end dates.
How this relates to bulk launching with Kapao
Kapao publishes ads through Meta's Marketing API to your own ad account, using the access you grant when you connect. Ads are created paused, so they can be checked in Ads Manager before they go live. If you currently run custom scripts for bulk uploads and are now facing a migration, you can compare what Kapao covers on the bulk upload page and the full list of features on /facts.