Troubleshooting
Common errors and how to fix them
"Binance requires an API-key credential with both an API key and an API secret"
Fix: Configure
credentialId is missing, unset, or the vault entry is missing its API key or secret.
Fix: Configure
credentialId on the node to a vault API-key credential
containing both fields — see Authentication.
BINANCE_INVALID_API_KEY
The API key is malformed, revoked, or lacks permission for the endpoint being called (e.g. a read-only key used for
Fix: Confirm the key is active in your Binance account and has trading permission enabled if you're calling
The API key is malformed, revoked, or lacks permission for the endpoint being called (e.g. a read-only key used for
order.placeMarketOrder).
Fix: Confirm the key is active in your Binance account and has trading permission enabled if you're calling
order.*.
BINANCE_TIMESTAMP_OUT_OF_RECV_WINDOW
The host machine's clock has drifted too far from Binance's server time for the configured
Fix: Sync the host clock (NTP), or increase
The host machine's clock has drifted too far from Binance's server time for the configured
RecvWindowMs.
Fix: Sync the host clock (NTP), or increase
Binance:RecvWindowMs — see Configuration.
BINANCE_INVALID_SYMBOL
The trading pair doesn't exist, isn't tradable, or was mistyped.
Fix:
The trading pair doesn't exist, isn't tradable, or was mistyped.
Fix:
symbol is auto-uppercased, but that doesn't fix a genuinely wrong
pair — confirm the exact ticker (e.g. BTCUSDT, not BTC-USDT) against Binance's
symbol list.
BINANCE_RATE_LIMIT_EXCEEDED (HTTP 429)
You've exceeded Binance's request-weight or order-count budget.
Fix: The node retries 429s automatically up to 3 times honoring
You've exceeded Binance's request-weight or order-count budget.
Fix: The node retries 429s automatically up to 3 times honoring
Retry-After. If it persists, lower ProactiveThrottleThreshold or reduce call
frequency — see Rate Limiting.
BINANCE_IP_BANNED (HTTP 418)
Your IP has been temporarily banned after repeated rate-limit violations.
Fix: Stop calling entirely for the
Your IP has been temporarily banned after repeated rate-limit violations.
Fix: Stop calling entirely for the
Retry-After duration in the error
message. Do not retry immediately — the node deliberately does not auto-retry 418s, and neither should
a workflow wrap one in its own retry loop.
BINANCE_ORDER_NOT_FOUND
No order matches the given
Fix: Double-check
No order matches the given
orderId/origClientOrderId.
Fix: Double-check
symbol — an order id is only valid together with the
symbol it was placed on, and a mismatch looks identical to a nonexistent order.
Validation error: "specify exactly one of quantity or quoteOrderQty"
Fix: Set exactly one —
placeMarketOrder was called with both fields set (or neither).
Fix: Set exactly one —
quantity for a base-asset amount, quoteOrderQty for a quote-asset spend amount.
Attempting a Margin, Futures, or streaming operation
This node covers the Spot v3 REST API only.
Fix: See Roadmap — Margin/Futures and any WebSocket-based design are explicitly out of scope for this version.
This node covers the Spot v3 REST API only.
Fix: See Roadmap — Margin/Futures and any WebSocket-based design are explicitly out of scope for this version.