Skip to content
  • Documentacion

Start Here

8
  • What’s TradeAdapter
  • How TradeAdapter works
  • Supported Platforms & Brokers
  • Requirements
  • Quick Start
  • Indicator vs Strategy
  • Strategy Example
  • Safety & Risk Disclaimer

Direct API

15
  • Overview
  • Binance Guide
  • Binance US Guide
  • Bybit Guide
  • MEXC Guide
  • Kucoin Guide
  • Kraken Guide
  • Coinbase Guide
  • OKX Guide
  • BingX Guide
  • Bitget Guide
  • Gate.io Guide
  • Alpaca Guide
  • Capital Guide
  • OANDA Guide

MetaTrader

6
  • Overview
  • MT4 Setup
  • MT5 Setup
  • TradingView Alerts
  • EA Settings
  • Symbol alignment

FAQ

7
  • Overview
  • Binance
  • Bybit
  • Bitget
  • TradingView
  • Metatrader
  • Other
View Categories
  • Home
  • Docs
  • FAQ
  • Binance

Binance

FAQ — Binance

Common errors and fixes when trading Binance with TradeAdapter and TradingView.

On this page #

  • 1. Account has insufficient balance for requested action
  • 2. Order’s position side does not match user’s setting
  • 3. Order’s notional must be no smaller than 5
  • 4. Filter failure: NOTIONAL
  • 5. Filter failure: LOT_SIZE
  • 6. Margin is insufficient
  • 7. Precision is over the maximum defined for this asset
  • 8. Invalid API-key, IP, or permissions for action

1. Account has insufficient balance for requested action #

This error appears when you try to place an order and Binance detects that your available balance is not enough. It often happens when selling or using 100% of your balance: trading fees reduce the effective amount and the order is rejected.

Why it happens #

Binance applies a fee to every order. If you use 100% of your balance, after the fee is deducted the available amount is below what you requested, so you get “insufficient balance”.

How to fix it #

  • Reduce order size slightly: In your strategy or indicator properties, set the size to less than 100% (e.g. 95–99%).
  • Pay fees with BNB: Enable the option to pay trading fees with BNB so Binance applies the discount and the fee is not taken from the asset you’re trading.
  • Fixed size in the asset: Instead of % of equity, use a fixed size in the asset (e.g. Order size = 0.1 for ETH/USDT = always 0.1 ETH). This avoids fee-related “insufficient balance” errors.

The easiest approach is usually to lower the % (95–99%) or use a fixed quantity.

2. Order’s position side does not match user’s setting #

This error (code -4061) usually appears when Hedge Mode is enabled on Binance Futures.

Solution #

  1. Go to the Futures tab and in the top-right corner of Place Order open Preferences.
  2. Open Position Mode Setting.
  3. Select One-way Mode.

TradeAdapter works with One-way mode on Binance Futures.

3. Order’s notional must be no smaller than 5 #

The message means the total order value is below the minimum allowed by Binance’s API, which is 5 USDT. You cannot place orders for less than 5 USDT.

Example: If OrderContract = 5 and Order Price = 0.1513, the value is 5 × 0.1513 = 0.7565 USDT, below the minimum.

Solution: Increase the order size so that the total value is greater than 5 USDT.

4. Filter failure: NOTIONAL #

The error appears when the order size is smaller than the minimum allowed by Binance for that symbol.

You can check the minimum (Min Notional Allowed) per symbol at:

  • Binance Futures: binance_symbols_futures
  • Binance Spot and Margin: binance_symbols_spot

5. Filter failure: LOT_SIZE #

This means your strategy is generating an order size that does not meet the MinQty, MaxQty, or step (increment) allowed by Binance for that symbol. For example: order of 0.037 when the step is 0.01 → you need to round to 0.03 or 0.04.

Min, Max and step per symbol: SPOT, MARGIN, FUTURES.

Solution options #

From TradingView: Set the Order Size in the strategy properties and recreate the alert after changing.

From Pine Script: Round the size to the step (e.g. divide by 1000 for step 0.001):

position_size = (math.ceil((strategy.equity / close) * 1000))/1000
strategy.order("Long", strategy.long, qty = position_size)
strategy.order("Short", strategy.short, qty = position_size)

Recreate the alert after modifying the strategy or script.

6. Margin is insufficient #

This happens when the order size is greater than Balance × Leverage.

Example: Order of 10 BTC at 30,125 USDT (301,250 USDT) with 100 USDT balance and 125x leverage → buying power = 12,500 USDT. 301,250 > 12,500 → “Margin is insufficient”.

Solution #

Keep position size within your buying power. In TradingView you can set the Order size in the strategy properties. In Pine Script you can use default_qty_type = strategy.percent_of_equity and default_qty_value to match your balance and leverage, or a fixed size in strategy.order(). Recreate the alert after any change.

7. Precision is over the maximum defined for this asset #

Your strategy is sending a size or price with more decimals than Binance allows for that asset (e.g. quantity 0.00200005 with 0.001 precision, or price with too many decimals).

Check precision at: SPOT, MARGIN, FUTURES.

Solution #

Quick: Use "auto_rounding": "Yes" in the alert message.

Pine Script: Round quantity and (for limit orders) price to the allowed step (e.g. ×1000 for step 0.001) before passing them to strategy.order().

Recreate the alert after changing the strategy.

8. Invalid API-key, IP, or permissions for action #

Check that you have completed the Binance setup for TradeAdapter:

  • Add the TradeAdapter IP to the whitelist: 35.75.198.16
  • Enable Spot & Margin and/or Futures depending on the market you use

← FAQ overview

Updated on February 26, 2026

What are your Feelings

  • Happy
  • Normal
  • Sad

Share This Article :

  • Facebook
  • X
  • LinkedIn
  • Pinterest
OverviewBybit
Table of Contents
  • On this page
  • 1. Account has insufficient balance for requested action
    • Why it happens
    • How to fix it
  • 2. Order's position side does not match user's setting
    • Solution
  • 3. Order's notional must be no smaller than 5
  • 4. Filter failure: NOTIONAL
  • 5. Filter failure: LOT_SIZE
    • Solution options
  • 6. Margin is insufficient
    • Solution
  • 7. Precision is over the maximum defined for this asset
    • Solution
  • 8. Invalid API-key, IP, or permissions for action
© 2026 • Built with GeneratePress