A TradingView webhook sends an HTTP POST to your address when an alert fires, from one of four IP addresses that TradingView publishes. TradingView's terms license its charts, alerts and webhooks for display-only use, and list automated trading among the prohibited uses. A bot that places trades from TradingView alerts therefore goes against those terms. A proxy does not fit that job. This page sets out the webhook rules, what the terms say about bots and scraping, and the separate case of an exchange that locks an API key to listed IPs.
How TradingView webhooks work
When an alert fires, TradingView sends a POST request to the address you gave it, with the alert message in the body. If the message is valid JSON, the request carries an "application/json" header, and otherwise "text/plain". It sets a few firm rules:
| rule | what TradingView says |
|---|---|
| sender IPs | 52.89.214.238, 34.212.75.30, 54.218.53.128 and 52.32.178.7, "in case they need to be allowlisted". |
| ports | Only ports 80 and 443. Requests to other ports are rejected. |
| time limit | A request is cancelled if the server takes longer than three seconds. |
| IPv6 | Not supported for webhooks. |
| account | Webhook alerts are only allowed when two-factor authentication is on. |
It also warns against putting login details or passwords in the webhook body. You can follow each delivery in the "Webhook status" column of the alert log.
When a webhook fails
Its error guide says most errors come from the receiving server. Its list of causes is practical:
| error | causes TradingView names |
|---|---|
| 3xx, redirection | The domain or path changed, a redirect to a sign-in page, or a proxy with redirection. |
| 4xx, client error | The endpoint does not exist, an authorization error, invalid JSON, or too many requests. |
| 5xx, server error | The server is unavailable, or processing timed out. |
| timeout | No answer within three seconds, often from an overloaded server or a network issue. |
| address not allowed | The URL points to localhost, an internal address or a private IP. |
A proxy that redirects in front of your endpoint is one of the named causes of failure. The fix there is to point the webhook straight at a public address on port 80 or 443, without the redirect.
What TradingView's terms say about bots
Section 3 of TradingView's terms is direct. Its content and market data, "including but not limited to charts, alerts, webhooks", are "licensed for exclusive display-only use". The license is limited to personal or internal business purposes. The prohibited uses include "any form of automated trading, automated order generation", algorithmic trading and smart order routing.
The terms also reach third parties. They forbid products or services that rely on its alerts or webhooks for automated trading. They also forbid any service that advertises webhooks for those purposes. In the words of the terms, webhooks are "intended solely for permissible uses within the scope of display and personal or internal business purposes". Without a separate agreement, TradingView does "not permit commercial usage of any of our services or APIs". A breach can lead to blocking, account termination and legal action.
The pages that rank for "tradingview bot" sell exactly this kind of automation. None of the five we read mentions the display-only license.
What the terms and robots.txt say about scraping
Some searches ask for a TradingView scraper. The same display-only license covers TradingView's content and data, and commercial use of its services needs a separate agreement. The terms page carries no date, and the copy we read is from 3 October 2026.
The robots.txt file of tradingview.com closes search pages, account pages and the embed widget paths to every crawler it does not name. A separate group shuts many AI crawlers out of ideas, scripts, charts and user pages. For charts on your own site, TradingView lists widgets and charting libraries among its business tools. Its terms say widgets used on other sites must keep their attribution "as was originally designed".
Exchange API keys and fixed addresses
A different question belongs to the exchanges: a fixed IP address for an exchange's API. Kraken's developer guide says: "Lock your API key to the IP addresses your trading system runs from. This single measure prevents almost all key misuse even if the key is leaked." Its help centre calls this IP Address Restriction, which "restricts API key use to specific client side IP addresses".
That rule belongs to the exchange, not to TradingView. It does not change TradingView's terms: trading on its alerts stays a prohibited use, whatever address the orders come from. Software that calls an exchange's API from a fixed address can use the rule. A server with a static IP has such an address, and a static proxy is another way to get one.
Where a proxy fits
A proxy does not fit a TradingView bot. Automated trading on TradingView's alerts goes against its terms, whatever address the orders come from. For webhooks used as the terms allow, a proxy is not needed either. They travel from TradingView's servers to yours, your server can allowlist the four IPs, and a redirecting proxy in front of it is a listed cause of failure.
A static address fits a different job: a service that locks a key to listed IP addresses, as Kraken describes. Our ISP proxies include a static option: one dedicated IP, held as long as you keep it, at $2.70/IP for a month. How to check if a proxy is working shows how to confirm the address a service sees.
The limits of this page
We did not create a TradingView alert or send a webhook, since that needs an account with two-factor authentication. We read TradingView's help pages, terms and robots.txt as text, from our server on 3 October 2026. We did not test any exchange API or IP restriction. Kraken is one exchange, and others set their own rules. This page is due for a check by 4 January 2027.
Sources
Every page below was read on 3 October 2026, from our server in St. Louis.
- TradingView Help, How to configure webhook alerts, "What do errors mean when sending webhooks?" and "I cannot send webhook to a URL with a port number".
- TradingView, Terms of Use, Policies, and Disclaimers, section 3, and the robots.txt file of tradingview.com.
- Kraken Developers, API key permissions, and Kraken Support, How to create an API key on Kraken Pro, last updated 31 March 2025.
- Google autocomplete, US suggestions for TradingView bot and webhook phrases.
