TradingView
Webhook JSON
Generator

Indicator alert example

Indicators do not automatically provide strategy order variables, so action and size are usually explicit in each alert. A long alert can use buy and a fixed quantity, while the corresponding short alert uses sell. This example sends relative SL/TP distances in pips.

{
  "platform_name": "metatrader5",
  "trade_type": "netting",
  "ticker": "{{ticker}}",
  "order_action": "buy",
  "order_contracts": 0.10,
  "sltp_type": "pips",
  "stop_loss": 25,
  "take_profit": 50
}

For exact protective prices, remove sltp_type, stop_loss and take_profit and use sl_price and tp_price. The TradingView SL/TP Calculator converts the same Entry, SL and TP levels into percent, pips and absolute-price JSON.

Strategy alert example

Strategies can fill dynamic values when the alert fires. The wizard can use the current strategy position as the action and the strategy order size as quantity, avoiding a hard-coded contract amount.

{
  "platform_name": "tradovate_api",
  "trade_type": "hedge",
  "ticker": "{{ticker}}",
  "order_action": "{{strategy.market_position}}",
  "order_contracts": "{{strategy.order.contracts}}"
}

Paste the generated payload into TradingView's alert Message field. Strategy alerts and indicator alerts do not use exactly the same TradingView variables, which is why the public wizard asks about the script type before generating the result.

Common webhook message problems

• Invalid JSON. Extra text, smart quotes, missing quotation marks or trailing commas can invalidate the whole message. Keep the alert Message field as valid JSON.
• Mixing relative and absolute SL/TP. stop_loss and take_profit are distances when paired with sltp_type. sl_price and tp_price are actual market prices.
• Strategy placeholders inside an indicator alert. Values such as {{strategy.order.contracts}} belong to strategy alerts. Indicator alerts normally use explicit actions and quantities unless the script builds its own dynamic message.
• Wrong symbol assumptions. A TradingView ticker is not always written exactly like the symbol used by the broker or exchange. Use the symbol handling required by the destination connection.
• Unsupported optional fields. Leverage, hedge controls and other optional parameters should appear only when they are relevant to the selected destination and mode.

A good troubleshooting workflow is to generate the message first, copy it unchanged, test it, and then modify only values you understand. Keeping the JSON compact makes errors easier to identify.