timetobail
My stack

Playbook for makers · Forced move · free while in beta

Act

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

Readers can stay on CircleCI: they change a setting or plan. Help the ones who would rather leave.

106 days left · February 1, 2027 · Public page

Low switching pressure28/100

An estimate from the deadline, cost, discussion and need to move. It is not a product rating.

What goes into it

Confidence: medium.

deadline8/30
money14/25
attention0/25
audience0/12
force6/8
  • Hard deadline in 106 days.
  • The change is forced: it reaches users even if they wait.

  1. 1 Related discussions

    Only threads tied to this event that talk about leaving, moving or prices. Saved, not live. Check the date and read the thread before replying.

    No live threads yet.

  2. 2 What people ask

    No common questions yet.

  3. 3 Reply templates

    Answer the question first. Link only if it helps. Always keep the disclosure line. Never post the same text twice.

    Helpful first
    Sorry you have to deal with this. You can stay on CircleCI. Here is what to change before February 1, 2027:

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.

If they would rather leave, describe a verified way <your product> can help: <your link>
[Disclosure: I build <your product>.]
    Short answer
    You have until February 1, 2027. You can stay on CircleCI. First: find the calls. Then trigger with v2 or v3.
Happy to help if you get stuck.
[Disclosure: I build <your product>.]

  4. 4 Switch-page builder

    Create a draft “Switch from CircleCI” page. Add your product, review every claim, then copy HTML or Markdown. Your product claims need your own evidence.

    • Add your product name to replace “Your product”.
    Preview

    Switch from CircleCI to Your product

    CircleCI API v1 and v1.1 trigger and rerun calls: a change is due by February 1. You can stay on CircleCI. If you would rather leave, here is how to move to Your product.

    What changes at CircleCI

    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.

    • 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 if you make the change. This page is for people who would rather leave.

    What Your product gives you

    Write two or three short lines here. Say what Your product does, who it is for, and what it costs. Use only facts you can show.

    How to move from CircleCI to Your product

    1. Save what you need from CircleCI. Keep a copy before you cancel anything.
    2. Import into Your product. Say which files you accept and how long an import takes.

    Tell readers the key date: February 1, 2027.

    Questions people ask

    If Your product has a direct answer to one of these, add it here. Keep it short and true.

    How to help new users settle in

    Send one short email. Say what changed, where to find you now, and what they need to do. 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.

    Sources

  5. 5 Search ideas to validate

    suggested, not measured Phrases people may search when a tool changes like this. We have no search volume data for them.

    • circleci api v1 and v1.1 trigger and rerun calls
    • circleci alternative
    • circleci alternatives
    • circleci export
    • how to leave circleci
    • switch from circleci
    • circleci migration
    • circleci migration 2027