Welcome to our new support center! Some articles may still be missing; they will be added shortly. For the old support documentation go to https://support.altrady.com. If you have questions, open a new ticket here. New tickets on support.altrady.com won’t be answered; existing tickets will be finalised there.

Altrady Support Altrady Support

Common exchange error messages

Exchanges reject an order and show an error instead of placing it. This is normal: it’s the exchange’s own safety rules doing their job, not a problem with your Altrady account. The exact wording comes from the exchange and varies, but the causes fall into a handful of groups, set out below.

Altrady usually shows these as EXCHANGE code: … message: …, where the prefix is the exchange: BINA/BIFU (Binance spot/futures), BYBI/BYBIF (Bybit), OKEX/OKEXF (OKX), GDAX (Coinbase), BVVO (Bitvavo), GATE (Gate.io), KRKN (Kraken), BNGX/BNGXF (BingX), HYPERLIQUID/HYPERLIQUIDF (Hyperliquid), MEXC, and TBITF (Toobit).

The order is below the minimum size

The exchange rejects an order below its minimum for that pair. This most often happens when several take-profits split a position so each slice is too small, or when a bot sized an order off a balance that was less than when the bot was created.

You might see:

  • Bitvavo 217: You set amountQuote to less than the minimum value possible for this market
  • Gate Your order size … is too small. The minimum is 10 USDT
  • Binance Filter failure: MIN_NOTIONAL or LOT_SIZE, or Binance futures -4164 Order's notional must be no smaller than …

Fix: use fewer take-profits, increase the size, or leave a balance buffer so each order clears the minimum. See what does “Order size is too small” mean?.

The price is out of range, or a stop is on the wrong side

Exchanges only accept prices within a band around the current market, and a stop has to sit on the correct side of it.

You might see:

  • Binance Filter failure: PRICE_FILTER (wrong tick size or out of range) or PERCENT_PRICE (too far from the average price)
  • OKX 51137 The highest price limit … is …
  • MEXC 30087 Order price exceeds allowed range
  • Coinbase PREVIEW_STOP_PRICE_BELOW_LAST_TRADE_PRICE
  • “Stop price would trigger immediately”

Fix: move the price closer to the market, or leave a wider gap between your trigger and stop, especially in fast-moving markets. See price and stop-loss order errors.

Too many orders, or an order too large

Exchanges cap how many orders you can have open, and how large a single order can be.

You might see:

  • Binance MAX_NUM_ORDERS / MAX_ALGO_ORDERS (too many orders, or too many stop/take-profit orders) or MAX_POSITION (a holding limit, mainly leveraged tokens)
  • BingX 100400 … entrust volume too high … maxVolume …
  • Binance futures -4005 Quantity greater than max quantity

Fix: cancel some open orders, reduce the order size, or trade a higher-liquidity market. A market order carries a size cap that a limit order doesn’t.

“Reduce only” was rejected (usually harmless)

A reduce-only order (used for take-profits and stop-losses) is rejected when there’s nothing left to reduce, usually because the position already closed, externally or via a duplicate close, or the remaining amount rounded to zero.

You might see:

  • OKX 51205 Reduce Only is not available
  • Binance futures -2022 ReduceOnly Order is rejected
  • Hyperliquid Reduce only order would increase position

Fix: usually nothing. Check My Orders, the close almost always went through. See why did an order fail after my position opened?.

The account is in the wrong mode (futures)

Some orders need your exchange account set a certain way. The most common is trying to trade both sides of a market while the account is in one-way mode.

You might see:

  • Binance futures -4061 Order's position side does not match user's setting
  • Bybit “Hedge mode is not supported”

Fix: set the account to the mode you need, on the exchange (hedge to hold both sides, one-way otherwise), or use Reduce Only if you’re only reducing a position. See hedge mode vs one-way mode.

The account is in the wrong mode (OKX spot)

OKX spot orders need your account in a spot-capable account mode. In Multi-currency margin mode or Portfolio margin mode, OKX treats every spot order as a margin order and rejects the ones Altrady sends. This affects all of your spot orders, not just one pair, while your futures orders keep working, so it can look as though only spot is broken.

You might see:

  • OKX 51000 Parameter tdMode error (on a spot order)

Fix: on OKX, switch your account to Spot mode or Spot and futures mode (Settings > Account mode). This is a single, account-wide setting, and OKX won’t let you change it until you close open positions and cancel pending orders. Altrady does not support spot trading in Multi-currency margin or Portfolio margin mode, and it does not support margin (borrowing) on spot at all. See set your OKX account mode.

The market or order type isn’t available

Some pairs and order types can be traded in the exchange’s own app but not by a connected app like Altrady, and some markets only accept certain order types.

You might see:

  • MEXC 10004 symbol not support api (the pair can’t be traded over the API at all)
  • “Order Type MARKET is not supported for this exchange”, or a market order refused because the market is in limit-only mode (some exchanges, such as Coinbase, restrict new or thin markets to limit orders until liquidity builds up): place a limit order instead
  • a market that switches to API-disabled after you’ve opened a position, without telling Altrady

Fix: trade a pair, and order type, the exchange allows over the API; if a market order is refused, try a limit order.

Insufficient balance or margin

The free balance or margin fell short of what the order needs.

You might see:

  • Binance Insufficient Balance (not enough quote currency for the entry) or Insufficient Funds (not enough to place the exit)
  • Binance futures “Margin is insufficient”
  • Hyperliquid “Insufficient margin to place order”
  • closing a spot position that’s fully invested can fail if there’s no quote currency left to pay the fee

If cross-margin mode is used for other positions, the available margin changes as those positions move from profit to loss and back.

Fix: add funds, or leave a small buffer for fees (some exchanges take the fee from quote currency, others from the coin). See what does “Insufficient balance” mean?.

Account restrictions

The exchange won’t let this account trade this market.

You might see:

  • “This action disabled on this account” (a leveraged token you haven’t unlocked, complete the exchange’s short quiz first)
  • “This symbol is restricted for this account” (often a regional restriction, for example privacy coins like XMR)
  • Binance 823013 … accept the Terms of Use of API Key … (accept the API terms on Binance’s API management page, using a main account, not a sub-account)

Authentication, API key, or IP whitelist

The exchange is rejecting the key itself rather than a specific order.

You might see:

  • Binance “Invalid API-key, IP, or permissions for action”
  • Crypto.com “Authentication error” (it now requires an IP whitelist)
  • on a bot position, “Signature invalid” (your 5-word password changed since the bot was created, so it can no longer authenticate)
  • Kraken “Invalid nonce” (the nonce setting on the API key is invalid)

Fix: check the key was connected correctly and has the right permissions and IP whitelist. For a bot that stopped authenticating after a password change, edit the bot and save; if that doesn’t clear it, duplicate the bot. See how to connect your Binance account, IP whitelisting explained, or replace an API key.

Rate limit reached

The exchange limits how many requests you can send in a short window, and briefly blocks the rest.

You might see:

  • Kraken EAPI:Rate limit exceeded
  • Bybit and Coinbase rate-limit rejections (Coinbase counts per account, and sub-accounts share the limit)

Fix: don’t share one API key across two Altrady accounts, and don’t resync too often. Some exchanges let you add an extra key to spread the load; where that’s the case, our API documentation notes it and you’ll see space for extra keys on your trading account.

Server error or timeout

A temporary problem on the exchange’s side, not your order.

You might see:

  • Coinbase 500 Internal Server Error
  • MEXC 504 internal error or a request timeout
  • Bybit 503 Service Unavailable
  • a Toobit timeout when a stop triggers

Fix: wait and try again. The action often went through despite the error, so check My Orders before retrying, and delete any position left stuck by a timeout.

Clock out of sync

Some exchanges reject requests if your computer’s clock drifts too far from theirs.

You might see:

  • Bybit 10002 … check your server timestamp or recv_window

Fix: correct your computer’s date and time, and make sure your time zone and daylight-savings options are right; ideally set it to sync automatically.

Security note

Altrady only ever asks for read and trade permissions on your API key. Altrady can never withdraw your funds: keep that permission switched off on the key you create for Altrady.

Still stuck?

If a message here doesn’t match, or the fix doesn’t clear it, send us the exact error text (including the code) and the market, so the team can see exactly what the exchange returned.

Need more help? You can reach our support team anytime through the chat bubble in the bottom-right corner of our Help Center at help.altrady.com.

Was this article helpful?