TradingView to Binance: automate your alerts on Binance futures and spot

AlgoVesta receives your TradingView alert through a webhook, checks that it came from TradingView, and places the order on your own Binance account using a trade-only API key. Futures orders carry your stop-loss and take-profit as reduce-only orders; spot orders get a linked OCO pair. You keep custody of your funds.

How it works

What happens on Binance when an alert fires

Binance is the exchange where this flow was first verified with real money, on both USDⓈ-M perpetual futures and spot. On futures, AlgoVesta sets your leverage, opens the position at market and then places the stop-loss and take-profit as separate reduce-only trigger orders. After placing them it reads them back from Binance; if a stop-loss cannot be confirmed, the position is closed instead of being left unprotected.

Binance accounts can run in one-way or hedge mode. AlgoVesta reads the position side from your account before it sends a protective order, so a stop that is moved to breakeven or trailed later is sent with the side Binance expects in hedge mode and with reduce-only in one-way mode.

On spot there is no reduce-only flag, so protection is an OCO order: a stop-limit leg and a take-profit limit leg linked together, so when one fills the other is cancelled. Binance enforces a minimum notional of about $5 per order. AlgoVesta checks the stop-loss leg against that minimum before it buys; if the leg would be too small, the buy is not sent at all, rather than buying and immediately selling at a fee.

Sizing on Binance

The amount in your alert is margin, not position value: $50 of margin at 10x leverage opens about $500 of exposure. Binance trades each symbol in fixed quantity steps, so AlgoVesta picks the step closest to what you asked for. If the nearest step is more than 20% away from your amount, the order is not opened and the bot card tells you which amounts would work.

The alert message

Paste this into the alert's message box. The two plot values come from your indicator; leverage is ignored on spot.

{
  "symbol": "{{ticker}}",
  "action": "buy",
  "price": "{{close}}",
  "stop_loss": "{{plot_0}}",
  "take_profit": "{{plot_1}}",
  "leverage": 10
}

For a Pine strategy, use the strategy template so exits and reversals work. Do not send only {{strategy.order.action}}: on an exit it reads "sell" and would open a short instead of closing. The market_position fields tell AlgoVesta when the strategy is flat.

{
  "symbol": "{{ticker}}",
  "action": "{{strategy.order.action}}",
  "market_position": "{{strategy.market_position}}",
  "prev_market_position": "{{strategy.prev_market_position}}",
  "position_size": "{{strategy.position_size}}",
  "price": "{{close}}"
}

TradingView only shows the Webhook URL box when two-factor authentication is on in your TradingView account. TradingView cannot send custom headers, so AlgoVesta verifies the source from TradingView's own server addresses and auto-trades only alerts it can verify.

Connect your Binance API key

Create the key in Binance with these permissions: Enable Spot & Margin Trading + Enable Futures. Withdrawal and transfer stay disabled, because AlgoVesta never needs them: it can place and close orders, but it cannot move funds out of your account. Binance keys have a key and a secret only, with no passphrase.

If you restrict the key to IP addresses, the AlgoVesta connection wizard shows the two server addresses to add. The full click-by-click guide, with what each Binance screen looks like, is in the help center.

How to connect Binance to AlgoVesta →

Rules that apply to every order

• A stop-loss on every order: from the signal, or from your own percentage or distance. No stop-loss source, no order.
• A daily-loss limit that pauses new entries until the next UTC day.
• Maximum open positions and maximum trades per day per bot.
• A panic button that closes what AlgoVesta opened and leaves your own positions alone.

On crypto exchanges an order opens in about 4.1 seconds on average, from the signal arriving to a filled order with its protection attached, measured across AlgoVesta's own executions.