timetobail
My stack

CircleCI · Forced move · Announced October 7, 2026 · Sources checked Oct 17

Time to bail on CircleCI API v1 and v1.1 trigger and rerun calls?

Time to Bail · Boarding pass

FromCircleCI API v1 and v1.1 trigger and rerun calls
ToYour pick

Act. You can stay.

These endpoints return HTTP 410 Gone from February 1, 2027. Move the calls to API v2 or v3 first.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
Removal
Time left
106days
Status
Act

CircleCI v1 and v1.1 trigger and rerun APIs end February 1, 2027

CircleCI removes 10 legacy API v1 and v1.1 endpoints that trigger and rerun builds on February 1, 2027. After that, they return HTTP 410 Gone. The date was moved from November 1, 2026. Other v1 endpoints and API v2 and v3 are not affected.

Email me 7 days before Feb 1

One email with the first steps. Nothing else.

We email you one link to confirm (double opt-in). Nothing starts until you click it. Unsubscribe any time. How we use your email.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

How it is winding down

  1. Oct 7, 2026AnnouncedDone
  2. Nov 1, 2026Earlier dateNext
  3. Feb 1Removal

What to do before February 1

Tick steps as you go. Your progress stays in this browser.

  1. Find the calls

    Search CI scripts and tools for /api/v1/project/ and /api/v1.1/project/.

  2. Trigger with v2 or v3

    Use POST /api/v3/runs on cloud, or the API v2 pipeline/run endpoint on server.

  3. Rerun by workflow

    Use the v3 or v2 workflow rerun endpoint. Set enable_ssh (v2) or is_ssh_enabled (v3) for SSH.

Email me 7 days before Feb 1

One email with the first steps. Nothing else.

We email you one link to confirm (double opt-in). Nothing starts until you click it. Unsubscribe any time. How we use your email.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

Facts we checked

Facts and their sources
RemovalFebruary 1, 2027[1]
Endpoints removed10 POST endpoints in API v1 and v1.1: project root, build, tree/:branch, retry and ssh[1]
After removalRequests return HTTP 410 Gone[1]
Earlier dateNovember 1, 2026, sent by email; now extended[1]
NowThese endpoints send Deprecation and Sunset headers[1]
Trigger instead withPOST /api/v3/runs (API v3) or POST /api/v2/project/:provider/:organization/:project/pipeline/run (API v2)[1]
Rerun instead withPOST /api/v3/workflows/:id/rerun (API v3) or POST /api/v2/workflow/:workflow-id/rerun (API v2)[1]
CircleCI serverAffected too; use API v2, since API v3 is cloud only[1]
Not affectedOther v1 and v1.1 endpoints, API v2 and API v3[1]
AnnouncedOctober 7, 2026[1]
Scripts that use these endpointsGet HTTP 410 Gone from February 1, 2027[1]

After February 1, 2027 you will see

Calls to these v1 and v1.1 endpoints get HTTP 410 Gone. Builds you trigger or rerun this way do not start.

Fix

  1. Search scripts and tools for /api/v1/project/ and /api/v1.1/project/.
  2. Trigger with POST /api/v3/runs, or POST /api/v2/project/:provider/:organization/:project/pipeline/run.
  3. Rerun with POST /api/v3/workflows/:id/rerun or POST /api/v2/workflow/:workflow-id/rerun.
  4. Change how you name the project: v2 uses :provider/:organization/:project, v3 uses UUIDs.

Source: [1] Deprecation of v1 and v1.1 Trigger and Rerun APIs, February 1, 2027 (CircleCI)

Sources

Check it yourself. Every fact above links here.

  1. Deprecation of v1 and v1.1 Trigger and Rerun APIs, February 1, 2027 CircleCI · primary · checked Oct 17
Read the published editorial report

What changed

Time to bail on CircleCI API v1 and v1.1 trigger and rerun calls? Act. You can stay. These endpoints return HTTP 410 Gone from February 1, 2027. Move the calls to API v2 or v3 first.

On our scale this is Act: change a setting or plan before the date. You can stay.

CircleCI removes 10 legacy API v1 and v1.1 endpoints that trigger and rerun builds on February 1, 2027. After that, they return HTTP 410 Gone. The date was moved from November 1, 2026. Other v1 endpoints and API v2 and v3 are not affected.

Here are the facts we checked:

  • Removal: February 1, 2027 (CircleCI)
  • Endpoints removed: 10 POST endpoints in API v1 and v1.1: project root, build, tree/:branch, retry and ssh (CircleCI)
  • After removal: Requests return HTTP 410 Gone (CircleCI)
  • Earlier date: November 1, 2026, sent by email; now extended (CircleCI)
  • Now: These endpoints send Deprecation and Sunset headers (CircleCI)
  • Trigger instead with: POST /api/v3/runs (API v3) or POST /api/v2/project/:provider/:organization/:project/pipeline/run (API v2) (CircleCI)
  • Rerun instead with: POST /api/v3/workflows/:id/rerun (API v3) or POST /api/v2/workflow/:workflow-id/rerun (API v2) (CircleCI)
  • CircleCI server: Affected too; use API v2, since API v3 is cloud only (CircleCI)
  • Not affected: Other v1 and v1.1 endpoints, API v2 and API v3 (CircleCI)
  • Announced: October 7, 2026 (CircleCI)
  • Scripts that use these endpoints: Get HTTP 410 Gone from February 1, 2027 (CircleCI)

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.

Who is affected

Scripts that use these endpoints: Get HTTP 410 Gone from February 1, 2027.

The date to remember is February 1, 2027. Make the change before then.

What to do before February 1

  1. Find the calls. Search CI scripts and tools for /api/v1/project/ and /api/v1.1/project/.
  2. Trigger with v2 or v3. Use POST /api/v3/runs on cloud, or the API v2 pipeline/run endpoint on server.
  3. Rerun by workflow. Use the v3 or v2 workflow rerun endpoint. Set enable_ssh (v2) or is_ssh_enabled (v3) for SSH.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

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.

Options people mention

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.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on CircleCI API v1 and v1.1 trigger and rerun calls 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.

Open the playbookList your product