| Error names | Start with |
|---|---|
| PRICE_FILTER | Price bounds and tick size |
| LOT_SIZE | Quantity bounds and step size |
| MIN_NOTIONAL or NOTIONAL | Order value under the current symbol rule |
Copy the exact error before changing the order. More decimal places will not help if the price or quantity falls between the permitted increments.
What does a price filter control?
The official Spot filters specification defines price limits and tick size through PRICE_FILTER. The price must align with the increment for that symbol. Extra decimals are not harmless when they fall between permitted ticks.
Round according to your intended limit and the pair rules, not automatically up or down.
What do quantity and lot-size filters control?
They define minimum, maximum and step size for the base-asset quantity. A value can be large enough but still invalid because it does not align with the step.
Check whether the interface asks for base quantity or quote amount and account for rounding.
What is minimum notional value?
It is a rule on price multiplied by quantity, subject to the platform’s calculation method. A quantity that passes lot size can still produce too little order value. Market orders may use an average-price window defined by current rules.
Do not treat a minimum copied from another pair as universal.
Can balance cause a similar failure?
Yes: fees, open orders and wallet location reduce available balance. Check free balance in the spot wallet and assets locked by other orders. Selling “100%” can fail when a fee or rounding leaves the request slightly above available quantity.
Internal transfer is appropriate only when funds are in another Binance account wallet.
Why did an order that worked before fail now?
Symbol filters and market conditions can change. A saved bot setting, spreadsheet or old screenshot may no longer match the exchange rules. Retrieve the current symbol information before reusing saved limits.
API users should validate values before submission and handle a changed-filter response safely.
What is the safest correction sequence?
- Copy the exact error and symbol; the official Spot error definitions help identify which rule rejected the request.
- Check current price tick and quantity step.
- Calculate price × quantity for notional rules.
- Check available balance and open orders.
- Resubmit once with the corrected values.
Do not keep altering every input at once. A single-variable correction makes the cause traceable.
How do you isolate the failing filter?
Start with the exact symbol and error text, then test the proposed price, quantity and notional value against the current rules one field at a time. Use the trading pair’s base and quote assets correctly: quantity normally refers to the base asset, while notional is derived from price and quantity under the applicable rule.
For an API order, record the endpoint, order type and parameters without exposing keys or signatures. Compare decimal precision with tick size and step size mathematically; merely rounding to a familiar number of decimal places can still produce an invalid increment. Re-fetch current exchange information before retrying rather than relying on cached limits.