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 account-related operations such as querying orders, managing open orders, retrieving account information, and handling trade lists. It is useful for users who want to automate and manage their Binance trading activities programmatically within n8n workflows. For example, it can be used to fetch current open orders, place new orders, cancel existing orders, or retrieve detailed account information including trade history.
Use Case Examples
- Fetch current open orders for a specific trading symbol to monitor active trades.
- Retrieve account information to check balances and account status.
- Place a new order or cancel an existing order programmatically based on trading signals.
- Query trade history for analysis or record-keeping.
Properties
| Name | Meaning |
|---|---|
| Timestamp | The timestamp parameter used for API requests to ensure request validity and synchronization with Binance server time. |
| Add Optional Operations | Optional parameters for the API request, such as 'Recv Window' which defines the validity window for the request in milliseconds (cannot exceed 60000). |
Output
JSON
*- The JSON output contains the response data from the Binance API for the requested operation, which varies depending on the operation performed (e.g., order details, account info, trade lists).
Dependencies
- Requires Binance API credentials including an API key and secret for authentication.
Troubleshooting
- Common issues include invalid or expired API keys, incorrect timestamps causing request rejection, and exceeding rate limits imposed by Binance API.
- Error messages from the Binance API are propagated and may indicate issues such as invalid parameters, unauthorized access, or network errors.
- Ensure the timestamp is synchronized with Binance server time and the 'Recv Window' is set appropriately to avoid request expiration errors.
Links
- Binance Spot API Documentation - Official documentation for Binance Spot API endpoints used by this node.