TradingView Webhook for Futures Accounts

How the webhook works and how to set it up

TradingView cannot place orders on a futures broker by itself. What it can do is send an HTTP POST to a URL of your choice when an alert fires. Signal Trade App gives you that URL. The address has the form /api/webhook/ followed by a long random token, and the token is the only credential, so treat the URL like a password.

Each token is tied to one trading account. When a POST arrives we look up the token, check that the account belongs to you and is not locked or inactive, then place the order on the broker connection for that account. The body is parsed as JSON even though TradingView labels alert messages as plain text, so you do not need to set any content type.

Setup takes a few minutes once your broker connection is live.

• Connect your Tradovate or Rithmic account in Signal Trade App.
• Open the Signals page, create a webhook token, and choose the account it should trade. Copy the webhook URL.
• In TradingView, create or edit an alert, tick Webhook URL in the notifications section, and paste the URL.
• In the Message box, paste one JSON message (examples below) and nothing else. Two messages in one box make the JSON invalid.
• Save the alert, let it fire once on a small size, and confirm the row in the signal log reads EXECUTED.

The JSON message our webhook accepts

A basic entry needs three fields. A minimal message looks like this: {"action": "buy", "symbol": "MNQ1!", "qty": 1}. The supported fields are listed below.

• action: buy, sell, close (flat, flatten and exit are also accepted) or breakeven. Required.
• symbol: for example ES1! or MNQ1!. Required for buy and sell.
• qty: whole contracts. Required for buy and sell.
• orderType: market, limit or stop. Defaults to market.
• price: the limit or stop price. Required for limit and stop orders.
• takeProfit and stopLoss: optional bracket prices that work with any order type.

Brackets, exits and multiple accounts

If your script is a strategy, TradingView fills in placeholders when the alert fires. A message of {"action": "{{strategy.order.action}}", "symbol": "{{ticker}}", "qty": {{strategy.order.contracts}}, "orderType": "market"} follows the strategy on every entry and exit. Create the alert on the strategy and set the trigger to order fills.

TradingView has no placeholder for a strategy's internal take-profit and stop-loss variables. To send them, plot them with display set to none and reference {{plot_0}} and {{plot_1}} in the message, or build the whole JSON string in Pine and send it with alert(). Indicators cannot use the strategy placeholders, so write the values directly or build the message in code.

When you send takeProfit, stopLoss or both with an entry, they are attached as a bracket and linked one-cancels-other at the broker. For Tradovate accounts, we confirm the legs with the broker before answering. If the broker refuses a leg, the request returns an error that says the entry was placed but the bracket is incomplete, so you check the account instead of resending.

A close action that names a symbol closes that symbol only: its position and its working orders, leaving every other symbol on the account alone. A close with no symbol flattens the whole account: it cancels resting orders and closes every open position.

Two more actions act on a position that is already open. Protect takes tp and sl arrays of prices and optionally autoBreakevenUsd. Breakeven moves the stop to your average entry price for the whole position and keeps the take-profit: {"action": "breakeven", "symbol": "MNQ1!"}. It is refused while the position is not in profit. Neither needs a quantity.

Multiple accounts and prop firm setups

A token trades one account. To run the same alert across several funded accounts, point the token at the account that leads a copy group and let the copy engine pass its orders to the followers, including followers on a different broker. That keeps you at one alert and one webhook regardless of how many accounts follow.

Limits and troubleshooting

TradingView requires a paid plan for webhook alerts and two-factor authentication on your TradingView account. Check TradingView's current documentation for the exact plan requirements. Set the alert frequency deliberately: once per bar close is the safe default for strategies, because a once-per-bar alert can fire several times on a forming candle.

Most failures show up in the signal log with a plain message. Invalid JSON is logged as an error. A missing action, symbol or qty is logged as rejected. A bare symbol such as MNQ! without the 1! suffix is not supported. A disabled token returns 403, an unknown token returns 401, and a locked or inactive account is refused. If a broker rejects an order after we sent it, the log row is corrected from EXECUTED to REJECTED with the broker's reason.