What does your alert actually say?
Paste the message body of your TradingView alert. You get back exactly what the bridge reads from it — the command, the symbol, the volume, the stop and the target — or the precise reason it would be refused. Nothing is sent to a broker, no order is placed, and no account is needed.
What this tool checks
It runs the exact parser our production gateway runs, then stops: it never looks up an account, never touches a quota and never reaches a broker. So a green verdict here means the payload is well formed — it does not mean your account, your symbol mapping or your robot are ready. Those are checked when you send the alert for real.
Sample messages to test
Copy one of these messages into the field above to see how the bridge reads it, then adapt it to your strategy.
{"action":"buy","symbol":"EURUSD","risk":1,"sl":0.2,"tp":0.4,"priceMode":"percent"}
{"action":"buystop","symbol":"EURUSD","price":1.0875,"volume":0.10}
{"action":"closelong","symbol":"USDJPY","tag":"trend"}
buy,EURUSD,risk=1,sl=0.2,tp=0.4,priceMode=percent
The most common refusals
- Unknown or missing command: the action must be buy, sell, closelong… (the full list is in the syntax reference)
- Missing symbol: every command, closes included, must name its instrument
- Unreadable number: volume, risk, sl, tp and price must be valid numbers, with no text or unit
- Malformed JSON: one missing quote or one extra comma is enough to break it
What next?
A message accepted here is well formed. What remains is wiring it up: your account's webhook address in TradingView, the robot in your terminal, and a first alert toward a demo account. Read the TradingView alerts guide.