API sunsets · Meta · checked

Meta Marketing API v24.0 expiry on 6 October 2026

Meta Marketing API v24.0 expired on 6 October 2026. Since then, calls to endpoints the next version did not change are upgraded to it, silently but for one header; and calls to endpoints the next version changed fail. The failure is partly silent: some calls are upgraded without an error, and the rest fail. Meta names v26.0 as the replacement (the latest Marketing API version on 8 October 2026, released 29 July 2026). The date has passed, so v24.0 can no longer be recorded as it was; compare the responses you still have with what v26.0 returns. Find every place your code pins v24.0: npx --allow-git=root github:agentwares/api-sunset scan

$ npx --allow-git=root github:agentwares/api-sunset scan

npx --allow-git=root github:agentwares/api-sunset scan lists every API version your code and config pin (Shopify, Meta Graph, Google Ads, HubSpot, Stripe and the rest of this list) with its end date, what breaks and this page's link. It needs no account and no API key, reads your files on your machine and sends nothing; its one request fetches this data. Free and MIT licensed.

The facts

API
Meta Marketing APICovers ads endpoints at graph.facebook.com/<version>/.
Version
v24.0Released 8 October 2025.
Ended
6 October 2026
After the date
falls forward, calls fail
Silent?
Partly: some calls are upgraded without an error, the rest fail
Answered by
v25.0The oldest version still usable on 9 October 2026; on the day after the date it was v25.0.
Replacement
v26.0the latest Marketing API version on 8 October 2026, released 29 July 2026

What breaks after 6 Oct 2026

How to upgrade

  1. Find every place your code and config pin v24.0: npx --allow-git=root github:agentwares/api-sunset scan prints each file and line, and the variable name for a .env file, never its value.
  2. Read what changed between v24.0 and v26.0 in Meta's notes, and list the calls that touch it.
  3. v24.0 no longer answers as it did, so compare the responses you logged before 6 October 2026 with what v26.0 returns now.
  4. Change the version string, deploy, and watch the first day's responses.

Record your real calls on the old version before the date, and replay them on the new one.

agentcheck runs scheduled checks of an endpoint. A check sends the request you define (a path or a full URL, a method and a body, with your API key as a header, stored encrypted) on a schedule and compares each response with a golden: exact text, contains, a regular expression or a JSON Schema, none of which costs an LLM call. When a response stops matching, it opens an incident and alerts you. Point one check at v24.0 and one at v26.0 with the same golden, and you see which of your calls answer differently before 6 October 2026.

Free: 1 monitored target, hourly checks, badge and public status page. Starter: 3 targets, 5-minute checks, Slack and Discord alerts, 30-day history. Recording the calls your code already makes is a different path: the trace import (POST /api/v1/targets/{id}/traces, or the agentcheck_record MCP tool) takes agent traces, a prompt and an answer, and turns them into checks judged by the LLM judge (Pro). It does not take raw HTTP requests and responses, so for an API the scheduled checks are the way in today.

Migration watch is not built. It would record the calls your code makes to Meta Marketing API v24.0 and replay them on v26.0 until 6 October 2026, with nothing to set up, and email you what answers differently. If you would pay for that, say so with one click. The click is counted; nothing else is sent or stored.

Other Meta dates

Every API sunset, by date

Sources

Built only from Meta's own pages. No intent is implied: a date is what the page says on the day it was read. Data: /apis/sunsets.json.

api-sunset is a free tool from agentcheck, which runs scheduled checks of your endpoints and alerts you when an answer changes.