binance_get_order_list
Check a specific OCO, OTO, or OTOCO order list by its ID or client order ID to verify whether it exists after a failed placement or inspect its current status.
Instructions
Look up one order list — OCO, OTO or OTOCO — by id.
Calls GET /api/v3/orderList (SIGNED, IP weight 4). No symbol is needed: pass exactly
one id, order_list_id (Binance's numeric orderListId) or orig_client_order_id (the
listClientOrderId used when placing). Both at once is rejected locally — Binance
resolves the numeric id first and then rejects a mismatch, so the ambiguous call buys
nothing.
When to Use:
After a 5xx or a timeout on a placement — this is how you find out whether the list exists before considering a retry.
To check whether a bracket is still working, or which leg ended it.
When NOT to Use:
To see every working list —
binance_get_open_order_lists(weight 6).For history across a period —
binance_get_all_order_lists.For an individual leg's fills —
binance_get_order/binance_get_my_tradeswith the leg's orderId.
Returns:
orderListId, contingencyType, listStatusType, listOrderStatus, listClientOrderId,
symbol, transactionTime and the ### Legs table. This endpoint returns orders[]
only (ids, no per-leg status), and the answer says so rather than implying more.
response_format="json" returns the raw payload.
Examples: params = {"order_list_id": 27} params = {"orig_client_order_id": "btc-bracket-001"}
Error Handling: -2011/-2013 mean no such order list for this account. -1102 means neither id reached Binance. -2015 means the key lacks permission or this IP is not allowlisted.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |