Meta Graph API
/v24.0/* version retirement
RedirectsSubscribe to Meta Graph APIShare
On February 18, 2028, Meta Graph API calls to /v24.0/* will be redirected to a newer version. Requests made to this version after that day will not fail immediately, as Meta Graph API will answer them using a newer version instead.
Calls it hits
/v24.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
- February 18, 2028
- 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?
From February 18, 2028, Meta Graph API answers calls to /v24.0/* from a newer version.
What happens to calls after February 18, 2028?
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 -
/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 -
/v25.0/*Version retirement Redirectsin 631 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before February 18, 2028.