CircleCI API · circleci.com
CircleCI API v1.1 deprecations
The breaking changes CircleCI API announced for its v1.1 endpoints: 6 of the 12 Okapi tracks.
Coming up 5
-
POST /api/v1.1/project/:vcs-type/:username/:repoEndpoint removal Stops workingin 95 days -
POST /api/v1.1/project/:vcs-type/:username/:repo/:build_num/retryEndpoint removal Stops workingin 95 days -
POST /api/v1.1/project/:vcs-type/:username/:repo/:build_num/sshEndpoint removal Stops workingin 95 days -
POST /api/v1.1/project/:vcs-type/:username/:repo/buildEndpoint removal Stops workingin 95 days -
POST /api/v1.1/project/:vcs-type/:username/:repo/tree/:branchEndpoint removal Stops workingin 95 days
Deprecated, no date yet 1
-
No date
/api/v1.1/*Version retirement Deprecated, no date
Questions
Is the CircleCI API v1.1 deprecated?
CircleCI API has announced 6 breaking changes to its v1.1 endpoints: 5 with a shutdown date, 1 deprecated without one. Each one's page says what to use instead.
When do CircleCI API v1.1 endpoints stop working?
The next is POST /api/v1.1/project/:vcs-type/:username/:repo endpoint removal, on February 1, 2027.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls these changes hit and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub