BingX Errors
BingX error codes in LootX: key and signature, IP whitelist, "API trading unavailable" and code 109400, position mode, insufficient margin, and rate limits.
BingX responds with code and msg fields: a zero code means success, any other number means a rejection with an English explanation. A rejection often arrives with HTTP status 200, so you need to look at the code. Some BingX codes are generic: for example, 109400 simply means “invalid parameters,” and the reason is clarified by the text. So pay attention to both the code and the text after it.
If the terminal does not recognize the rejection, the pop-up message after “Order:” will contain the BingX response as BingX place order error 101204: … — first the word error, then the exchange’s code and text. A cancel rejection looks like “Cancellation rejected: …” with the same response inside. The general procedure for reading errors is on the Error messages: how to read page, and key setup is covered in Connecting exchanges and API keys.
What the terminal explains itself
| Situation | Codes | What you will see |
|---|---|---|
| Exchange rejected the key or signature | 100413, 100001 |
Card “…: exchange rejected the API key or secret — check them in the connection settings”; the connection in Settings → Connections gets a tooltip “Exchange rejected the API key or secret” |
| Invalid signature in the order | 100001 |
“Order rejected: invalid API key or secret”. No retry |
| Exchange does not accept API orders for this coin | 109400 or words like “temporarily disabled” in the response |
“API trading unavailable for this coin — exchange restriction”. More details — below |
| Account position mode does not match the order | 109400 about the positionSide field |
The terminal retries the order once with a different position side indication. Usually you will not notice anything |
| Stop order with trigger on the wrong side of the price | 110411, 110412 |
The terminal changes the stop type itself — stop-loss or take-profit — and retries. The stop is displayed in the order book with the type the exchange accepted |
| Too many requests | HTTP 429 | “BingX: rate limit (429), pause ~… s — until … UTC”; for a long restriction — “…limit until … UTC (~… min)”. The terminal waits out the pause itself |
| Clock drift | — | The terminal syncs time with BingX once a minute |
| Order no longer exists | 80016, “not exist” |
Nothing: the cancellation is treated as completed, and the terminal gets the final status from the exchange |
| Not enough coins when closing a spot position | words “insufficient” or “not enough” in the response | The terminal rereads the wallet and retries the sale with a slightly smaller amount — within the fee. If that does not help, it shows the exchange’s text |
| Nothing to close on spot | — | “BingX …: nothing to sell — balance … = 0, position already closed” with the pair and coin names. No order is sent to the exchange |
Common codes
| Code | What it looks like | Cause | What to do |
|---|---|---|---|
100413 |
Card “exchange rejected the API key or secret” | The exchange does not know such a key: inserted with an error or deleted | Check API Key — see Exchange rejected the key |
100001 |
Card or “Order rejected: invalid API key or secret” | The signature did not match: the secret does not fit the key | Re-enter API Secret |
100419 |
Exchange text in the order message: “IP does not match IP whitelist” | Your IP is not in the key’s whitelist | See Permissions and IP whitelist |
100004 |
Exchange text in the order message: “Permission denied…” | The key does not have permission for this action | Enable trading for the key |
101204 |
Exchange text in the order message about insufficient margin | Not enough available margin on the futures account | See Insufficient funds |
80001 |
Exchange text in the order message | Order parameters failed exchange validation: most often the quantity is not on the step or below the minimum | Change the quantity. Reducing the quantity does not fix this rejection, so the terminal does not retry it |
109400 |
“API trading unavailable for this coin — exchange restriction” | BingX does not accept API orders for this coin — or rejected the order parameters | See API trading unavailable |
80016 |
Nothing | The order being cancelled no longer exists: filled or cancelled | No action needed |
| HTTP 429 | “BingX: rate limit (429), …” | Too frequent requests | Wait out the pause — see Rate limit exceeded |
How to fix common issues
Exchange rejected the key
Check the key on the BingX website
Open API management in your BingX profile and make sure the key exists and trading is enabled for it.
Copy the key and secret again
The secret is usually visible only when the key is created — if it was not saved, create a new key. In Settings → Connections, paste the values into API Key and API Secret without leading or trailing spaces. BingX does not have a passphrase.
Wait for reconnection
The terminal will restore the connection itself on the next attempt. The BingX account event stream opens only with the correct key and secret pair, so if the connection is restored, the key and secret were accepted.
Permissions and IP whitelist
Codes 100419 and 100004 mean the key is correct, but the exchange is not letting the request through. In the order message, such a rejection comes as exchange text, not as a “key rejected” card: the key is correct, and recreating it is useless.
For 100419, 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 to the list. For 100004, enable the trading permission for the key in the key settings on the BingX website.
API trading unavailable
The terminal shows the card “API trading unavailable for this coin — exchange restriction” for any BingX rejection with code 109400. Most often this really is an exchange restriction: right after a listing or during high volatility, BingX temporarily does not accept API orders for a coin. In that case, wait or place the order on the exchange website.
But BingX uses the same code for other order parameter errors, such as a position mode mismatch. If the coin has been trading for a long time and the card repeats on every order, check the position mode — see the next section.
Futures position mode
LootX works with futures positions in one-way mode: one position per coin. On connection, the terminal checks the BingX account mode and, if hedge mode is enabled (separate long and short), switches the account to one-way mode itself.
BingX does not allow changing the mode while there are open futures positions or orders. In that case, the terminal keeps working in hedge mode and writes about it to the log. To switch to one-way mode:
Close positions and cancel orders
Close all BingX futures positions and cancel all open futures orders.
Reconnect
Turn the BingX connection off and on in Settings → Connections — the terminal will change the mode itself. You can also do it manually: switch the position mode to one-way in the BingX futures settings.
Insufficient funds
On futures (101204), an order requires available margin, taking into account leverage and already open positions. Reduce the quantity or leverage, cancel unnecessary orders, or top up the futures account — BingX spot and futures accounts are separate.
On spot, funds locked by open orders are not available for a new order. When closing a spot position by selling, the shortage often arises from the fee charged in the purchased coin; the terminal accounts for this and retries the sale with a slightly smaller amount. After that, the wallet may still hold “dust” below the quantity step — it cannot be sold with an order.
Rate limit exceeded
The terminal shows how many seconds the pause will last and until what time UTC. The limit is counted per address: all BingX connections — both spot and futures — through one IP or proxy share a common quota. If the restriction repeats, reduce the number of windows and panels with BingX or spread the connections across different proxies. More details — in Terminal messages.