Alert Sources

Alert sources are where your trading signals originate. Nyria supports multiple alert sources, each with unique setup requirements and capabilities.

TradingView

Automate alerts from your TradingView scripts and indicators.

Setup

1. Create your strategy in Nyria with TradingView as the alert source
2. Complete strategy configuration and validation
3. Copy your webhook URL from the Integration tab
4. In TradingView, create an alert with:
   • Webhook URL: Your Nyria webhook URL
   • Message: Your alert format (validated in Nyria)

Alert Format

TradingView alerts can be simple text:

long entry spy

Or structured JSON:

{
  "action": "open",
  "direction": "long",
  "instrument": "SPY"
}

Or using the default TradingView alert format for backtesting strategies.

TradingView Variables

Use TradingView's built-in variables in your alerts:

• {{ticker}} - Automatically replaced with the instrument
• {{close}} - Current close price
• {{time}} - Alert timestamp

Provide your alert, with variables, to our validation section in your Strategy's Integration tab. Nyria will fill in the variables intelligently and confirm proper handling of each alert type.

Options Strategies

TradingView strategies MUST use Internal Selection for options due to TradingView's limited option data access. Configure your option selection parameters in the strategy settings.

Discord

Automate alerts from Discord servers you manage.

Setup

1. Link your Discord account in Nyria Integrations
2. Invite the Nyria bot to your Discord server
3. Create a strategy with Discord as the alert source
4. Configure Discord settings:
   • Server - Select your Discord server
   • Channel - Which channel to monitor
   • Author (optional) - Filter by specific user
   • Keyword (optional) - Filter messages containing text

Alert Format

Discord alerts are parsed from natural language:

spy long entry

close short btc

SPY 675C buy to open

For options with External Selection, specify strikes:

SPY 675C/676C bull call spread

Expiration Handling

External-selection option strategies can be set to assume the next available expiration, otherwise you must provide it in the alert.

Best Practices

• Use a dedicated alerts channel
• Keep alerts concise and clear
• Include instrument, direction, and action
• For exits, match the language used in entries

TrendSpider

Connect TrendSpider alerts directly to Nyria.

Setup

1. Create strategy with TrendSpider as alert source
2. Copy webhook URL from Integration tab
3. In TrendSpider, configure alert webhook with your URL
4. Format alerts similar to TradingView

Custom API

Send alerts from your own code or trading system via REST API.

Setup

1. Create strategy with Custom as alert source
2. Copy your webhook URL from Integration tab
3. Send POST requests to the webhook URL

API Format

Send JSON payloads:

{
  "instrument": "SPY",
  "action": "OPEN",
  "direction": "LONG",
  "price": "450.50"
}

For options with external selection:

{
  "instrument": "SPY",
  "action": "OPEN",
  "direction": "LONG",
  "legs": [
    {
      "strike": 675,
      "side": "CALL",
      "expiration": "2025-11-17",
      "action": "buy_to_open"
    }
  ]
}

Authentication

Webhook URLs include a unique token hash for security. Keep your webhook URL private.

Rate Limiting

Custom API endpoints have rate limiting to prevent abuse. Contact support if you need higher limits.

Broker Orders (Coming Soon)

Create strategies from orders placed in your broker account, allowing other users to copy your manual trades automatically.

Alert Validation

Regardless of source, all strategies require alert validation:

1. Provide example alerts for each enabled trade type
2. System validates parsing and execution logic
3. Simulates full trade lifecycle
4. Strategy activates once validation passes

What Gets Validated

• Alert parsing extracts correct instrument, action, direction
• Option selection finds valid contracts (for options)
• Limit order pricing calculates correctly
• Exit alerts match entry positions
• All required fields are present

Common Validation Issues

"Could not parse instrument"

• Ensure instrument name is clear (SPY, BTC, etc.)
• Check spelling and formatting

"No option contracts found"

• Strike may be invalid or unavailable
• Check DTE range includes available expirations
• Verify delta/price targets are reasonable

"Price required for limit order"

• Strategy configured for alert-specified price
• Include price in your alert

"Multiple pairs selected"

• For crypto with both USDT/USDC pairs
• Specify exact pair in alert (BTCUSDT not just BTC)

Signal Source Comparison

Next Steps

• Create Your First Strategy
• Configure Trading Behavior
• Validate Alerts