TradingView Webhook Not Working: Fix Common Issues Fast

Troubleshoot TradingView webhook failures caused by URL typos, malformed JSON, or broker API errors. Use this guide to ensure your automated trades execute.

TradingView webhooks fail for several common reasons: incorrect URL formatting, missing or malformed JSON payload, alert misconfiguration, broker API authentication errors, or network/firewall blocks. The fix depends on identifying which component is breaking—webhook delivery, JSON syntax, or broker connection. Testing each layer systematically (TradingView alert trigger, webhook delivery logs, broker API response) isolates the problem and points to the specific configuration error causing the failure.

Key Takeaways

Most webhook failures stem from URL typos, incorrect JSON formatting, or missing authentication tokens—check these first
TradingView's webhook field is case-sensitive and requires exact JSON syntax with no trailing commas or missing quotes
Use webhook testing tools like Webhook.site to verify TradingView is sending data before troubleshooting broker connection
Broker API errors often return specific codes—check your platform's logs to see if the webhook reached the broker but was rejected

Why Do TradingView Webhooks Fail?

Webhooks fail when any part of the alert-to-execution chain breaks: TradingView alert trigger, webhook delivery, JSON parsing, or broker API acceptance. The most common failure points are incorrect webhook URLs (wrong domain, missing endpoint, typos), malformed JSON payloads (syntax errors, missing fields), and broker authentication failures (expired tokens, incorrect API keys). Each failure type produces different symptoms—alerts fire but trades don't execute, webhook logs show no activity, or broker returns specific error codes.

Webhook: A webhook is an HTTP POST request sent from TradingView to your automation platform when an alert triggers. It carries your trade parameters as JSON data, which the receiving platform parses and converts into broker orders.

Network issues and firewall blocks affect about 5-10% of webhook failures. Some corporate networks or VPNs block outbound webhook traffic. Rate limiting can also cause problems—TradingView allows multiple alerts per minute, but some platforms throttle incoming webhooks during high-frequency strategies.

The fix strategy is systematic: test TradingView delivery first, then JSON syntax, then broker connection. This isolates the exact failure point instead of guessing across multiple components.

How to Verify Your Webhook URL Is Correct

The webhook URL must exactly match your automation platform's endpoint, including protocol (https://), domain, path, and any query parameters. Copy the URL directly from your platform dashboard—don't type it manually. Check for trailing slashes, which some platforms require and others reject. Verify the domain is spelled correctly and includes the full subdomain if required (e.g., api.platform.com vs. platform.com).

Test the URL in a browser or with a tool like cURL to confirm it's reachable. A working endpoint typically returns a 200 or 405 status (405 means it's live but expects POST, not GET). A 404 error means the endpoint doesn't exist. A timeout suggests network or firewall issues.

For platforms like ClearEdge Trading, the webhook URL includes your account-specific token as part of the path or query string. Regenerating your API token invalidates the old URL—if webhooks stopped working after changing settings, verify you updated TradingView with the new URL.

Common JSON Payload Formatting Mistakes

JSON syntax errors are the most frequent cause of webhook failures after URL problems. Missing quotes around field names, trailing commas after the last field, single quotes instead of double quotes, and unescaped special characters all break JSON parsing. TradingView's webhook message field requires valid JSON—even one syntax error causes the entire payload to fail.

Here's a valid JSON payload example:

{
"ticker": "{{ticker}}",
"action": "{{strategy.order.action}}",
"quantity": {{strategy.order.contracts}},
"price": {{close}}
}

Common errors include:

Trailing comma after last field: "price": {{close}}, (invalid)
Single quotes: 'ticker': '{{ticker}}' (invalid)
Missing quotes on strings: {ticker: {{ticker}}} (invalid)
Missing comma between fields: "action": "buy" "quantity": 1 (invalid)

Use a JSON validator (jsonlint.com) to check syntax before pasting into TradingView. Copy your webhook message, replace TradingView placeholders like {{ticker}} with sample values ("ES"), then validate. If the validator shows errors, fix them before testing live alerts.

JSON Payload: The JSON payload is the structured data sent in the webhook containing your trade parameters—ticker, action (buy/sell), quantity, price, and any custom fields. Your automation platform parses this JSON to extract order details and execute the trade.

