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 interacts with the Binance API to perform various operations related to cryptocurrency orders and account information. It supports operations such as querying all orders, querying a specific order, managing open orders, creating new orders, canceling orders, and retrieving account trade lists. This node is useful for automating trading workflows, monitoring order statuses, and managing Binance account data programmatically.
Use Case Examples
- Retrieve all orders for a specific trading symbol within a given time range.
- Query details of a specific order by its ID and symbol.
- Cancel all open orders for a trading symbol.
- Create a new order with specified parameters such as symbol, side, and type.
Properties
| Name | Meaning |
|---|---|
| Symbol | The trading pair symbol (e.g., BTCUSDT) for which the operation is performed. |
| Timestamp | The timestamp parameter used for API requests to specify the time context of the operation. |
| Add Optional Operations | Additional optional parameters to refine the API request, such as order ID, start time, end time, limit, and receive window. |
Output
JSON
orderId- The unique identifier of the order.symbol- The trading pair symbol related to the order.status- The current status of the order.price- The price at which the order was placed.quantity- The quantity involved in the order.timestamp- The timestamp when the order was created or updated.
Dependencies
- Binance API
Troubleshooting
- Ensure the API key and secret are correctly configured and have the necessary permissions for the requested operations.
- Check that the timestamp parameter is accurate and synchronized with Binance server time to avoid signature errors.
- Verify that optional parameters like startTime and endTime are valid date-time values and logically consistent (startTime before endTime).
- If receiving errors related to rate limits, consider adjusting the request frequency or using the recvWindow parameter appropriately.
Links
- Binance API - All Orders (USER_DATA) - Official Binance API documentation for the All Orders endpoint, detailing parameters and response structure.