KuCoin Futures API
iceberg body parameter removal on POST /api/v1/orders*
Stopped workingSubscribe to KuCoin Futures APIShare
On August 3, 2026, KuCoin Futures API stopped supporting the iceberg body parameter on POST /api/v1/orders* endpoints. Requests that send this parameter now fail instead of being processed.
Calls it hits
POST /api/v1/orders*body parameter iceberg
What to use instead of these calls
Stop sending hidden, iceberg, and visibleSize on futures orders using POST /api/v1/orders and its test and batch variants, as KuCoin rejects them with error 400413.
In KuCoin Futures API's words
No longer supports the hidden, iceberg and visibleSize parameters.
Facts
- API
- KuCoin Futures API
api-futures.kucoin.com - Kind
- Parameter removal
- Announced
- August 3, 2026
- Takes effect
- August 3, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against KuCoin Futures API's own pages
Questions
When does this change take effect?
Calls to POST /api/v1/orders*, body parameter iceberg on KuCoin Futures API stopped working on August 3, 2026.
What happens to calls after August 3, 2026?
They have failed since August 3, 2026.
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 -
No date
DELETE /api/v1/ordersEndpoint removal Deprecated, no date -
No date
GET /api/v1/broker/api/rebase/downloadEndpoint removal Deprecated, no date -
No date
GET /api/v3/etf/infoEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.