Meta Graph API: Graph API v16.0 is redirected to a newer version

Calls it hits

/v16.0/*

What to use instead of these calls

Call a supported version, such as v26.0. Past this day, Meta answers with the oldest version still available.

Facts

API: Meta Graph API graph.facebook.com
Kind: Version retirement
Takes effect: May 14, 2025
Calls after that day: Answered by a newer version
Source: Lifecycle page
Last updated: October 24, 2026
Verified: November 6, 2026, against Meta Graph API's own pages

Questions

When does this change take effect?

Since May 14, 2025, Meta Graph API answers calls to /v16.0/* from a newer version.

What happens to calls after May 14, 2025?

Meta Graph API answers them from a newer version. The response can differ from what your code expects.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

More from Meta Graph API 10

Sep 14, 2023 /v11.0/*Version retirement Redirected
Feb 8, 2024 /v12.0/*Version retirement Redirected
May 28, 2024 /v13.0/*Version retirement Redirected
Sep 17, 2024 /v14.0/*Version retirement Redirected
Nov 20, 2024 /v15.0/*Version retirement Redirected
Sep 12, 2025 /v17.0/*Version retirement Redirected
Jan 26, 2026 /v18.0/*Version retirement Redirected
May 21, 2026 /v19.0/*Version retirement Redirected
Sep 24, 2026 /v20.0/*Version retirement Redirected
Jan 21, 2027 /v21.0/*Version retirement Redirectsin 76 days

You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub

Meta Graph API /v16.0/* version retirement