Binance errors
Binance error codes in LootX: what the terminal explains on its own, common spot and futures rejections, and how to fix them.
Binance reports an error with a negative numeric code and a short English text, for example {"code":-2010,"msg":"Account has insufficient balance for requested action."}. Separately, the exchange responds with HTTP statuses 429 and 418 when there are too many requests. This page lists the codes you’ll most often encounter when trading from LootX, and what to do about them.
Binance spot and USDT-M futures are two different APIs with their own request limits and key permissions. So a key that trades on spot can be rejected on futures, and vice versa. For the general approach to any error, see Error messages: how to read them; for key setup, see Connecting exchanges and API keys.
What the terminal explains on its own
LootX recognises some rejections by code and shows its own message or handles the situation without your involvement:
| Situation | Codes | What you’ll see |
|---|---|---|
| Exchange rejected the key on connection | -2014, -2015, -1022, any 401/403 auth rejection |
Connection card: “…: exchange rejected the API key or secret — check them in the connection settings”. In Settings → Connections, the connection has a tooltip “Exchange rejected the API key or secret”. The terminal retries about every 30 seconds |
| Bad signature in the order | -1022 |
“Order rejected: invalid API key or secret” |
| Too many requests | HTTP 429 | “⚠ … Rate limit (429), pausing ~N s — until HH:MM:SS UTC”. The terminal waits out the pause itself |
| IP address banned | HTTP 418, -1003 |
“⚠ … Too many requests to the exchange, IP address banned until 30.09.2026 19:37:54 UTC”. Until then, the terminal sends no requests from this IP on any connection |
| Clocks out of sync | -1021 |
Nothing: the terminal syncs with the exchange on connection and once a minute, and on rejection recalculates the offset and retries |
| Order no longer exists | -2011, -2013 |
Nothing: the cancellation is considered done — the order filled or was cancelled earlier |
| Not enough coins when selling on spot | -2010 |
The terminal retries the sale with the volume reduced by the fee. If that doesn’t help — it shows the exchange’s text |
| Nothing to close on spot | — | “Binance SOLUSDT: nothing to sell — SOL balance = 0, position already closed”. No order is sent to the exchange: the wallet is empty or the balance is less than the volume step |
| Exchange suspended API trading for the coin | by wording in the response | “API trading is unavailable for this coin — exchange restriction” |
Everything else the terminal doesn’t translate: in the popup message after “Order:” the Binance response appears as is — code and text. In the tables below this is marked as “exchange text in the order message”.
Common codes
| Code | What it looks like | Cause | What to do |
|---|---|---|---|
-2014 |
Card “exchange rejected the API key or secret” | Wrong key format: copied incompletely or with an extra character | Copy the key again into the API Key field |
-2015 |
Same card | Key doesn’t exist, your IP isn’t in the key’s whitelist, or the key lacks permission for this action | Check the key, IP binding and permissions — see Exchange rejected the key |
-1022 |
Card or “Order rejected: invalid API key or secret” | Secret doesn’t match the key | Paste the API Secret again; if the key was recreated — update both fields |
-1021 |
Usually nothing | Computer clock drifted from exchange time | The terminal corrects the time itself. If rejections persist — enable time sync in Windows |
| HTTP 429 | “Rate limit (429), pausing ~N s…” | Exceeded the per-minute request weight limit | Wait out the pause, close extra windows for this exchange |
HTTP 418, -1003 |
“IP address banned until …” | Requests continued after the 429 warning, and Binance temporarily blocked the IP | Wait until the stated time — see IP address banned |
-2010 |
Exchange text in the order message: “Account has insufficient balance…” | Not enough free funds: some are locked by orders or taken as fees | Check the free balance, cancel extra orders |
-2019 |
Exchange text in the order message: “Margin is insufficient” | On futures, not enough margin for the order at the current leverage | Reduce the volume, top up the futures wallet, or cancel extra orders |
-1013 |
Exchange text in the order message: “Filter failure: …” | The order violates the instrument’s rules: volume step (LOT_SIZE), minimum notional (MIN_NOTIONAL), or price step (PRICE_FILTER) | Increase the order size or fix the price. The filter name in the text tells you exactly what’s wrong |
-4164 |
Exchange text in the order message: “Order’s notional must be no smaller than …” | Futures order notional is below the contract minimum | Increase the volume. A reduce-only close order is exempt from this rule |
-2022 |
Exchange text in the order message: “ReduceOnly Order is rejected” | Reduce-only order is larger than the position, or the position is already gone | Refresh the position, reduce the close volume |
-2011 |
Nothing | The order being cancelled no longer exists | Nothing to do |
-2013 |
Nothing | Order not found on status check | Nothing to do |
-1121 |
Order book or chart for the coin won’t load | No such symbol: typo or the coin was delisted | Check the ticker and market — spot or futures |
How to fix common problems
Exchange rejected the key
The card “exchange rejected the API key or secret” appears on any connection auth rejection. On Binance, this can be more than a key mistake: code -2015 also means a wrong key, an IP not in the whitelist, or missing permissions.
Check the key is alive
Open API management in your Binance profile. If the key isn’t in the list — it was deleted: create a new one.
Copy the key and secret again
Binance shows the secret only when the key is created. If it wasn’t saved, create a new key. In Settings → Connections, paste the values into API Key and API Secret with no spaces around them.
Check IP binding
If the key has an IP whitelist enabled, it must include your computer’s external address. If you use a proxy (the Proxy section in the connection card) — add the proxy address, not your own.
Check permissions
For spot trading, the key must have spot trading enabled; for futures — futures. Enable permissions for the markets marked on the connection with the Spot and Futures toggles.
After fixing it, the terminal reconnects automatically on the next attempt.
Key works on spot but not on futures
Binance grants futures permissions separately, and you can only enable them after the futures account is opened on the exchange website. Open a USDT-M account, then enable futures for the key in API management. You don’t need to recreate the key.
IP address banned
Binance first responds with 429, and if requests continue — blocks the entire IP address (HTTP 418). The exchange itself sends the ban end time; the terminal shows it in the message.
- Until then, LootX doesn’t send requests from this IP on any Binance connection: every extra request would extend the ban.
- The time in the message is UTC. In Moscow, add three hours.
- If bans keep happening, reduce the load: fewer windows and panels with Binance on one machine, fewer connections from one IP.
Not enough coins when selling the entire spot balance
When the purchase fee is charged in the bought coin, the wallet ends up with slightly less than you bought. The terminal checks the sell volume against the actual wallet balance, and if Binance still responds -2010, retries the order with the volume reduced by the fee.
After such a sale, the wallet may hold “dust” — a balance smaller than the minimum volume step. You can’t sell it with an order: that’s an exchange restriction. If -2010 still fails after retries, the wallet really has fewer coins — check whether they’re locked by another order.
Account in hedge mode
LootX works with futures positions in one-way mode: one position per coin. If Binance futures settings have hedge mode enabled (two positions — long and short), the exchange rejects the terminal’s orders with a text about position side mismatch. Switch the position mode to one-way in the futures settings on the Binance website. The exchange only lets you change the mode when there are no open positions or orders.