Bitrise API
GET /v0.1/apps/{id}/secrets/{id}/value endpoint removal
Deprecated, no dateSubscribe to Bitrise APIShare
Bitrise API deprecated the GET /v0.1/apps/{id}/secrets/{id}/value endpoint without a shutdown date, listing it under deprecated endpoints. This deprecation affects requests made to retrieve app secret values through this path. Once removed, calls to this endpoint fail.
Calls it hits
GET /v0.1/apps/{id}/secrets/{id}/value
What to use instead of these calls
Call GET /v0.1/apps/{app-slug}/secrets/{secret-name}, which returns the secret's details and its value when unprotected.
In Bitrise API's words
Deprecated endpoints—what’s going out
Facts
- API
- Bitrise API
api.bitrise.io - Kind
- Endpoint removal
- Announced
- October 31, 2024
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Bitrise API's own pages
Questions
When does this change take effect?
Bitrise API deprecated GET /v0.1/apps/{id}/secrets/{id}/value without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Bitrise 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 Bitrise API 2
-
No date
PUT /v0.1/apps/{id}/secrets/{id}Endpoint removal Deprecated, no date -
No date
/release-management/v1/*Version retirement 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.