How to test a TradingView webhook
- 1Create a test URL above. It works for one hour and keeps up to 50 requests.
- 2In TradingView, create a new alert for the test; a plain price alert is enough. Leave your real bot alerts as they are, so a live alert never points here.
- 3In the alert’s Notifications, turn on Webhook URL and paste the test URL. TradingView only allows webhooks when two-factor authentication is on.
- 4Put the message you want to check in the Message box, or use the example in the tester. To check what a script sends with
alert(), create the alert on that script with the condition Any alert() function call instead. - 5Save the alert and let it trigger. Each request appears in the tester a few seconds after it arrives.
- 6Read the verdict and compare the fields with what your bot expects. When it looks right, put your bot’s URL back in the alert.
What the tester checks
Every request gets a verdict at the top, then the points behind it. These are the checks:
Who sent it
Whether the request came from one of TradingView’s four webhook addresses, or from a tool such as curl, Postman or a browser.
JSON or plain text
TradingView sends valid JSON as application/json and anything else as text/plain. The tester shows which one your bot would get.
Where the JSON breaks
The exact line and column, and the usual cause: a trailing comma, curly quotes, a {{ticker}} without quotes, a line break inside a value, NaN.
Placeholders left as typed
A {{close}} that reached the receiver unchanged, as happens with text from a script’s alert() call or a misspelled placeholder.
Missing values
Price, size and other number fields that arrived as NaN or empty, which most bots reject.
The same alert twice
Two identical messages within two minutes. The tester always answers 200, so this is the alert firing twice: two orders on a live bot.
Symbols and secrets
A symbol with an exchange prefix or the .P perpetual suffix, and fields such as passphrase or api_key that do not belong in a test.
Browser visits
A GET from opening the link, which is not what TradingView sends, and why a URL that opens in a browser can still reject alerts.
If nothing arrives
Open the alert log in TradingView and find the alert. No entry means the alert has not triggered, or TradingView stopped it for triggering more than 15 times in three minutes, so nothing was sent. An entry with an error under Webhook status means TradingView tried to send it, and the error names what failed.
The test URL meets every requirement in TradingView’s webhook help: HTTPS on port 443, reachable over IPv4, and an answer in far less than three seconds. So when a test arrives here but your own URL gets nothing, look at your own server: its address, how fast it answers, a firewall in front of it, or what it does with the message.
GuideTradingView Alert Fired, but the Webhook Never Arrived?Read the Webhook status, send a test alert to a free test URL, and fix the step that failed: the alert, the delivery, your server or your bot.Read the guidePrivacy and limits
- A test URL and everything it received are deleted one hour after it was created, or at once when you press Delete now.
- Each URL keeps up to 50 requests, takes at most 20 a minute, and stores the first 32 KB of each request.
- Nothing is forwarded. Requests stop here, and the tester never calls your bot, exchange or broker.
- Only the browser that created a URL can read what it received. The URL itself can only send to it.
- Use a test message. TradingView’s own help says to keep login details and passwords out of webhook messages, and the same goes for a bot’s secret.
Questions
Is the webhook tester free?
Yes. There is no sign-up and no account. Each test URL lasts one hour and keeps up to 50 requests.
Can it test my bot’s own webhook URL?
No. It gives you its own URL and shows what TradingView sends there. It never sends requests to other addresses. Use it to see exactly what your alert sends, then compare that with your bot’s logs and the format it expects.
How do I know a request really came from TradingView?
The tester compares the sender’s address with the four addresses TradingView sends webhooks from: 52.89.214.238, 34.212.75.30, 54.218.53.128 and 52.32.178.7. A test you send yourself with curl or Postman shows as another sender.
Why does a request show as a browser visit?
Opening the URL in a browser sends a GET request. TradingView sends alerts as POST requests with the message as the body, so a browser visit does not test an alert.
Why does my alert arrive as text/plain?
TradingView sends application/json only when the whole message is valid JSON; anything else is sent as text/plain. The tester shows the line and column where the JSON breaks and the usual cause, such as a trailing comma or a placeholder without quotes.
Does TradingView retry a webhook that fails?
Only when the receiver answers with a status between 500 and 599, except 504: it resends up to three times, five seconds apart. The tester always answers 200 straight away, so two identical requests here mean the alert fired twice.
What happens to the requests I send?
They are stored only so this page can show them, and deleted with the URL one hour after it was created, or straight away when you press Delete now. Nothing is forwarded to anyone. Use a test message and leave real passwords and API keys out of it.