Meta Graph API
/v2.0/* version retirement
RedirectedSubscribe to Meta Graph APIShare
On August 8, 2016, Meta retired version v2.0 of the Graph API. Requests targeting /v2.0/* endpoints were not rejected, but Meta Graph API began redirecting them to be answered from a newer version. Following this date, incoming calls to these paths are served by the oldest version that remains available.
Calls it hits
/v2.0/*
What to use instead of these calls
Update requests to call a supported version, such as v26.0.
Facts
- API
- Meta Graph API
graph.facebook.com - Kind
- Version retirement
- Takes effect
- August 8, 2016
- 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 August 8, 2016, Meta Graph API answers calls to /v2.0/* from a newer version.
What happens to calls after August 8, 2016?
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
-
/v1.0/*Version retirement Redirected -
/v2.1/*Version retirement Redirected -
/v2.2/*Version retirement Redirected -
/v2.3/*Version retirement Redirected -
/v2.4/*Version retirement Redirected -
/v2.5/*Version retirement Redirected -
/v2.6/*Version retirement Redirected -
/v2.7/*Version retirement Redirected -
/v2.8/*Version retirement Redirected -
/v2.9/*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.