KuCoin Futures API
GET /api/v1/broker/api/rebase/download endpoint removal
Deprecated, no dateSubscribe to KuCoin Futures APIShare
KuCoin Futures API announced on September 26, 2025, that endpoint GET /api/v1/broker/api/rebase/download is deprecated without a shutdown date. Calls made to this route are slated to fail upon eventual removal. This change specifically impacts brokers using the v1 rebase download endpoint.
Calls it hits
GET /api/v1/broker/api/rebase/download
What to use instead of these calls
Use the GET /api/v2/broker/api/rebase/download endpoint instead.
In KuCoin Futures API's words
Deprecated the [GET /api/v1/broker/api/rebase/download](/docs-new/3470280e0) endpoint. Please use [GET /api/v2/broker/api/rebase/download](/docs-new/rest/broker/api-broker/get-broker-rebate) endpoint instead.
Facts
- API
- KuCoin Futures API
api-futures.kucoin.com - Kind
- Endpoint removal
- Announced
- September 26, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against KuCoin Futures API's own pages
Questions
When does this change take effect?
KuCoin Futures API deprecated GET /api/v1/broker/api/rebase/download without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: KuCoin Futures 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 KuCoin Futures API 4
-
POST /api/v1/orders*Parameter removal Stopped working -
POST /api/v1/orders*Parameter removal Stopped working -
No date
DELETE /api/v1/ordersEndpoint removal Deprecated, no date -
No date
GET /api/v3/etf/infoEndpoint 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.