Webhook Checker for TradingView
Test your webhook URL and alert message in a few seconds. Free, no signup.
What it checks
- HTTPS (plain HTTP works on port 80 but is unencrypted)
- Port 80 or 443: TradingView rejects other ports
- Public IPv4 address: TradingView doesn't support IPv6 for webhooks
- Valid TLS certificate
- 2xx status and a reply within about 3 seconds, with the time in milliseconds
- No redirect: we don't follow redirects, and TradingView's docs don't promise to
- Alert message: valid JSON, misspelled or unquoted
{{placeholders}}, size - Common mistakes: curly quotes, a trailing comma or a missing comma (with the line to fix)
- Destination (optional): pick a tool to get a link to its own docs for the message format. We don't check any tool's fields; HoldAlarms forwards the message unchanged.
Example messages
Two generic examples for the alert's Message box: a JSON message with the symbol, price and time, and a Slack-style text message. HoldAlarms forwards whatever you put there unchanged.
{"ticker":"{{ticker}}","price":{{close}},"fired_at":"{{timenow}}"}
{"text":"{{ticker}} alert fired at {{close}}"}
Sending to a third-party tool? Paste the message exactly as that tool's docs show it. HoldAlarms forwards it unchanged.
What it can't tell you
We test from our server, not TradingView's. We can't see whether TradingView fired your alert, and one passing test doesn't mean your endpoint is always up. A 2xx means your server received the request, not that it finished processing it.
Common causes on the TradingView side
- The alert expired or stopped (check its status in the Alerts Manager).
- "Only once" alerts stop after one trigger; "Once per bar close" waits for the bar to close.
- Webhooks need two-factor authentication turned on and a TradingView plan that includes them.
- You edited the script after creating the alert: alerts keep the old version until you recreate them.
- Repainting or intrabar conditions can trigger differently on live bars.
More in our questions page. HoldAlarms answers TradingView as soon as the alert is queued, designed to reply fast, well before its ~3-second timeout and retries delivery to your endpoint 5 times. It can't fix a wrong URL. Free trial: 300 alerts or 7 days, whichever comes first, no card.