MEXC errors
MEXC error codes in LootX for spot and futures: API key and permissions, futures verification, IP whitelist, insufficient balance, margin mode, and request limits.
MEXC has two separate APIs — one for spot and one for futures — and they report errors differently. Spot responds with code and msg fields: for example, {"code":10101,"msg":"Insufficient balance"}. Futures responds with "success":false and a numeric code, often with a normal HTTP status of 200 — you need to look at the code, not the status. The code numbers for the two APIs do not overlap: 10101 only occurs on spot, 2005 only on futures.
If the terminal does not recognize the rejection, the popup message after “Order:” will contain MEXC’s response as-is. On spot: MEXC order rejected: HTTP 400 {"code":10101,"msg":"Insufficient balance"}, on futures: MEXC futures order rejected: HTTP 200 code=2005 …. For the general approach to reading errors, see Error messages: how to read them; for key setup, see Connecting exchanges and API keys.
What the terminal explains on its own
| Situation | Codes | What you will see |
|---|---|---|
| Exchange rejected the key on connection | HTTP 401 or 403 on account check | Card “…: exchange rejected the API key or secret — check them in the connection settings”; the connection in Settings → Connections shows the tooltip “Exchange rejected the API key or secret”. More below — Exchange rejected the key |
| Invalid signature on an order | 700002 |
“Order rejected: invalid API key or secret” |
| Too many requests | HTTP 429 and 418 | Card “MEXC: request limit exceeded (429), restricted until … UTC”. The terminal waits on its own |
| Clock skew | 700003, -1021 |
Nothing: the terminal syncs time with MEXC and retries the request |
| Order no longer exists on spot | -2011, “Unknown order sent” |
Nothing: the terminal asks the exchange for the final order status |
| Insufficient coins when selling on spot | 10101, 30004, 30005, -2010 |
The terminal retries the sale up to three times, each time with a slightly smaller volume — within the fee, no more than 0.1%. If that doesn’t help, it shows the exchange’s text |
| Exchange suspended API trading for this coin | Based on words in the response | “API trading is unavailable for this coin — exchange restriction” |
Common codes
Spot
| Code | What it looks like | Cause | What to do |
|---|---|---|---|
700001 |
Exchange text in the order message: “API-key format invalid” | The key was pasted incorrectly or incompletely | Copy the API Key again, without leading or trailing spaces |
700002 |
“Order rejected: invalid API key or secret” | The secret does not match the key | Paste the API Secret again |
10072 |
Exchange text in the order message: “invalid access key” | The key does not exist: deleted or expired | Create a new key — see Exchange rejected the key |
700003 |
Usually nothing; on a sudden clock jump — exchange text “Timestamp for this request is outside of the recvWindow” | The computer clock has drifted from the exchange | Retry in a minute. If it persists, enable time synchronization in Windows |
700006 |
Exchange text in the order message: “IP non white list” | Your IP is not in the key’s whitelist | Add the IP to the whitelist — see Permissions and IP whitelist |
700007 |
Exchange text in the order message: “No permission to access the endpoint” | The key lacks permission for this action | Enable the permission on the key |
10101 |
Exchange text in the order message: “Insufficient balance” | Not enough available funds | See Insufficient balance |
30004, 30005 |
Exchange text in the order message: “Insufficient position”, “Oversold” | You are selling more coins than the wallet holds | Reduce the sell volume |
30002 |
Exchange text in the order message: “The minimum transaction volume cannot be less than: …” | The order amount is below the minimum for the pair | Increase the volume — MEXC states the minimum directly in the response |
-2011 |
Nothing | The order being cancelled no longer exists: filled or cancelled | No action needed |
Futures
| Code | What it looks like | Cause | What to do |
|---|---|---|---|
401 |
Exchange text: “Unauthorized” | The key was not accepted or lacks futures permissions | See Futures do not connect |
402 |
Exchange text: “Api_key expired” | The key has expired | Create a new key |
602 |
Exchange text in the order message: “Verify failed” | Signature mismatch: the secret does not match the key | Paste the API Secret again |
406 |
Exchange text: “Accessed IP is not in the whitelist” | Your IP is not in the key’s whitelist | Add the IP to the key’s whitelist |
2005 |
Exchange text in the order message: “Balance insufficient” | Not enough margin on the futures account | See Insufficient balance |
2006 |
Exchange text: “Leverage ratio error” | Leverage is not allowed for this coin | Choose lower leverage |
2007 |
Exchange text in the order message: “Order price error” | Price is outside the allowed range or does not match the tick size | Place the order closer to the market |
2011 |
Exchange text in the order message: “Order quantity error” | Volume does not meet the minimum or contract step | Change the volume |
2027 |
Exchange text in the order message: “There is only one cross or isolated in the same direction” | You already have a position in this coin in the other margin mode | See Isolated margin on futures |
2009 |
Exchange text: “Positions do not exist or have been closed” | The position being closed no longer exists | Check the position on the exchange |
2040, 2041 |
“Cancel rejected: … code=2040 …” | The order no longer exists or cannot be cancelled: filled or cancelled | Check the order list and position |
510 |
Exchange text: “Excessive frequency of requests” | Requests are too frequent | Wait and reduce the number of windows with MEXC |
How to fix common problems
Exchange rejected the key
Check the key on the MEXC website
Open API management in your MEXC profile and make sure the key exists and has not expired. A key not bound to an IP has a limited lifespan — if the key stopped working on its own, this could be the reason.
Copy the key and secret again
The secret is usually visible only when the key is created — if you did not save it, create a new key. In Settings → Connections, paste the values into API Key and API Secret without leading or trailing spaces.
Check permissions
The key must have permission to trade the market enabled in the connection with the Spot and Futures toggles. For futures, you need a separate permission and completed verification.
After fixing the issue, the terminal reconnects on its own at the next attempt.
Futures do not connect
If MEXC spot works but futures do not, it is almost always one of two exchange conditions: the account has not completed verification (KYC), or the key does not have futures permissions enabled. A key created only for spot gets a 401 or 403 rejection on futures, and the terminal shows it with the same card: “exchange rejected the API key or secret”.
Complete verification on MEXC and enable futures permissions on the key. You usually do not need to recreate the key: permissions are changed in the settings of the existing key. If futures still do not connect after that, open the log (Help → Logs) and find the line “Trading: exchange rejected key” — it contains MEXC’s response.
Permissions and IP whitelist
Rejections 700006, 700007, and 406 mean the key is valid, but the exchange is blocking the request: your IP is not in the key’s whitelist, or the key lacks the required permission. The terminal does not present such a rejection as “key rejected” in the order message — the exchange’s text is shown there.
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’s address to the whitelist.
Insufficient balance
On spot (10101), funds locked by open orders are unavailable for a new order. Cancel unnecessary orders or reduce the volume.
On futures (2005), an order requires margin on the futures account. MEXC keeps spot and futures accounts separate: spot funds are not visible for futures until you transfer them between accounts on the exchange website.
When selling on spot, shortfalls often occur because the fee was deducted in the purchased coin. The terminal accounts for this and automatically retries the sale with a slightly smaller volume. After that, a “dust” amount smaller than the volume step may remain in the wallet — it cannot be sold with an order.
Isolated margin on futures
The terminal places MEXC futures orders in isolated margin mode. If you already have a position in the same coin and direction in cross margin mode — for example, opened on the website — MEXC will reject the order with code 2027. Close that position or switch it to isolated mode on the exchange website.
Request limit exceeded
The terminal shows the UTC time until which the restriction applies. On a 429 response, background requests wait until that time, but the terminal still sends orders and cancellations. A 418 response is a ban: nothing is sent to MEXC until the specified time. The limit is counted per address: MEXC connections to the same market — spot or futures — through one IP or proxy share the same quota. If the restriction keeps recurring, reduce the number of windows and panels with MEXC, or spread connections across different proxies. More in Terminal messages.