Meta Graph API: Graph API v2.8 is redirected to a newer version

Calls it hits

/v2.8/*

What to use instead of these calls

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

Facts

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

Questions

When does this change take effect?

Since April 18, 2019, Meta Graph API answers calls to /v2.8/* from a newer version.

What happens to calls after April 18, 2019?

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

Oct 9, 2017 /v2.4/*Version retirement Redirected
Apr 12, 2018 /v2.5/*Version retirement Redirected
Jul 13, 2018 /v2.6/*Version retirement Redirected
Oct 5, 2018 /v2.7/*Version retirement Redirected
Jul 22, 2019 /v2.9/*Version retirement Redirected
Nov 7, 2019 /v2.10/*Version retirement Redirected
Jan 28, 2020 /v2.11/*Version retirement Redirected
May 5, 2020 /v2.12/*Version retirement Redirected
Jul 28, 2020 /v3.0/*Version retirement Redirected
Oct 27, 2020 /v3.1/*Version retirement Redirected

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 /v2.8/* version retirement