Questions › Guides

TradingView webhook not received: 7 things to check

Your alert shows in TradingView's Alerts log, but your server logs show nothing. That means the alert fired and the problem is somewhere between TradingView and your app. (If there's no entry in the log, start with why didn't my TradingView alert fire? instead. No webhook tool can fix an alert that never fired.)

Every rule below is from TradingView's own webhook documentation unless noted.

The 7-point checklist

  1. Webhooks are switched on for your account. "Webhook alerts are only allowed when 2-factor authentication is enabled." Turn on 2FA in your TradingView account settings. Check that your TradingView plan includes webhook alerts (TradingView plans).
  2. The Webhook URL box is ticked on this alert. Open the alert, go to the Notifications tab, tick Webhook URL and paste the full URL. Remember that editing a script doesn't update an existing alert; recreate it (Pine FAQ).
  3. The port is 80 or 443. "Only ports 80 and 443 are accepted. Requests to other ports will be rejected." A URL like https://example.com:8080/hook won't work. Put a reverse proxy on 443 in front of your app.
  4. The address is reachable over IPv4. "IPv6 isn't currently supported for webhooks." If your host only has an AAAA record, TradingView can't reach it. Use a public IPv4 address, not a private one (192.168.x.x or 10.x.x.x) or localhost.
  5. The TLS certificate is valid. For HTTPS URLs, use a certificate from a public CA with the full chain installed. A self-signed or expired certificate, or a missing intermediate, is a common reason for silent failures. TradingView's docs don't spell out its TLS rules, so treat this as best practice.
  6. Your firewall lets TradingView in. TradingView sends from four published IPs: 52.89.214.238, 34.212.75.30, 54.218.53.128 and 52.32.178.7. If you allowlist, include all four, and recheck the webhook page from time to time in case the list changes.
  7. Your app answers quickly and without redirects. Requests that take longer than about three seconds are cancelled (timeout guide). Avoid http→https, trailing-slash and www→apex redirects. Use the final URL. TradingView's docs don't say whether webhooks follow redirects, and a redirect adds a round trip inside the 3-second limit.

Check the message too

TradingView sends the message as the request body: application/json if it's valid JSON, otherwise text/plain. If your endpoint expects JSON and gets text, it may reject the alert, which looks like "not received" in your app logs. Use double quotes for JSON keys and string values (Pine FAQ). Placeholders such as {{ticker}} and {{close}} are filled in when the alert fires (placeholder docs). Note that alert() calls in Pine don't process placeholders.

Test it in one step

Our free Webhook Checker for TradingView needs no signup and doesn't store your URL or message (only a one-way hash of the URL, to count tests). Enter your URL and our server sends one test request. It reports whether the URL is HTTPS on port 443 or 80, whether the address is public, whether the host has a public IPv4 address, whether the TLS certificate is valid, whether the response comes back within ~3 s, whether the status is 2xx, and whether there are redirects. Paste your message template and it checks for valid JSON, placeholders and size.

It tests from our server, not TradingView's, so it can't prove your firewall allows TradingView's IPs, and it can't see TradingView's logs.

If your server is fine but sometimes down

Once the path works, the next risk is your endpoint being slow, restarting or briefly offline when an alert arrives. HoldAlarms sits in between: we answer TradingView quickly, queue the alert, and retry delivery up to 5 times, 2 to 60 seconds apart; permanent errors aren't retried. Alerts that keep failing are parked in a dead-letter queue, and failure emails are grouped and capped at up to 10 a day. Your endpoint needs a public HTTPS URL, or you can watch alerts arrive in our hosted inbox. Starter is €19/mo, Ops €49/mo.

Check your URL with the free Webhook Checker for TradingView Start your free trial: 300 alerts or 7 days, whichever comes first, no card

Questions

Which ports does TradingView allow for webhooks?

Only 80 and 443. Requests to other ports are rejected.

Does TradingView support IPv6 webhooks?

No. TradingView's docs say IPv6 isn't currently supported for webhooks.

What IP addresses does TradingView send webhooks from?

TradingView lists 52.89.214.238, 34.212.75.30, 54.218.53.128 and 52.32.178.7 on its webhook help page.

Why can't I enable the webhook option?

TradingView only allows webhook alerts when 2-factor authentication is on, and your TradingView plan needs to include webhook alerts.

More guides

HoldAlarms is not affiliated with TradingView. TradingView is a trademark of TradingView, Inc.