How to rewrite CircleCI v1/v1.1 trigger and rerun paths

Use this when scripts or third-party tools still POST CircleCI /api/v1 or /api/v1.1 trigger and rerun endpoints that will return 410 Gone after 2027-02-01. Local rewriter only. Re-check the CircleCI Changelog and API guides.

1. Step 1. Confirm February 1 2027 removal (extended from the earlier November 1 2026 communication) and the list of ten endpoints on the Changelog.
2. Step 2. Grep scripts, internal tools, and vendor integrations for the listed v1/v1.1 project build/retry/ssh/tree paths.
3. Step 3. Paste matches into the home rewriter and choose cloud (prefer API v3) or server (API v2 only).
4. Step 4. Rewrite triggers to POST .../pipeline/run (v2) or POST /api/v3/runs. Update project addressing from username/repo to provider/org/project or UUIDs.
5. Step 5. Rewrite retry/ssh calls to workflow-level rerun APIs. Map SSH flags: enable_ssh (v2) or is_ssh_enabled (v3). Stop keying retries by build_num alone.
6. Step 6. Watch Deprecation and Sunset response headers already returned by legacy endpoints; add alerts for future 410s.
7. Step 7. Smoke-trigger a non-prod pipeline with the new path; keep scope clear that other v1/v1.1 endpoints are not removed by this change.
8. Step 8. Export Markdown into the migration ticket with Changelog and API guide links.

Related: FAQ · Use cases · Home tool. Always prefer official vendor documentation for authoritative dates.