binance amount of BTC/USDT must be greater than minimum amount precision of 0.00001
ccxt raises this InvalidOrder before it even talks to the exchange. It rounds your amount DOWN to the market's amount precision (amount_to_precision), the result became zero, so the amount you passed is smaller than one step of that market.
What the official docs say
ccxt source (python/ccxt/base/exchange.py), amount_to_precision(): the amount is truncated to market precision and if the result is "0" it raises InvalidOrder "... amount of <symbol> must be greater than minimum amount precision of <precision>". price_to_precision() raises the same for prices.
Three common causes
- The amount is smaller than one step of the market (for BTC/USDT on Binance one step is 0.00001 BTC).
- You passed a USD amount where ccxt wants base coin units.
- The market's minimum amount (limits.amount.min) is larger than the precision, so even a rounded amount can be rejected by the exchange afterwards.
How to fix it
- Call exchange.load_markets() and read market['precision']['amount'] and market['limits']['amount']['min'].
- Convert your size to base-coin units.
- Check amount >= max(precision step, limits min) before calling create_order.
- Use exchange.amount_to_precision(symbol, amount) to get the exact string to send.
Python (standard library only) example (runs as shown with sample numbers):
import ccxt
ex = ccxt.binance()
# offline demo: hand-made market (normally ex.load_markets() fills this)
ex.set_markets({"BTC/USDT": {"id": "BTCUSDT", "symbol": "BTC/USDT", "base": "BTC", "quote": "USDT", "spot": True,
"precision": {"amount": 0.00001, "price": 0.01}, "limits": {}}})
ex.precisionMode = ccxt.TICK_SIZE
try:
print(ex.amount_to_precision("BTC/USDT", 0.000004))
except ccxt.InvalidOrder as e:
print("InvalidOrder")
print(ex.amount_to_precision("BTC/USDT", 0.123456789))
Current limits for popular symbols
| Symbol | Price step (tick) | Quantity step | Minimum quantity | Source and read date |
|---|---|---|---|---|
| Binance BTCUSDT | 0.01 | 0.00001 | 0.00001 | data-api.binance.vision, read 2026-11-11 |
| OKX BTC-USDT | 0.1 | 0.00000001 | 0.00001 | www.okx.com, read 2026-11-11 |
| Kraken XBTUSD | 0.1 | 0.00000001 | 0.00006 | api.kraken.com, read 2026-11-11 |
| Coinbase BTC-USD | 0.01 | 0.00000001 | - | api.exchange.coinbase.com, read 2026-11-11 |
| KuCoin BTC-USDT | 0.1 | 0.00000001 | 0.00001 | api.kucoin.com, read 2026-11-11 |
| Gate BTC_USDT | 0.1 | 0.000001 | 0.000001 | api.gateio.ws, read 2026-11-11 |
Check your numbers
Pick a symbol, type your quantity and see the valid rounded quantity.
Check this automatically before every order: AIKIT (free 1,000 calls)
Disclosure: AIKIT is our own product. It returns sourced exchange and broker rules (with the official source and read date) and checks bot code against them. Facts and checks only, not advice.
Questions people ask
Why does ccxt say amount must be greater than minimum amount precision?
After truncating to the market's amount precision your amount became zero, so it is smaller than one step.
Is that the exchange's minimum order size?
Not exactly. It is the precision step. The exchange minimum is market['limits']['amount']['min'] and can be larger.
Which function rounds the amount?
exchange.amount_to_precision(symbol, amount). It truncates (rounds down).
Sources
- https://github.com/ccxt/ccxt/blob/master/python/ccxt/base/exchange.py (read 2026-11-16)
Symbol limits in the table: AIKIT facts read 2026-11-11 from the venue's own public API (links in the table). Exchange rules change; read the live values from the venue before you trade.
Related fixes
- Filter failure: LOT_SIZE (Binance spot)
- Filter failure: NOTIONAL (Binance spot)
All error fixes. General information for education only. It is not financial advice, and trading can lose money.