TradingView Webhooks FAQ

Run five checks from TradingView's Pine Script FAQ. First, confirm the alert is active and not expired, because created alerts do not fire after they expire. Second, open the alert log: an alert can fire without sending a notification. Third, check for repainting, which shifts when signals appear. Fourth, TradingView halts an alert that triggers more than 15 times in 3 minutes. Fifth, a script runtime error stops that script's alerts. Also, an alert runs on a saved copy of the script and its inputs, so after changing settings on your chart, delete the alert and create a new one.

"Once per bar" fires the first time the condition is true while the candle is still forming. "Once per bar close" waits for the candle to close and fires only if the condition is still true then. The trade-off: "Once per bar" is earlier but can fire on a signal that disappears by the close, for example an RSI cross that reverses before the bar ends, according to TradingView's Help Center. If you want alerts to match what the chart shows after the close, the Pine Script FAQ recommends "Once Per Bar Close".

They are the two trigger types for an alert on a TradingView strategy. "Order fills" fires whenever the strategy's simulated broker fills an order, such as an entry, exit, stop or target. "alert() function calls" fires only when the script runs an alert() call its author wrote. Per the Pine Script docs, strategies run alert() calls only at bar close by default, while alerts from order fill events "execute immediately", which the docs call "often more suitable for sending alerts to third parties for automation." If the script has no alert() calls, that option sends nothing.

Yes to both, as of 5 Oct 2026. TradingView's pricing comparison table marks "Webhook notifications" as not included on the free Basic plan and included on Essential, Plus, Premium and Ultimate. Separately, the Help Center says webhook alerts are only allowed when two-factor authentication is enabled. So you need a paid plan and 2FA turned on in your TradingView account before you can use webhook alerts. TradingView also warns not to put login credentials or passwords in the webhook message body.

Check TradingView's documented webhook limits first. The Help Center says only ports 80 and 443 are accepted, requests are cancelled if the receiving server takes longer than three seconds to process them, and IPv6 is not supported. If your server has a firewall, allowlist the four TradingView IP addresses listed on that Help Center page. Then open the alert log and read the "Webhook status" column, which shows delivery failures. TradingView also notes webhooks may occasionally fail to reach the URL, so treat a webhook as a best-effort channel, not guaranteed delivery.

Two per chart. TradingView's pricing page, checked 5 Oct 2026, lists indicators per chart as 2 on Basic (free), 5 on Essential, 10 on Plus, 25 on Premium and 50 on Ultimate. The free plan is also tighter on alerts: the comparison table shows 3 active price alerts on Basic and marks technical alerts as not included. TradingView counts any alert built on an indicator, strategy or drawing as a technical alert, so alerts from an indicator need a paid plan. Plan limits change, so check the pricing page before you buy.

Yes, but there is a cost. By default a TradingView strategy calculates only when a bar closes. Turning on "On realtime bar tick" in the strategy's Script execution settings (calc_on_every_tick = true in code) lets it calculate on every price update, so orders and alerts can fire mid-candle. The Pine Script docs warn this can cause repainting in the strategy's orders and results, because after a reload, historical bars do not keep the intrabar ticks the strategy acted on. The backtest may then not show the trades your live alerts sent.

TradingView documents specific delay cases, not a general latency figure. Its Help Center says "Once Per Bar Close" alerts wait for the first trade of the next bar to confirm the close, so on thinly traded symbols they can arrive several seconds late; if no trades arrive, for example after a session closes, the server closes the bar 1 minute after its formal close. Strategy alerts can also look late in the Strategy Tester, because historical orders show the bar's open time, not the real fill time. We found no official TradingView figure for total alert-to-broker latency.

Yes for CME Group markets unless you add real-time data. TradingView's CME page states that all CME Group data is free on TradingView with a 10-minute delay, and real-time CME, CBOT, COMEX and NYMEX data is sold as a separate subscription. The Help Center adds a catch for traders who connect a broker: the order panel and buy and sell buttons use your broker's data, not TradingView's, so those quotes can still be delayed even after you buy real-time chart data. Check which feed your chart and order panel use before trading.

Yes. TradingView's Help Center says alerts are server-side, so you can close TradingView or leave the chart page and they keep working. When you create an alert on a script, TradingView saves a copy of the script, its inputs, the symbol and the timeframe, and runs that copy on its servers. The catch: later edits on your chart do not reach the running alert. If you change a setting, symbol or timeframe, delete the old alert and create a new one, or it keeps firing on the old settings.