ClickHouse Cloud API
GET /v1/organizations/{id}/activeBalances endpoint removal
Deprecated, no dateSubscribe to ClickHouse Cloud APIShare
ClickHouse Cloud deprecated the GET /v1/organizations/{id}/activeBalances endpoint without announcing a shutdown date. Requests to this path will eventually fail once the removal is finalized. It impacts callers currently retrieving balance details via this route.
Calls it hits
GET /v1/organizations/{id}/activeBalances
What to use instead of these calls
Call GET /v1/organizations/{organizationId}/creditBalances instead.
In ClickHouse Cloud API's words
DEPRECATED. Use the `/v1/organizations/{organizationId}/creditBalances` endpoint instead.
Facts
- API
- ClickHouse Cloud API
api.clickhouse.cloud - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against ClickHouse Cloud API's own pages
Questions
When does this change take effect?
ClickHouse Cloud API deprecated GET /v1/organizations/{id}/activeBalances without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: ClickHouse 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 ClickHouse Cloud API 1
-
GET /v1/organizations/{id}/prometheusEndpoint removal Stops workingin 56 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.