FAQ

Which endpoints return 410 after February 1 2027?

Ten legacy trigger and rerun endpoints under /api/v1 and /api/v1.1 project build/retry/ssh/tree paths listed on the Changelog. After removal they return HTTP 410 Gone.

Should cloud customers use API v3 or v2 for triggers?

Cloud customers are encouraged to start with v3 runs. API v2 remains supported when v3 does not cover a need. CircleCI server customers should use API v2 because v3 is cloud-only.

How do I replace build_num retry with workflow rerun?

Reruns become workflow-based on v2/v3. You can choose which jobs to rerun instead of posting to a build_num retry path.

What are enable_ssh vs is_ssh_enabled?

They are the SSH-enabled rerun flags on v2 and v3 respectively. Use them when you previously posted to the legacy .../ssh endpoints.

Are all v1/v1.1 APIs being removed?

No. This change targets the listed trigger and rerun endpoints only. Other v1/v1.1 endpoints are unaffected, and API v2/v3 are unaffected.

Does this rewriter call CircleCI or store API tokens?

No. Paths are rewritten locally in your browser. We never send traffic to CircleCI or ask for tokens.

Is this official CircleCI documentation?

No. Unofficial local helper. Not affiliated with CircleCI.

Do you store pasted paths?

No. Text stays in the browser session until you copy Markdown out.