CircleCI API
/api/v1.1/* version retirement
Deprecated, no dateSubscribe to CircleCI APIShare
CircleCI deprecated the /api/v1.1/* endpoints without a shutdown date. CircleCI API noted that API v1.1 is planned for End-Of-Life (EOL), with discontinuation details to follow. Once retired, calls to these endpoints fail.
Calls it hits
/api/v1.1/*
What to use instead of these calls
Move the calls to API v3 or API v2. For example, trigger pipelines using POST /api/v2/project/{project-slug}/pipeline instead of the v1.1 project build endpoints.
In CircleCI API's words
API v1.1 is planned for End-Of-Life (EOL); CircleCI will communicate the discontinuation date in the future.
Facts
- API
- CircleCI API
circleci.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against CircleCI API's own pages
Questions
When does this change take effect?
CircleCI API deprecated /api/v1.1/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: CircleCI API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from CircleCI API 10
-
/graphql-unstableVersion retirement Stops workingin 56 days -
POST /api/v1.1/project/:vcs-type/:username/:repoRemoval Stops workingin 87 days -
POST /api/v1.1/project/:vcs-type/:username/:repo/:build_num/retryEndpoint removal Stops workingin 87 days -
POST /api/v1.1/project/:vcs-type/:username/:repo/:build_num/sshEndpoint removal Stops workingin 87 days -
POST /api/v1.1/project/:vcs-type/:username/:repo/buildEndpoint removal Stops workingin 87 days -
POST /api/v1.1/project/:vcs-type/:username/:repo/tree/:branchEndpoint removal Stops workingin 87 days -
POST /api/v1/project/:username/:repoRemoval Stops workingin 87 days -
POST /api/v1/project/:username/:repo/:build_num/retryEndpoint removal Stops workingin 87 days -
POST /api/v1/project/:username/:repo/:build_num/sshEndpoint removal Stops workingin 87 days -
POST /api/v1/project/:username/:repo/buildEndpoint removal Stops workingin 87 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.