Meta Graph API
/v3.1/* version retirement
RedirectedSubscribe to Meta Graph APIShare
On October 27, 2020, Graph API v3.1 reached retirement. Requests targeting /v3.1/* were redirected, with Meta Graph API answering them from a newer version. Calls made to this version no longer run on v3.1.
Calls it hits
/v3.1/*
What to use instead of these calls
Call a supported version, such as v26.0. Past this date, Meta answers with the oldest version still available.
Facts
- API
- Meta Graph API
graph.facebook.com - Kind
- Version retirement
- Takes effect
- October 27, 2020
- 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 October 27, 2020, Meta Graph API answers calls to /v3.1/* from a newer version.
What happens to calls after October 27, 2020?
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
-
/v2.9/*Version retirement Redirected -
/v2.10/*Version retirement Redirected -
/v2.11/*Version retirement Redirected -
/v2.12/*Version retirement Redirected -
/v3.0/*Version retirement Redirected -
/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
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.