How to Test If TradingView Is Sending Webhooks

Before troubleshooting your broker connection, confirm TradingView is actually sending webhooks. Use Webhook.site or a similar testing service: create a unique test URL, paste it into your TradingView alert's webhook URL field, and trigger the alert manually. If the test site receives a POST request with your JSON payload, TradingView delivery works—the problem is downstream in your automation platform or broker API.

If Webhook.site receives nothing, the issue is in TradingView alert configuration. Check that the alert's "Notifications" tab has the webhook URL filled in and "Webhook URL" is enabled. Verify the alert actually fired by checking TradingView's alert log (clock icon in the top menu). If the alert didn't fire, the problem is alert conditions, not webhooks.

Check alert expiration settings. Alerts set to "Once" expire after first trigger. Alerts with date/time limits stop firing after expiration. "Every time" alerts fire repeatedly but can be disabled if you accidentally clicked "Stop" in the alert panel.

Network restrictions occasionally block webhook delivery. Test from a different network (mobile hotspot vs. home WiFi) to rule out firewall issues. Some workplace or school networks block outbound webhooks entirely.

Troubleshooting Broker API Connection Errors

If TradingView sends webhooks but trades don't execute, the broker API connection is failing. Check your automation platform's logs for specific error messages—most platforms show broker responses like "invalid credentials," "insufficient margin," or "symbol not found." These errors mean the webhook reached your platform but the broker rejected the order.

Authentication errors ("unauthorized," "invalid token") mean API credentials expired or were entered incorrectly. Regenerate API keys in your broker dashboard and update them in your automation platform. For brokers that support automation, credential refresh intervals vary—some expire keys after 90 days, others after inactivity periods.

Symbol mapping issues cause "invalid symbol" errors. TradingView uses different ticker formats than some brokers (e.g., TradingView shows "ES1!" for continuous ES contract, but broker API expects "ESH4" for March 2024 contract). Verify your automation platform maps TradingView symbols to broker-specific codes correctly.

Error TypeCauseFixUnauthorizedExpired/incorrect API keyRegenerate and update credentialsInsufficient marginAccount lacks capital for positionReduce quantity or add fundsInvalid symbolTicker format mismatchCheck symbol mapping settingsTimeoutBroker API slow or downCheck broker status pageRate limit exceededToo many orders per minuteSlow alert frequency or increase limits

Broker API outages happen during high volatility or maintenance windows. Check your broker's status page or contact support to confirm API availability. Some brokers throttle API requests during FOMC announcements or NFP releases to protect systems.

Alert Configuration Problems That Break Webhooks

Alert conditions that never trigger will never send webhooks. Verify your Pine Script alert conditions or indicator-based alerts actually evaluate to true. Use TradingView's Strategy Tester to confirm your strategy generates signals in historical data. If backtesting shows zero trades, your logic may be too restrictive or contain errors.

Alert frequency settings affect webhook delivery. "Once Per Bar Close" fires only when the candle closes, which delays execution. "Once Per Bar" fires immediately on signal but only once per candle. For futures automation requiring fast execution, "Once Per Bar" or real-time alerts are preferred over bar-close triggers.

Alert Conditions: Alert conditions are the logical rules in Pine Script or indicator settings that determine when TradingView fires an alert. Conditions combine price, indicator values, and comparison operators—alerts trigger when the condition evaluates to true.

Placeholder syntax errors break JSON payloads. TradingView provides placeholders like {{ticker}}, {{close}}, and {{strategy.order.action}} to insert dynamic values. Misspelling these ({{tickers}}, {{strategy.action}}) produces blank or error values. Reference TradingView's placeholder documentation to confirm exact syntax.

Some strategies use compound alerts (multiple conditions in one alert). If any condition fails to evaluate correctly, the entire alert may not fire. Simplify to single-condition alerts for testing, then rebuild complexity once basic webhooks work.

Step-by-Step Webhook Troubleshooting Checklist

Webhook Debugging Checklist

