Meta Graph API
/v10.0/* version retirement
RedirectedSubscribe to Meta Graph APIShare
On June 8, 2023, Meta retired Graph API version v10.0. Requests made to /v10.0/* are no longer served by version v10.0 directly. Instead, Meta Graph API redirects these calls and answers them from a newer version.
Calls it hits
/v10.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
- June 8, 2023
- 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 June 8, 2023, Meta Graph API answers calls to /v10.0/* from a newer version.
What happens to calls after June 8, 2023?
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
-
/v5.0/*Version retirement Redirected -
/v6.0/*Version retirement Redirected -
/v7.0/*Version retirement Redirected -
/v8.0/*Version retirement Redirected -
/v9.0/*Version retirement Redirected -
/v11.0/*Version retirement Redirected -
/v12.0/*Version retirement Redirected -
/v13.0/*Version retirement Redirected -
/v14.0/*Version retirement Redirected -
/v15.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.