Connect TradingView Alerts to Nyria

By the end you will have a TradingView Pine Script alert that fires on bar close, posts a JSON payload to your Nyria strategy webhook, and routes a real order to your connected broker.

Prerequisites

• A Nyria strategy with TradingView selected as the alert source. If you don't have one yet, follow the Quick Start first.
• A connected broker. See the per-broker setup pages: Schwab, Tradier, tastytrade, Alpaca, Binance.
• A TradingView plan that allows webhook alerts (Essential tier or higher — the free tier cannot send webhooks).

The webhook URL

Every Nyria strategy exposes one webhook endpoint:

POST https://trades.nyria.io/webhooks/<tokenHash>

<tokenHash> is the unique token shown on your strategy's Integration tab. It looks like s_8f2a91c4b6e0... — copy it exactly. The token is a secret; anyone who has it can send orders to the strategy, so treat it like an API key.

If you ever need to rotate it (suspected leak, employee turnover, etc.), regenerate from the same Integration tab. The old URL stops accepting traffic immediately.

Step 1: Copy the webhook URL from Nyria

Step 2: Write the Pine Script alert message

In TradingView's Pine editor, add an alert() call inside your strategy or indicator. The alert message is what TradingView posts to the webhook URL.

Use a string template literal so TradingView substitutes your runtime values at fire time:

//@version=5
strategy("Nyria SPY Long", overlay=true)

// Replace with your real entry/exit logic.
longCondition  = ta.crossover(ta.sma(close, 9), ta.sma(close, 21))
shortCondition = ta.crossunder(ta.sma(close, 9), ta.sma(close, 21))

if longCondition
    strategy.entry("Long", strategy.long)
if shortCondition
    strategy.close("Long")

// Fire one alert per bar close, with a structured JSON payload.
alertMessage = '{"ticker":"{{ticker}}","action":"{{strategy.order.action}}","sentiment":"{{strategy.market_position}}","price":{{close}},"live_price":{{close}}}'

if barstate.isconfirmed and (longCondition or shortCondition)
    alert(alertMessage, alert.freq_once_per_bar_close)

What each field does once TradingView substitutes the placeholders:

A fired alert turns the above template into a concrete payload like:

{
  "ticker": "SPY",
  "action": "buy",
  "sentiment": "long",
  "price": 542.18,
  "live_price": 542.18
}

Step 3: Add the script to a chart

Step 4: Create the TradingView alert

Step 5: Fire a test alert

You have two options to confirm the wiring without waiting for a real signal:

Option A — Validate inside Nyria. On the strategy's Integration tab, paste your Pine alert template into the Validate box. Nyria substitutes placeholder values and shows exactly how the parser will interpret each field. This catches bad JSON before TradingView ever fires.

Option B — Send a manual cURL. Replace <tokenHash> with your actual token and run:

curl -X POST https://trades.nyria.io/webhooks/<tokenHash> \
  -H "Content-Type: application/json" \
  -d '{
    "ticker": "SPY",
    "action": "buy",
    "sentiment": "long",
    "price": 542.18,
    "live_price": 542.18
  }'

The response should be 200 OK with a JSON body that includes a bot_log_id. The same trade then appears in the strategy's Logs tab within ~1 second.

About Once Per Bar Close

TradingView gives you four trigger frequencies for alerts. Only one of them is safe for automated trading:

Once Per Bar Close is the only setting that guarantees the value of {{close}} is the real bar close, not an intra-bar tick — and the only setting that prevents the same bar from triggering multiple times.

If you use Once Per Bar, you will see orders fire on the open of a bar, then a second alert fire when the same bar's condition flips back, leaving your bot with conflicting fills. There is no Nyria-side filter that can recover from this — fix it at the TradingView trigger setting.

Common pitfalls

1. Duplicate alerts

Symptoms: two webhook hits within a second of each other; the broker shows two opens instead of one.

Causes, in order of frequency:

• The TradingView alert is set to Once Per Bar instead of Once Per Bar Close.
• Two alerts are configured on the same chart for the same strategy (e.g. you cloned an alert and forgot to delete the original). Open Alerts → Manage and confirm exactly one alert per signal exists.
• Your Pine code calls alert() inside a block that runs on every tick. Wrap the call in if barstate.isconfirmed as shown in Step 2.

Nyria automatically deduplicates identical payloads received within a 60-second window. If you legitimately need a second order on the same bar (e.g. scaling in), add an idempotency_key:

{
  "ticker": "SPY",
  "action": "buy",
  "idempotency_key": "scale-in-2"
}

2. Wrong tokenHash

Symptoms: 401 Unauthorized in TradingView's alert log, or 404 Not Found.

Causes:

• The token was copied with a leading/trailing space. Copy the URL using Nyria's copy button rather than a manual highlight.
• The strategy's token was rotated. Open Integration, copy the new URL, and update every TradingView alert that points at this strategy.
• You pasted the strategy's public share URL (which starts with https://app.nyria.io/share/...) instead of the webhook URL. Only the trades.nyria.io/webhooks/... URL accepts POSTs.

3. Market order when you wanted limit, or vice versa

Symptoms: orders fill at a worse price than expected, or orders never fill and time out.

Causes:

• Your strategy is configured for Market orders but the Pine payload sets "order_type": "limit" (the per-alert field overrides the strategy default). Either remove order_type from the payload or change the strategy.
• Your strategy is configured for Limit but the payload omits a price. Without a price, Nyria falls back to the strategy's default offset rules — which may not match your intent. Always send price for limit orders.
• You sent "price": {{close}} on a low-liquidity symbol and the bar close is far from the current quote. Add a slippage buffer in your Pine code, or switch to market for low-liquidity instruments.

4. Repainting strategies

Symptoms: backtest shows 90% win rate; live trading loses money.

The script generated signals that didn't exist in real time. Nyria cannot detect this — it has no view of your Pine code. Read Alert Sources → TradingView Repainting Warning, then verify your script uses barstate.isconfirmed, avoids lookahead=barmerge.lookahead_on, and references close[1] rather than close when pulling higher-timeframe data.

Going from paper to live

What's next

• Convert an Indicator to a Strategy — using an indicator() script? Turn it into a strategy() so one alert covers every side.
• Webhook Payload Reference — every field Nyria accepts in the JSON payload.
• Alert Sources — Discord, Telegram, and other non-TradingView sources.
• Strategies — how Nyria turns a payload into an order using your strategy config.
• Troubleshooting — error codes mapped to fixes if the webhook returns non-2xx.