KuCoin API
GET /api/v3/etf/info endpoint removal
Deprecated, no dateSubscribe to KuCoin APIShare
KuCoin API deprecated GET /api/v3/etf/info without giving a shutdown date yet.
Calls it hits
GET /api/v3/etf/info
What to use instead of these calls
Stop relying on GET /api/v3/etf/info; KuCoin names no replacement.
KuCoin names no replacement for leveraged token (ETF) info, so what to read instead is the team's call.
In KuCoin API's words
Get ETF Info: Deprecated the /api/v3/etf/info endpoint.
Facts
- API
- KuCoin API
api.kucoin.com - Kind
- Endpoint removal
- Announced
- May 8, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against KuCoin API's own pages
Questions
When does this change take effect?
KuCoin API deprecated GET /api/v3/etf/info without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: KuCoin 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 API 10
-
GET /api/v1/isolated/account/{id}Endpoint removal Stopped working -
GET /api/v1/isolated/accountsEndpoint removal Stopped working -
POST /api/v1/margin/orderEndpoint removal Stopped working -
POST /api/v1/margin/order/testEndpoint removal Stopped working -
POST /api/v1/hf/orders*Parameter removal Stopped working -
POST /api/v3/hf/margin/order*Parameter removal Stopped working -
POST /api/v1/hf/orders*Parameter removal Stopped working -
POST /api/v3/hf/margin/order*Parameter removal Stopped working -
No date
/api/v1/margin/lend*Endpoint removal Deprecated, no date -
No date
GET /api/v1/hf/orders/activeEndpoint 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.