KuCoin errors
KuCoin error codes in LootX: key, secret and passphrase, permissions and IP whitelist, insufficient spot and futures balance, contract volume and rate limits.
KuCoin responds with code and msg fields: code 200000 means success, anything else is a rejection. Codes are six-digit numbers, and a rejection often comes with HTTP status 200, so you need to look at the code. KuCoin spot and futures are separate APIs with different code sets: for example, insufficient balance is 200004 on spot and 300003 on futures.
A KuCoin key has three parts — key, secret and passphrase — and any of them can be wrong. If the terminal doesn’t recognize the rejection, the popup after “Order:” shows the exchange’s response verbatim: KuCoin API 200004: Balance insufficient or KuCoin POST /orders HTTP 400: {"code":"…","msg":"…"}. See Error messages: how to read them for the general approach, and Connecting exchanges and API keys for key setup.
What the terminal explains itself
| Situation | Codes | What you’ll see |
|---|---|---|
| Exchange didn’t recognize the key or passphrase | 400003, 400004 |
Card “…: exchange rejected the API key or secret — check them in connection settings”, and a tooltip “Exchange rejected the API key or secret” on the connection in Settings → Connections |
| Invalid signature | 400005 |
Same card on connection; on an order — “Order rejected: invalid API key or secret” |
| Old or new generation key | — | Nothing: KuCoin signs different key generations differently, and the terminal picks the right variant itself |
| Too many requests | HTTP 429 | Card “KuCoin: rate limit exceeded (429), restricted until … UTC”. The terminal waits out the pause itself |
| Clock skew | 400002 |
Nothing: the terminal syncs time with KuCoin and retries the request |
| Order no longer exists | HTTP 404 with order_not_exist_or_not_allow_to_cancel |
Nothing: the terminal asks the exchange for the final order status itself |
| Not enough coins when closing a spot position | 200004, 300003, 100005 |
The terminal immediately re-reads the wallet and retries the sell up to three times, each time with a slightly smaller amount — within the fee. If that doesn’t help, it shows the exchange’s text |
| Nothing to sell on spot | — | “KuCoin …: nothing to sell — balance … = 0, position already closed” — with the pair and coin name. The order isn’t sent to the exchange |
| Exchange suspended API trading for this coin | by words in the response | “API trading is unavailable for this coin — exchange restriction” |
An IP whitelist rejection (400006) or key permission rejection (400007) comes through as exchange text in the order message: the key itself is correct. But if the exchange rejects this way already at connection time, the terminal can show the same “exchange rejected API key or secret” card — so when you see it, also check the key’s permissions and IP whitelist.
Common codes
| Code | How it looks | Cause | What to do |
|---|---|---|---|
400003 |
Card “exchange rejected API key or secret” | Key missing: pasted with a typo or deleted | Check API Key — see Exchange rejected the key |
400004 |
Card “exchange rejected API key or secret” | Wrong passphrase | Re-enter the key’s Passphrase |
400005 |
Card or “Order rejected: invalid API key or secret” | Signature mismatch: secret doesn’t match the key | Re-enter API Secret |
400001 |
Exchange text: “Any of KC-API-KEY, KC-API-SIGN, KC-API-TIMESTAMP, KC-API-PASSPHRASE is missing in your request header” | One of the three key fields is empty | Fill in all three connection fields |
400002 |
Usually nothing; on a sharp clock jump — exchange text “KC-API-TIMESTAMP Invalid” | Computer clock is out of sync with the exchange | Retry in a minute. If it persists, enable time sync in Windows |
400006 |
Exchange text: “The requested ip address is not on the api whitelist” | Your IP isn’t in the key’s whitelist | See Permissions and IP whitelist |
400007 |
Exchange text: “Access Denied” | Key doesn’t have permission for this action | Enable the required permission on the key |
411100 |
Exchange text: “User is frozen” | Account is frozen on KuCoin’s side | Contact KuCoin support |
200004 |
Exchange text in order message: “Balance insufficient” | Not enough free balance on the spot account | See Insufficient balance |
300003 |
Exchange text in order message: “Balance not enough…” | Not enough balance on the futures account | Top up the futures account or reduce the quantity |
102435 |
Exchange text in order message: “Below the minimum order size” | Quantity below the pair’s minimum | Increase the quantity |
300005 |
Exchange text in order message: “The order will exceed the maximum risk limit of …” | Position with this order would exceed the risk limit | Reduce the quantity or leverage |
300016 |
Exchange text: “The leverage cannot be greater than …” | Leverage above the contract’s allowed maximum | Choose a lower leverage |
200001 |
Exchange text in order message: “Order creation for this pair suspended” | Exchange temporarily isn’t accepting orders for this pair | Wait or place the order on the KuCoin website |
900001 |
Exchange text in order message: “symbol does not exist” | Pair doesn’t exist on this KuCoin market | Check that the coin is listed on the right market — spot or futures |
429000 |
Exchange text: “Too Many Requests…” | KuCoin’s global server limit hit | Wait a few seconds and retry |
Fixing common problems
Exchange rejected the key
Double-check all three fields
In Settings → Connections, the KuCoin connection has three fields: API Key, API Secret and Passphrase. Re-copy the key and secret without extra spaces on the ends. The Passphrase is the password you set when creating the API key, not your KuCoin login password.
Check the key on the KuCoin website
Open API management in your KuCoin profile and make sure the key hasn’t been deleted. If the secret or passphrase wasn’t saved, create a new key — you can’t view them later.
Check permissions and IP whitelist
The key must have permission to trade the market enabled in the connection by the Spot and Futures toggles. If the key has an IP whitelist, it must include your external address or the proxy address.
The rejected-key card appears once per connection. Once the connection comes up with a fixed key, the terminal can show it again if the key stops working again.
Permissions and IP whitelist
Codes 400006 and 400007 mean the key is correct, but the exchange is blocking the request. For 400006, add your computer’s external IP to the key’s whitelist; if the connection goes through a proxy (the Proxy section in the connection card), add the proxy address instead. For 400007, enable trading permission on the key for the required market. You usually don’t need to recreate the key: permissions and IP list are changed in the existing key’s settings.
Insufficient balance
On spot (200004), funds locked by open orders are not available for a new order. Cancel extra orders or reduce the quantity.
On futures (300003), funds must be on the KuCoin futures account. KuCoin keeps spot and futures accounts separate — transfer funds between them on the exchange website.
When closing a spot position with a sell, the shortfall often comes from the fee charged in the purchased coin. The terminal accounts for this: it re-reads the wallet and retries the sell with a slightly smaller quantity. After that, the wallet may hold “dust” smaller than the volume step — you can’t sell it with an order.
Futures volume
KuCoin futures orders are counted in contracts, not coins: each contract has its own size. The terminal converts the volume from coins to contracts itself and rounds to the nearest whole number of contracts, but never below one. So an order smaller than one contract goes to the exchange as one contract — the actual volume will be larger than what you entered. On small accounts, check the coin’s contract size on the KuCoin website.
Rate limit exceeded
The terminal shows the UTC time until the restriction is active and waits out the pause itself. The limit counts per address: KuCoin connections to the same market through one IP or proxy share the same pool. If the restriction repeats, reduce the number of KuCoin windows and panels or spread connections across different proxies. See Terminal messages for more.