Direct conclusion: price should be rounded down to a multiple of tickSize, quantity should be as well. Do not use conventional rounding. Incorrect rounding will cause the order to be rejected by the system.
The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!
1. First, Clarify Which Type of "Precision Exceeded" It Is
Binance order rejection usually happens because the decimal places of the price or quantity exceed the allowed range for that trading pair, commonly called "precision exceeded." This limit is controlled by two filters: PRICE_FILTER and LOT_SIZE.
Before placing an order, first check which rule your order violates:
Price precision exceeded: The price you set has more decimal places than the tickSize allowed for that trading pair. For example, if BTCUSDT's tickSize is 0.01, entering 110384.123 is invalid because 0.123 is not an integer multiple of 0.01.
Quantity precision exceeded: The quantity you set has more decimal places than the stepSize allowed for that trading pair.
2. Correct Rounding Method: Round Down to the Step Multiple
Many users mistakenly think "rounding half up" is acceptable, but the exchange requires order parameters to be integer multiples of tickSize or stepSize. The correct approach is to round down (truncate extra decimals), which ensures the order parameters are valid.
2.1 Price Rounding Rules
What to do: Adjust the price to an integer multiple of tickSize.
How to do it: Assuming BTCUSDT's tickSize is 0.01 and you want to place an order at 60000.123, the valid price should be 60000.12 (retain to the cent).
When is it considered done: Make sure the number of decimal places in your submitted price does not exceed the precision defined for that trading pair.
2.2 Quantity Rounding Rules
What to do: Adjust the quantity to an integer multiple of stepSize.
How to do it: Assuming a token's stepSize is 0.001 and you want to buy 100.0005, the valid quantity should be 100.000 (retain three decimal places).
When is it considered done: Similarly, ensure the number of decimal places in your submitted quantity complies with the rules.
3. Practical Steps: How to Get the Correct Precision Parameters
Stop guessing or testing blindly. Binance provides official channels to query the exact rules for each trading pair.
Step 1: Obtain exchangeInfo via API
What to do: In your code or Postman, call GET /api/v3/exchangeInfo and specify the trading pair.
How to do it: Request GET /api/v3/exchangeInfo?symbol=BTCUSDT; the returned JSON data will contain detailed filters for that trading pair.
When is it considered done: You have successfully obtained a response that includes PRICE_FILTER and LOT_SIZE.
Step 2: Parse Key Parameters
What to do: Extract tickSize and stepSize from the returned data.
How to do it:
Find PRICE_FILTER in the filters array; tickSize is the minimum price increment.
Find LOT_SIZE; stepSize is the minimum quantity increment.
When is it considered done: You have clarified the precision baseline for the current trading pair.
Step 3: Dynamically Adjust Order Parameters
What to do: Before placing an order, use your program logic to "clip" the price and quantity to valid values.
How to do it:
Calculate the decimal places of price and quantity, then truncate directly to the precision allowed by tickSize and stepSize.
If the price/quantity is lower than minPrice/minQty, the order will also be rejected, so you need to check that as well.
When is it considered done: You have successfully submitted an order that will not be rejected due to precision exceeded.
The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!
Common Failure Reasons
Using the price displayed on the website, but the API reports that the precision is too high. This commonly happens with orders that are extremely price-sensitive. For example, after the adjustment of ORDI/USDT in May 2025, the price precision was narrowed from 0.01 to 0.001. The website front-end was adapted, but if your API script was not updated synchronously, orders submitted with the old precision will be rejected.
Risk reminder: Precision rules can be adjusted. If you are using automated trading, do not hardcode the number of decimal places in your code. Obtaining the latest rules via API every time you start or periodically is a safer practice.
After completing the above, how to confirm that you rounded correctly?
If after submitting an order you receive error code -1111 with the message "Parameter '%s' has too much precision", it means your price or quantity is still not rounded properly. Adjust and resubmit until the order successfully enters the matching queue.
