Binance error codes#
HookTrader classifies Binance errors into two buckets:
- User errors — bad inputs, bad credentials, insufficient funds. Logged at WARNING. You're expected to fix something on your end. These appear in Notifications.
- System errors — unexpected. HookTrader's on-call team is alerted automatically.
Only user-error codes are documented here — system errors are HookTrader's problem to investigate, not yours.
The user-error allowlist#
These are surfaced cleanly in the dashboard as notifications:
| Error | What to do |
|---|---|
| Invalid API key, IP, or permissions | Re-check API key permissions (Reading + Futures), IP whitelist, and that the key isn't deleted on Binance. Use Verify permissions on the exchange detail page. |
| API key format invalid | Re-paste the key — usually a trimmed or wrapped paste. |
| Invalid signature | Wrong API secret saved against this key. Re-add the key with the correct secret. |
| Margin is insufficient | Fund the sub-account, reduce position size, or use lower leverage. |
| Order size below minimum | The position size in USDT is below Binance's minimum for this symbol. Increase sizing. |
| Quantity less than minimum | Your fixed quantity (or computed risk qty) is below the symbol's minimum lot. Increase. |
| Quantity greater than maximum | Position size exceeds the symbol's max lot. Decrease. |
| Order would immediately trigger | The SL or TP price is already past the current mark price. HookTrader has dedicated handling for this on SL moves — see SL safety guard. |
| Position exceeds maximum at current leverage | Position size + existing exposure exceeds Binance's per-symbol limit. Reduce leverage or close other positions on the symbol. |
Temporary exchange errors#
These are transient and resolve on their own:
| Error | What's happening |
|---|---|
| Rate limit / temporary IP cooldown | Binance has temporarily limited requests. The exchange detail page shows a red banner with a retry countdown. Your credentials are fine. Trading resumes automatically. |
| Position already closed | The exchange closed the position (via its own take-profit or stop-loss) before HookTrader's action arrived. HookTrader handles this gracefully. |
If you see anything else in a notification or an unexpected error popup, it's probably worth a bug report.
How to read a notification#
A typical trade-error notification shows the symbol, error description, and strategy name. Click through for the full webhook log entry with additional context.
See also#
- Connecting Binance → Permissions
- Rejected trades — HookTrader-side rejection reasons.