Meta Graph API
/v20.0/* version retirement
RedirectedSubscribe to Meta Graph APIShare
On September 24, 2026, Meta Graph API retired version v20.0. Requests directed to /v20.0/* are now redirected, with Meta answering them from a newer version rather than serving them directly from v20.0.
Calls it hits
/v20.0/*
What to use instead of these calls
Update your requests to call a supported version, such as v26.0. Past this day, Meta answers these calls with the oldest version still available.
Facts
- API
- Meta Graph API
graph.facebook.com - Kind
- Version retirement
- Takes effect
- September 24, 2026
- 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 September 24, 2026, Meta Graph API answers calls to /v20.0/* from a newer version.
What happens to calls after September 24, 2026?
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
-
/v15.0/*Version retirement Redirected -
/v16.0/*Version retirement Redirected -
/v17.0/*Version retirement Redirected -
/v18.0/*Version retirement Redirected -
/v19.0/*Version retirement Redirected -
/v21.0/*Version retirement Redirectsin 76 days -
/v22.0/*Version retirement Redirectsin 195 days -
/v23.0/*Version retirement Redirectsin 336 days -
/v24.0/*Version retirement Redirectsin 469 days -
/v25.0/*Version retirement Redirectsin 631 days
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.