TradingView to Bitget: automate alerts on Bitget USDT-M futures

AlgoVesta executes TradingView alerts on your Bitget account using an API key with a passphrase and trade permission only. On USDT-M futures the stop-loss and take-profit are attached to the position itself in one-way mode. On Bitget spot a stop-loss trigger is placed, but no take-profit, because Bitget spot has no separate take-profit order type here.

How it works

SL and TP attached to Bitget positions

Bitget futures can hold stop-loss and take-profit as properties of the position rather than as standalone orders. AlgoVesta uses that model: it sets your account to one-way mode for the symbol, opens the position and attaches the two levels to it. When you look at the position in the Bitget app, the levels appear on the position card instead of in the open orders list, and AlgoVesta checks them there.

Because the levels belong to the position, closing the position removes them as well; there are no orphaned trigger orders left behind.

Bitget spot: stop-loss only

On Bitget spot the trading library exposes one general trigger price and rejects separate stop-loss and take-profit fields. AlgoVesta therefore places the stop-loss as a trigger (plan) order and does not place a take-profit. The setup screen warns you before you save a spot bot on Bitget, and the exit then comes from your stop or from a closing alert.

Passphrase and permissions

Bitget, OKX and KuCoin all require a passphrase. On Bitget it is set when you create the key and is needed for every signed request. Only the Trade permission is required; keep withdrawals switched off.

Testing a Bitget alert safely

The signal designer has a test button that sends your message through the full check without placing an order, so you can see that the symbol, side and size are understood. After that, run the bot in paper mode for a few alerts; the fills are simulated on a $5,000 virtual balance and appear in the dashboard like real trades.

Switch to live only when the paper results look the way your strategy behaves on the chart.

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 Bitget API key

Create the key in Bitget with these permissions: Trade (withdrawal off). 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. Bitget keys also have a passphrase that you choose when you create the key. Enter it in AlgoVesta together with the key and secret; it is encrypted the same way.

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 Bitget screen looks like, is in the help center.

How to connect Bitget 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.