☐ Verify webhook URL is copied exactly from platform dashboard (no typos, correct protocol)
☐ Test URL in browser or Webhook.site to confirm it's reachable
☐ Validate JSON payload syntax with jsonlint.com (replace placeholders with sample values first)
☐ Check TradingView alert log to confirm alert actually fired
☐ Verify alert has webhook URL filled in and enabled in Notifications tab
☐ Use Webhook.site to test TradingView delivery (confirms TradingView sends data)
☐ Check automation platform logs for broker API error messages
☐ Verify broker API credentials are current and correctly entered
☐ Confirm symbol mapping matches broker's expected ticker format
☐ Test from different network to rule out firewall blocks
☐ Check alert expiration settings and frequency (Once vs. Every time)
☐ Verify account has sufficient margin for position size in JSON payload

Work through this checklist in order—each step isolates a specific failure point. Most webhook issues resolve within the first four checks (URL, JSON, alert fired, webhook enabled). If you reach broker API checks, the problem is authentication or order parameters, not webhook delivery.

Frequently Asked Questions

1. Why does my TradingView alert fire but no trade executes?

The alert firing confirms TradingView's alert conditions work, but the webhook or broker connection is failing. Check your automation platform's logs for error messages—common causes include expired API credentials, insufficient account margin, or incorrect symbol mapping between TradingView and your broker.

2. How do I know if TradingView is actually sending webhooks?

Use Webhook.site: create a test URL, paste it into your TradingView alert's webhook field, and manually trigger the alert. If Webhook.site receives a POST request with your JSON data, TradingView delivery works and the problem is in your automation platform or broker API.

3. What does "invalid JSON" mean in webhook errors?

Invalid JSON means your webhook message has syntax errors—missing quotes, trailing commas, or incorrect formatting. Copy your webhook message, replace TradingView placeholders with sample values, and test it at jsonlint.com to find and fix syntax errors.

4. Can network firewalls block TradingView webhooks?

Yes, some corporate or school networks block outbound webhook traffic. Test from a different network (mobile hotspot) to rule out firewall restrictions. If webhooks work on mobile but not your main network, contact your IT department about webhook URL whitelisting.

5. Why did my webhooks stop working suddenly?

Common causes include expired broker API credentials, changed webhook URLs after platform settings updates, or alert expiration settings. Check your automation platform for credential refresh requirements and verify the webhook URL in TradingView matches your current platform endpoint.

Conclusion

TradingView webhook failures almost always trace to incorrect URLs, malformed JSON, or broker API authentication—systematic testing of each component identifies the exact problem. Use webhook testing tools to isolate TradingView delivery from broker connection issues, and check platform logs for specific error messages that point to credential, margin, or symbol mapping problems.

For additional webhook configuration guidance, see our complete TradingView automation guide. Paper trade new webhook setups before going live to catch configuration errors without risking capital.

Need a no-code solution for TradingView automation? Explore ClearEdge Trading for webhook-to-broker execution with built-in troubleshooting logs and support.

References

TradingView. "Alerts - TradingView Wiki." https://www.tradingview.com/support/solutions/43000529348-about-tradingview-alerts/
TradingView. "Webhooks - Using Webhooks with Alerts." https://www.tradingview.com/support/solutions/43000529273-webhooks/
JSON.org. "Introducing JSON." https://www.json.org/json-en.html
CME Group. "API Documentation - Market Data and Order Entry." https://www.cmegroup.com/market-data/api.html

Disclaimer: This article is for educational and informational purposes only. It does not constitute trading advice, investment advice, or any recommendation to buy or sell futures contracts. ClearEdge Trading is a software platform that executes trades based on your predefined rules—it does not provide trading signals, strategies, or personalized recommendations.

Risk Warning: Futures trading involves substantial risk of loss and is not suitable for all investors. You could lose more than your initial investment. Past performance of any trading system, methodology, or strategy is not indicative of future results. Before trading futures, you should carefully consider your financial situation and risk tolerance. Only trade with capital you can afford to lose.

CFTC RULE 4.41: Hypothetical or simulated performance results have certain limitations. Unlike an actual performance record, simulated results do not represent actual trading. Also, since the trades have not been executed, the results may have under-or-over compensated for the impact, if any, of certain market factors, such as lack of liquidity.

By: ClearEdge Trading Team | 29+ Years CME Floor Trading Experience | About

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5

Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.