TradingView webhook alerts with retry, logs, and deduplication
TradingView fires webhooks — SignalTo receives, validates, retries on failure, and logs every attempt. Built for traders who need proof that alerts actually delivered.
Webhook reliability for serious traders
A raw Discord or Telegram webhook URL in TradingView works until it doesn't. SignalTo adds the retry layer, observability, and routing that production signal workflows require.
- Dedicated endpoint per strategy — isolate alerts and route to different channels.
- Configurable auto-retry with backoff — recover from transient failures without manual intervention.
- Complete event timeline: received → queued → delivered or failed, with HTTP status codes.
- Deduplication window stops duplicate alerts from flooding your channels during fast markets.
How SignalTo handles your webhooks
- 01
TradingView sends the alert
Your strategy triggers and TradingView POSTs the webhook payload to your SignalTo endpoint URL.
- 02
SignalTo validates and queues delivery
We parse the payload, apply deduplication, format the message, and enqueue delivery to your configured channels.
- 03
Retry on failure, log everything
If the target channel is down, SignalTo retries automatically. Every attempt is recorded in your delivery dashboard.
TradingView webhook requirements
TradingView enforces these rules on every webhook URL. Break any one and alerts silently fail or show errors in the alert log.
| Requirement | What TradingView expects |
|---|---|
| HTTPS only | http:// URLs are rejected. The SSL certificate must be valid. |
| Ports 80 or 443 | URLs with :3000, :8080, or any other port are rejected. |
| Public IPv4 | No localhost, private LAN IPs, or IPv6-only hosts. |
| 3-second response | Your endpoint must return HTTP 200 within 3 seconds or the delivery is marked failed. |
| 2FA enabled | Webhook alerts are only allowed on accounts with two-factor authentication turned on. |
Example JSON alert message
When the Message field contains valid JSON, TradingView sends Content-Type: application/json. Use TradingView placeholders for live market data.
{
"symbol": "{{ticker}}",
"action": "{{strategy.order.action}}",
"price": "{{close}}",
"exchange": "{{exchange}}"
}TradingView webhook FAQ
- Does the free TradingView plan support webhooks?
- No. The Basic (free) plan does not include webhook URLs on alerts. You need Essential or higher.
- Why do my webhooks work sometimes and fail other times?
- Usually the 3-second timeout. If your receiver does heavy work before returning 200, sporadic slow responses get marked as failed. Acknowledge fast, process async.
- Does SignalTo place trades for me?
- No. SignalTo only forwards alert notifications to Telegram, Discord, or Feishu. It never touches your broker account or places orders.
- Can I paste a Discord webhook URL directly into TradingView?
- Sometimes, but Discord expects a specific JSON shape. Plain TradingView text often fails. A relay like SignalTo formats the payload and adds retries plus delivery logs.
- What JSON format should I use?
- Match what your receiver expects. For SignalTo, a simple JSON object with symbol, action, and price fields works. See the example above.
- Is there a free trial?
- Yes — 7 days, one webhook endpoint, two delivery channels, and 1,000 signals per month. No credit card required.
Upgrade your TradingView webhook setup
Replace fragile direct webhooks with managed forwarding. Free trial — no server required.
Start free trial