Meta Graph API
/v18.0/* version retirement
RedirectedSubscribe to Meta Graph APIShare
On January 26, 2026, version v18.0 of the Graph API reaches its retirement date. This change affects calls to /v18.0/*. After that day, requests are redirected, and Meta Graph API answers them using the oldest version still available rather than serving v18.0.
Calls it hits
/v18.0/*
What to use instead of these calls
Call a supported version instead, such as v26.0. Past the retirement date, Meta answers these requests with the oldest version still available.
Facts
- API
- Meta Graph API
graph.facebook.com - Kind
- Version retirement
- Takes effect
- January 26, 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 January 26, 2026, Meta Graph API answers calls to /v18.0/* from a newer version.
What happens to calls after January 26, 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
-
/v13.0/*Version retirement Redirected -
/v14.0/*Version retirement Redirected -
/v15.0/*Version retirement Redirected -
/v16.0/*Version retirement Redirected -
/v17.0/*Version retirement Redirected -
/v19.0/*Version retirement Redirected -
/v20.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
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.