Alert syntax

Alert syntax is the exact text format a signal source uses to describe a trade, for example the JSON message a TradingView alert sends to a webhook or the keyword pattern a Telegram channel follows; the receiving platform parses that syntax into symbol, direction, entry, stop-loss and take-profit.

Why it matters

Automation only works if the sender and the receiver agree on the format. TradingView lets you write any message you like and fills placeholders such as the ticker and the close price at alert time; if the message does not say which direction to trade, or uses a field name the receiver does not know, the alert arrives and nothing happens. The default TradingView text ("BTCUSDT Crossing 60000") carries no direction at all. On Telegram there is no standard, so the syntax is whatever the channel habitually writes, and small changes in that habit can break parsing.

How AlgoVesta handles it

For TradingView, AlgoVesta gives you a ready JSON template per strategy with the placeholders already in place: symbol from the ticker, side, an entry hint from the close price, and optional stop-loss and take-profit from plots or fixed values. The template is generated in the dashboard and can be copied into the alert's message box unchanged. Fields you do not send fall back to the bot's own rules, such as a fixed stop in percent. Alerts whose text cannot be parsed into a direction are recorded as rejected with the reason rather than guessed. For Telegram, the parser recognises the common keyword layouts, emoji markers, target lists and stop notations, and every channel can be tested in paper mode to see message by message what was extracted. Documentation is on the TradingView bot page and in the webhook setup guide.

Example

A TradingView strategy is configured with the message {"symbol":"{{ticker}}","side":"{{strategy.order.action}}","price":{{close}},"stop_loss":{{plot_0}},"take_profit":{{plot_1}},"market_position":"{{strategy.market_position}}"}. When a long entry fires on ETHUSDT, TradingView sends the filled-in JSON to the strategy's webhook URL; AlgoVesta reads side "buy", the entry hint and the two plot values, and opens the position with those levels. A second alert with the default text "ETHUSDT Crossing 3100" is rejected as having no direction.

Common mistakes

• Leaving TradingView's default alert text in place.
• Using strategy.order.action alone for exits, so a "sell" that should close a long opens a short; include the position state or use the platform's exit handling.
• Editing the JSON by hand and breaking a quote or a comma, which makes the whole message unparsable.
• Creating the alert on a different chart than the symbol it is meant to trade, so the ticker placeholder fills in the wrong symbol.