What is a TradingView webhook?

Risk warning: CFDs are complex instruments with a high risk of losing money rapidly due to leverage. 70–80% of retail investor accounts lose money when trading CFDs. Risk disclosure · Past performance.

Webhooks turn TradingView alerts from passive notifications into machine-readable events. The alert condition is your trigger, the alert message is the payload, and the webhook URL is the destination. TradingView never receives anything back and never sends trades itself — it only fires the POST. Any automation happens entirely on the receiving service.

A TradingView webhook works in three parts: a trigger, a payload, and a destination. The trigger is the alert condition you set — for example, when a strategy fires a buy or sell, or when price crosses a level. When that condition is met, TradingView builds the alert message and POSTs it to the webhook URL.

The payload is whatever you write in the alert's Message field. TradingView lets you embed placeholders that it substitutes with live values at the moment the alert fires — so the receiving service gets the actual symbol, price and action rather than a static string.

• {{ticker}} — the symbol the alert fired on (e.g. EURUSD)
• {{close}} — the closing price of the current bar
• {{strategy.order.action}} — "buy" or "sell" from a strategy order
• A typical message is JSON, e.g. {"action": "{{strategy.order.action}}", "symbol": "{{ticker}}", "price": {{close}}}

Most webhook integrations expect JSON, because it is structured and easy for a receiving service to parse. A common pattern uses an action field for direction, a symbol field for the instrument, and numeric fields for price, stop-loss and take-profit.

The placeholders are filled in by TradingView when the alert fires, so the destination receives concrete numbers. Fields like stop-loss, take-profit and lot size can be hard-coded, left at zero to mean "none" or "market", or driven by your strategy's own variables — the exact schema is defined by whatever service you send the webhook to, not by TradingView.

A TradingView webhook lets you connect an alert to almost anything that can receive an HTTP POST. The most common use in trading is automated execution: the webhook forwards a strategy or indicator signal to a service that translates it into a real order on a broker account.

Because the payload is just data, webhooks are also used to log signals to a spreadsheet or database, push notifications into chat apps, or chain TradingView into a larger automation pipeline. PipSync, for example, exposes a per-account webhook URL that accepts a JSON payload and routes the resulting trade to platforms such as MetaTrader 4, MetaTrader 5, cTrader, Match-Trader, Binance Futures or Bybit — but the webhook itself is platform-agnostic and works the same way regardless of the receiver.

A webhook needs a destination that can accept an inbound HTTP POST at a public URL. MetaTrader 4 and MetaTrader 5 are trading terminals: they connect outward to a broker server and do not expose a public inbound endpoint that TradingView could post to. So pointing a TradingView alert directly at "MetaTrader" has nowhere to land.

Bridging the gap requires an intermediary that does have a webhook URL: it receives TradingView's POST, parses the JSON, and then sends the order to MetaTrader through the broker's API on your behalf. This is exactly the role described on the metatrader-webhook page — the webhook hits a service, and the service talks to MT4/MT5.