/graphql-unstable → version retirement
CircleCI API
Stops working
On January 1, 2027, the /graphql-unstable endpoint will reach end of life and will no longer be supported. Requests made to this endpoint after that date will fail.
Calls it hits
/graphql-unstable
What to use instead of these calls
Migrate to the CircleCI V3 REST API, which provides equivalent and expanded functionality with stable, versioned endpoints.
In CircleCI API's words
The CircleCI GraphQL Unstable API (https://circleci.com/graphql-unstable) will reach end of life on January 1, 2027 and will no longer be supported or accessible after that date.
Facts
- API
- CircleCI API
circleci.com - Kind
- Version retirement
- Announced
- September 3, 2026
- Takes effect
- January 1, 2027
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against CircleCI API's own pages
Questions
When does this change take effect?
Calls to /graphql-unstable on CircleCI API stop working on January 1, 2027.
What happens to calls after January 1, 2027?
They fail from that day.
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 CircleCI API 6
-
POST /api/v1.1/project/:vcs-type/:username/:repoEndpoint removal Stops workingin 98 days -
POST /api/v1.1/project/:vcs-type/:username/:repo/:build_num/retryEndpoint removal Stops workingin 98 days -
POST /api/v1.1/project/:vcs-type/:username/:repo/:build_num/sshEndpoint removal Stops workingin 98 days -
POST /api/v1.1/project/:vcs-type/:username/:repo/buildEndpoint removal Stops workingin 98 days -
POST /api/v1.1/project/:vcs-type/:username/:repo/tree/:branchEndpoint removal Stops workingin 98 days -
POST /api/v1/project/:username/:repoEndpoint removal Stops workingin 98 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 January 1, 2027.