Actions15
- Query Order (USER_DATA)
- Current Open Orders (USER_DATA)
- Query OCO (USER_DATA)
- Query all OCO (USER_DATA)
- Query Open OCO (USER_DATA)
- Account Information (USER_DATA)
- Account Trade List (USER_DATA)
- Query Current Order Count Usage (TRADE)
- Cancel an Existing Order and Send a New Order (TRADE)
- Cancel Order (TRADE)
- Cancel OCO (TRADE)
- All Orders (USER_DATA)
- New Order (TRADE)
- New OCO (TRADE)
- Cancel all Open Orders on a Symbol (TRADE)
Overview
This node integrates with the Binance API to perform various operations related to orders and account information, specifically supporting the 'Query OCO (USER_DATA)' operation among others. It is useful for users who want to programmatically query and manage their Binance orders, including OCO (One Cancels the Other) orders, retrieve account info, and trade lists. For example, it can be used to query details of a specific OCO order by providing either an order list ID or an original client order ID along with a timestamp.
Use Case Examples
- Querying an OCO order by providing a timestamp and either an orderListId or origClientOrderId to get the order details.
- Retrieving all OCO orders within a specified time range by providing startTime and endTime optional parameters.
- Fetching current open OCO orders to monitor active trades.
Properties
| Name | Meaning |
|---|---|
| Timestamp | The timestamp at which the request is made, required for all operations to ensure request validity. |
| Add Optional Operations | Additional optional parameters for the operation, such as orderListId, origClientOrderId, and recvWindow, which refine the query or request. |
Output
JSON
orderListId- The unique identifier of the OCO order list returned from the query.orders- Details of the individual orders within the OCO order list.status- The status of the OCO order list, such as executed, cancelled, or expired.symbol- The trading pair symbol associated with the OCO order.timestamp- The timestamp of the response or the queried order.
Dependencies
- Binance API with API key and secret for authentication
Troubleshooting
- Ensure that either 'orderListId' or 'origClientOrderId' is provided when querying OCO orders, as omitting both will cause the request to fail.
- Verify that the 'timestamp' parameter is correctly set and synchronized with the server time to avoid signature or request expiration errors.
- Check that the 'recvWindow' value does not exceed 60000 milliseconds to prevent request rejection by the Binance API.
- Handle API rate limits and errors gracefully, as Binance may reject requests if limits are exceeded or parameters are invalid.
Links
- Binance API - Query OCO (USER_DATA) - Official Binance API documentation for querying OCO orders.