Binance
Trade and query the Binance Spot market — accounts, orders, and market data — over HMAC-signed REST calls
binance) exposes Binance's Spot v3 REST API as workflow steps — 11 operations across 3 resources (account, order, marketData). Account and order calls are HMAC-SHA256 signed with your API key/secret; market data calls are public and need no credential.
Quick Start
- Add a Binance node to your workflow
- Try it with no credential first: set
resourcetomarketDataandoperationtogetTickerPrice, leavesymbolblank to fetch every symbol - For account/order calls, add a
credentialIdpointing at a vault API-key credential holding your Binance API key and secret (see Authentication) - Set
resourcetoaccountandoperationtogetAccountInfo - Run the workflow — the node returns your asset balances
resource,
operation, credentialId — plus a small set of operation-specific fields.
Learn the shared shape once on Input & Output and every
operation below follows it.
Pages in This Guide
Configuration
appsettings.json, rate-limit defaults, and dependency registration.
Authentication
API key/secret vault credential and HMAC-SHA256 request signing.
Account Operations
getAccountInfo and getOrderRateLimit — balances and your rate-limit budget.
Placing Orders
placeMarketOrder and placeLimitOrder — submit new spot orders.
Managing Orders
getOrder, cancelOrder, getOpenOrders, getOrderHistory.
Market Data Operations
getTickerPrice, getKlines, getOrderBookDepth — no credential required.
Rate Limiting
Request-weight budgets, proactive throttling, and IP bans.
Error Codes
The full BINANCE_* error taxonomy and what triggers each one.
Input & Output
The shared config-key pattern and how errors surface.
Examples
Worked workflow patterns using this node.
Troubleshooting
Common errors and how to fix them.
Roadmap
What's explicitly out of scope for v1, and known gaps.
Core Concepts
Spot REST API, v1 Scope
Every operation on this node calls Binance's Spot v3 REST API
(api.binance.com). Margin, Futures, and any WebSocket streaming design are explicitly out
of scope for this version — see Roadmap.
Resources
- account — asset balances and your current order rate-limit usage
- order — place, look up, cancel, and list spot orders
- marketData — public price, candlestick, and order-book reads
Signed vs. Public Endpoints
account and order operations are HMAC-SHA256 signed and require a
credentialId. marketData operations are public — no credential is required,
though supplying one is honored and raises the per-IP rate-limit bracket. See
Authentication.
Operation Summary
| Resource | Operation | Endpoint | Signed | Guide Page |
|---|---|---|---|---|
account | getAccountInfo | GET /api/v3/account | Yes | Account Operations |
account | getOrderRateLimit | GET /api/v3/rateLimit/order | Yes | Account Operations |
order | placeMarketOrder | POST /api/v3/order | Yes | Placing Orders |
order | placeLimitOrder | POST /api/v3/order | Yes | Placing Orders |
order | getOrder | GET /api/v3/order | Yes | Managing Orders |
order | cancelOrder | DELETE /api/v3/order | Yes | Managing Orders |
order | getOpenOrders | GET /api/v3/openOrders | Yes | Managing Orders |
order | getOrderHistory | GET /api/v3/allOrders | Yes | Managing Orders |
marketData | getTickerPrice | GET /api/v3/ticker/price | No | Market Data Operations |
marketData | getKlines | GET /api/v3/klines | No | Market Data Operations |
marketData | getOrderBookDepth | GET /api/v3/depth | No | Market Data Operations |