Bitbucket Cloud API
GET /2.0/addon/linkers/{id} endpoint removal
Deprecated, no dateSubscribe to Bitbucket Cloud APIShare
Bitbucket Cloud API deprecated GET /2.0/addon/linkers/{id} without giving a shutdown date yet.
Calls it hits
GET /2.0/addon/linkers/{id}
In Bitbucket Cloud API's words
GET /2.0/addon/linkers/{linker_key}
Facts
- API
- Bitbucket Cloud API
api.bitbucket.org - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Bitbucket Cloud API's own pages
Questions
When does this change take effect?
Bitbucket Cloud API deprecated GET /2.0/addon/linkers/{id} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Bitbucket Cloud 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 Bitbucket Cloud API 10
-
GET /2.0/repositoriesEndpoint removal Stopped working -
GET /2.0/user/permissions/workspacesEndpoint removal Stopped working -
GET /2.0/workspacesEndpoint removal Stopped working -
/2.0/addon/linkers*Endpoint removal Stopped working -
/2.0/repositories/{id}/{id}/issues*Endpoint removal Stopped working -
No date
DELETE /2.0/addon/linkers/{id}/valuesEndpoint removal Deprecated, no date -
No date
GET /2.0/addon/linkersEndpoint removal Deprecated, no date -
No date
GET /2.0/addon/linkers/{id}/valuesEndpoint removal Deprecated, no date -
No date
GET /2.0/addon/linkers/{id}/values/{id}Endpoint removal Deprecated, no date -
No date
POST /2.0/addon/linkers/{id}/valuesEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.