Meta Graph API
/v8.0/* version retirement
RedirectedSubscribe to Meta Graph APIShare
On November 1, 2022, Meta Graph API retired version v8.0. Calls targeting /v8.0/* are no longer served by that version and are redirected to a newer version instead. Requests sent to these endpoints now receive responses generated by the oldest available release.
Calls it hits
/v8.0/*
What to use instead of these calls
Update your calls to target a supported version, such as v26.0. After this date, Meta automatically serves requests using the oldest version still available.
Facts
- API
- Meta Graph API
graph.facebook.com - Kind
- Version retirement
- Takes effect
- November 1, 2022
- Calls after that day
- Answered by a newer version
- Source
- Lifecycle page
- Last updated
- Verified
- , against Meta Graph API's own pages
Questions
When does this change take effect?
Since November 1, 2022, Meta Graph API answers calls to /v8.0/* from a newer version.
What happens to calls after November 1, 2022?
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
-
/v3.2/*Version retirement Redirected -
/v3.3/*Version retirement Redirected -
/v4.0/*Version retirement Redirected -
/v5.0/*Version retirement Redirected -
/v6.0/*Version retirement Redirected -
/v7.0/*Version retirement Redirected -
/v9.0/*Version retirement Redirected -
/v10.0/*Version retirement Redirected -
/v11.0/*Version retirement Redirected -
/v12.0/*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.