When an Order Does Not Behave as Expected
After a timeout or dropped connection, look up the original order before submitting another. Use its client order ID, account ID, and latest revision to reconcile exposure.
Find the Problem
Section titled “Find the Problem”| Symptom or Code | What to Check | Next Action |
|---|---|---|
| No response after submission | Existing order under the same client order ID | Read its state and fills before retrying |
INSUFFICIENT_MARGIN |
Available margin for the exchange and settlement asset | Reduce size or arrange eligible collateral |
INVALID_ORDER |
Minimum quantity, quantity step, price tick, required fields | Correct the rejected field using the market specification |
POST_ONLY_WOULD_TAKE |
Current best bid and ask | Choose a passive quote or change the order policy |
NO_ELIGIBLE_VENUE |
Allowed exchanges, settlement asset, order capabilities, collateral | Correct the incompatible constraint |
REVISION_CONFLICT |
Latest order revision and intervening fills | Recalculate the amendment from the current state |
RATE_LIMITED |
Returned reset information and request budget | Wait for reset and reduce request frequency |
VENUE_UNAVAILABLE |
Affected exchange and existing child orders | Pause dependent orders and reconcile fills |
Errors & Recovery includes authentication errors, HTTP status codes, and retry rules.
Check Size and Price Precision
Section titled “Check Size and Price Precision”The Binance BTC/USDT contract example uses a 0.001 BTC quantity step and a 0.10 USDT price tick. A quantity of 0.1005 BTC or a limit of 77,000.05 USDT does not match those increments. Read the current market record before correcting the request.
Recover a Stream
Section titled “Recover a Stream”After reconnecting, authenticate, resubscribe, and reconcile account state with REST. Deduplicate fills by fill_id; apply newer order revisions only. Rebuild an order book from a snapshot when its sequence has a gap.
See WebSocket Recovery and Order-Book Recovery.
Send a Useful Report
Section titled “Send a Useful Report”Contact Us with the request ID, order or client order ID, exchange, instrument, UTC time, error code, and redacted request details. Include any fills received and whether exposure remains open. Remove API keys, signatures, tokens, and personal documents from logs.