Time to Bail · Boarding pass
Act. You can stay.
Every request to graphql-unstable fails from January 1, 2027. Move to the V3 REST API first.[1]
Act means: change a setting or plan before the date. You can stay.
CircleCI GraphQL Unstable API shuts down January 1, 2027
CircleCI ends its GraphQL Unstable API at circleci.com/graphql-unstable on January 1, 2027. After that, every request fails. CircleCI asks you to move to the V3 REST API and to upgrade the CircleCI CLI from V0 to V1. CircleCI server is not affected.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
Tick steps as you go. Your progress stays in this browser.
Search code and scripts for graphql-unstable.
Find the V3 REST API endpoint for each query or mutation you use.
Move from CircleCI CLI V0 to V1.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
| End of support | January 1, 2027[1] |
|---|---|
| Endpoint | https://circleci.com/graphql-unstable[1] |
| After January 1, 2027 | Endpoint shut down; all requests fail[1] |
| Move to | CircleCI V3 REST API[1] |
| CircleCI CLI | Upgrade to V1 if you still use V0[1] |
| CircleCI server | Not affected[1] |
| Announced | September 3, 2026[1] |
| Integrations, scripts and tools that call it | Stop working after January 1, 2027[1] |
Every request to https://circleci.com/graphql-unstable fails. Integrations, scripts and tools that call it stop working.
graphql-unstable.Source: [1] Deprecation of GraphQL Unstable API - January 1st, 2027 (CircleCI)
Check it yourself. Every fact above links here.
Time to bail on Tools that call CircleCI's graphql-unstable API? Act. You can stay. Every request to graphql-unstable fails from January 1, 2027. Move to the V3 REST API first.
On our scale this is Act: change a setting or plan before the date. You can stay.
CircleCI ends its GraphQL Unstable API at circleci.com/graphql-unstable on January 1, 2027. After that, every request fails. CircleCI asks you to move to the V3 REST API and to upgrade the CircleCI CLI from V0 to V1. CircleCI server is not affected.
Here are the facts we checked:
You can stay on CircleCI. You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
CircleCI is the main source for this page. CircleCI has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Integrations, scripts and tools that call it: Stop working after January 1, 2027.
The date to remember is January 1, 2027. Make the change before then.
A few tips:
If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.
If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.
Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.
Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.
No questions collected yet.
Thanks.
Run SaaS spend at work? Get these changes before the invoice
Arrivals · for builders
People on Tools that call CircleCI's graphql-unstable API can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.
Listing is free. An editor checks it. Not ranked. Not paid.
One email when we publish a checked change in the category you pick. No account needed.
One email on Mondays: the gates in the next 14 days, with the first step for each.