Steps

Confirm the official policy at developers.facebook.com/docs/graph-api/guides/versioning: each Graph API version is guaranteed to operate for at least two years, expiring two years after the next version's release
Check your integration's pinned API version against its specific changelog page (developers.facebook.com/docs/graph-api/changelog/version{N}) for its exact expiration date rather than assuming the two-year rule applies uniformly
Use v9.0 as a concrete reference point: released November 10, 2020, available until February 23, 2023
If you use the Marketing API specifically, track its expiration separately from the core Graph API, since the two have independent clocks even for the same version number (e.g., v9.0 Marketing API expired August 25, 2021, over a year before v9.0 Graph API)
Don't rely on graceful failure after expiration for the Marketing API — unlike core Graph API (which silently falls back to the oldest still-usable version), Marketing API throws errors on expired versions

Known gotchas

Graph API and Marketing API expiration clocks are independent even for the same version number — check both if you use both
Expired Graph API versions don't error, they silently fall back to the oldest supported version, which can quietly change behavior without an obvious failure
Not every version changelog page has a hard "Available until" date yet (some show "TBD") — don't assume a date exists just because the version is old

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Track Facebook Graph API version expirations to avoid silent behavior changes on old integrations

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?