Nyria Docs — Automate any alert on any broker

Key terms and definitions used throughout Nyria — platform concepts, data-model entities, and trading terminology, with cross-links to where each term is used.

Key terms used throughout Nyria's platform and documentation. The "Where it's used" links jump to the docs page that shows the term in context.

Nyria-specific terms

These are the names Nyria uses for the entities in its data model and product. Most of these terms also appear in the codebase, so they're the right vocabulary to use in a bug report or support ticket.

tokenHash

The secret token embedded in a strategy's webhook URL. It is the only piece of authentication on the public webhook endpoint, so it must be treated like an API key.

A tokenHash looks like s_8f2a91c4b6e0... (strategy webhook) or wh_... (legacy share/webhook tokens) and is stored as a SHA-256 hash server-side — Nyria never stores the raw token.
Each strategy has exactly one active webhook tokenHash; rotating it invalidates every alert source that was sending to the old URL.
Anyone who has the URL can fire orders into your strategy. If you suspect it leaked, rotate it from the strategy's Integration tab.

Where it's used: Custom webhook setup, TradingView setup, Build your first strategy, Alert sources overview, Webhook payload reference.

broker_authorization

A single user's OAuth or API-key authorization with one broker — i.e., the token bundle that lets Nyria call that broker on the user's behalf. In the codebase this is the user_broker_authorizations table.

One row per (user, broker, account_type) — so a user with both paper and live Tradier connections has two separate authorizations.
Holds access_token / refresh_token / expires_at for OAuth brokers (Schwab, Tradier, tastytrade) and a credentials JSON blob for API-key brokers (Alpaca, Binance, Binance US).
Status flips to Reauth Required when tokens expire and Nyria can't refresh them silently — visible on the Integrations page.

Where it's used: Integrations overview, individual broker setup pages (e.g. Schwab, tastytrade, Alpaca, Coinbase).

broker_account

A specific brokerage account that hangs off a broker_authorization. Backed by the user_broker_accounts table.

A single Schwab or tastytrade authorization can expose multiple accounts (e.g. IRA + individual + joint). Each is its own broker_account row with its own account_number.
Bots reference a broker_account — never a broker_authorization directly — so swapping which account a bot trades into is independent of the OAuth connection.
Disconnecting the parent authorization cascades to every broker_account under it.

Where it's used: Integrations overview, Bots, broker setup pages where multi-account selection is documented (e.g. Schwab setup, tastytrade setup).

strategy

The blueprint that defines how alerts are processed and what trading rules to apply. Strategies do not execute trades by themselves — bots do.

A strategy includes:

Alert source — where signals come from (TradingView, Discord, custom webhook; Telegram coming soon)
Equity type — what asset class (stocks, options, crypto spot, crypto perps; equity futures coming soon)
Trading behavior — how entries and exits map to broker orders
Allowed instruments — which tickers can be traded
Visibility — public, private, or paywalled (sold via Whop / Stripe)
Validation alerts — example alerts used to prove parsing works before the strategy can be deployed

Where it's used: Strategies overview, Build your first strategy, Trading behavior, Multi-leg options strategies, Crypto perpetuals strategies.

bot

Your personal trading instance that copies a strategy and routes its orders into one of your broker_accounts.

A bot includes:

The broker_account it trades into
Position sizing (fixed dollars, % of buying power, or per-strategy override)
A subset of the strategy's allowed instruments
Overrides (e.g. force market orders, paper-only, pause)

You can deploy multiple bots from the same strategy with different broker accounts and different sizing.

Where it's used: Bots, Build your first strategy, FAQ, Trading behavior.

strategy_entitlement

A grant that says "this user is allowed to deploy a bot from this paywalled strategy." Backed by the strategy_entitlements table. This is how Nyria enforces paid-strategy access.

One entitlement per (strategy, provider_integration, provider_entitlement_id) — e.g. one Whop pass, one Stripe subscription, one manual grant.
Status is active, inactive, revoked, expired, or pending. When a Whop or Stripe webhook signals a cancellation, the entitlement flips to revoked and the user's bot on that strategy is paused.
Linked to a strategy_product row when the access came from a specific paid SKU (e.g. a Whop pass tier).

Where it's used: Whop customer access, Integrations overview (Whop / Stripe seller sections), Strategies — visibility & monetization.

provider_integration

A creator's connection to a monetization provider — i.e., the OAuth/API-key bundle that lets Nyria read entitlement events from Whop, Stripe, or a manual provider. Backed by the provider_integrations table.

Distinct from a broker_authorization: broker_authorization routes trade execution, provider_integration routes paid-access grants.
Each row stores the provider type, the creator's external account id, an optional API key, a webhook secret, and a webhook endpoint id — so Nyria can both receive and verify incoming entitlement webhooks.
A creator can have multiple provider_integrations (e.g. one Whop, one Stripe) and route different strategies through different providers.

Where it's used: Integrations overview — third-party / sellers, Whop seller and Stripe seller onboarding flows referenced from there.

alert source

The upstream service that sends signals into Nyria. Configured per strategy as one of: TradingView, Discord, or a generic custom webhook (Telegram and TrendSpider are coming soon). The alert_sources table catalogs the supported sources and their status (active, coming_soon, beta, inactive).

The alert source determines parsing rules: a TradingView text alert is read differently from a Discord channel message.
Nyria cannot verify the accuracy or timeliness of an alert source — see Known limitations for the latency table.

Where it's used: Alert sources overview, per-source guides under Alerts, Alerts → Discord, Alerts → Telegram, Alerts → TrendSpider, Alerts → Custom webhook.

signal source

Synonym for alert source when discussing the originating trading idea. "Signal source" emphasizes the who/what produced the trade idea (a Pine strategy, a Discord call-out group, a TrendSpider scan); "alert source" emphasizes the transport mechanism (TradingView webhooks, Discord bot, Telegram bot).

Used interchangeably in the docs and product UI — when in doubt, treat them as the same concept.

Where it's used: Alert sources overview, Risk disclosure, and the beta_signup form, which asks new users which signal sources they plan to wire up.

paper

A simulated trading environment where orders are filled against a fake balance. Nyria models "paper" two ways:

Nyria Paper — Nyria's built-in paper broker. Always available, no broker connection required, fills against live market data.
Broker paper / sandbox — Some brokers (Alpaca, Tradier) expose their own paper API. Selected at broker-connection time by choosing Paper as the account_type on a broker_authorization. Schwab, tastytrade, and Binance are live-only at the broker — use Nyria Paper there.

Always validate a new strategy on paper before flipping a bot to live.

Where it's used: Quick start, FAQ, Integrations overview — account types, each broker setup page (e.g. Tradier setup, Alpaca setup).

live

Real-money trading against a real brokerage account. The opposite of paper. On a broker_authorization, this is account_type = 'live'.

Going live is a deliberate switch: a bot on a paper broker_account will not migrate automatically to a live broker_account — you create a new bot (or repoint the existing one) on the live account.

Where it's used: Quick start, Integrations overview, Risk disclosure, every broker setup page.

multi-leg

An options order made up of more than one contract submitted as a single combo order, so all legs fill atomically (or none do). Nyria supports up to 4 legs on Schwab, Tradier, and Alpaca, and up to 10 legs on tastytrade.

Common multi-leg structures:

Vertical spread (2 legs) — same expiration, different strikes
Calendar / diagonal (2 legs) — different expirations
Iron condor / iron butterfly (4 legs) — two vertical spreads, one on each side

Multi-leg orders are defined in the alert payload as a legs array — see the Webhook payload reference for the schema.

Where it's used: Multi-leg options strategies, Webhook payload reference, Migrate from TradersPost, Equity types, each options-capable broker setup page (e.g. Schwab setup, tastytrade setup, Tradier setup).

OCC

The standardized 21-character option symbol format defined by the Options Clearing Corporation. Example: SPY260619C00500000 = SPY, expires 2026-06-19, Call, strike $500.000.

Format: <ROOT padded to 6><YY><MM><DD><C|P><strike × 1000 padded to 8>.

Nyria formats OCC symbols correctly for each broker automatically — Schwab requires specific spacing, tastytrade pads to exactly 21 characters. You never need to type a raw OCC symbol; supply ticker + expiration + strike + side and Nyria builds it.

Where it's used: Webhook payload reference, Alerts → Telegram, Migrate from TradersPost, Schwab setup, Tradier, tastytrade setup, Alpaca setup.

magic-link

A one-click sign-in email Nyria can send instead of a password prompt. Powered by Better-Auth's magic-link plugin: the user enters their email, receives a short-lived signed URL, and clicking it logs them in and lands them at the configured ?from= deep-link target.

Useful for users who signed up via the lander's broker-modal deep-link, since they may never have set a password.
Tokens expire and are single-use.

This is currently a sign-in mechanism only — the magic-link sign-in flow lives in the app, not in the public docs.

Where it's used: Not documented as a standalone page yet. Surfaced on the in-app /login screen and from deep-links described in the internal deep-link conventions (the ?from= and ?mode=signup params).

beta_signup

A row in the beta_signups table created when a prospective user submits the lander's early-access form. Stores name, email, the signal sources they plan to use, equity types, brokers (plus a free-text "other brokers"), and a status of pending, approved, or rejected.

Not a Nyria account by itself — approving a beta_signup is a separate admin step that invites the email to create a real account.
The captured signal_sources / equity_types / brokers arrays feed launch-readiness prioritization (which alert sources and brokers the waitlist actually wants).

Where it's used: Not documented in the public docs (it's an admin/lander concept). Listed here for clarity for users who see the term in marketing copy or support replies.

Trading terms

Entry

Opening a new position by buying or selling an instrument.

Long entry — buying with the expectation price will rise
Short entry — selling/shorting with the expectation price will fall

Exit

Closing an existing position.

Long exit — selling to close a long position
Short exit — buying to close a short position (cover)

Position size

The dollar amount or quantity allocated to each trade. Configured on the bot, not the strategy.

Fixed amount — e.g. $500 per trade
Percentage — e.g. 5% of account buying power
Strategy override — strategy author specifies sizing on every alert

Allocation

The maximum dollar amount deployed per entry signal across your bots.

Example: If your allocation is $20,000, Nyria will deploy at most $20,000 across all bots that fire on the same alert.

Allocation is not your account size — it's the per-signal ceiling.

Webhook

A URL endpoint that receives alerts from an external service. For Nyria, each strategy's webhook URL ends in its tokenHash.

Market order

An order that executes immediately at the best available price.

Limit order

An order that only executes at your specified price or better.

Slippage

The difference between expected price and actual fill price. Driven by volatility, low liquidity, large order size, and latency between signal and broker.

Options terms

Internal selection

Nyria picks the option contract for you based on rules in the strategy (delta target, DTE window, strike offset). Required for TradingView strategies because TradingView has no native option-chain access.

External selection

The alert explicitly specifies strike, expiration, and option type (call/put). Required for legs[] payloads where you want exact contract control.

Delta

How much an option's price moves per $1 move in the underlying. ≈0.50 at-the-money, lower out-of-the-money, higher in-the-money.

DTE

Days to expiration. 0 DTE expires today; 45 DTE expires in about six weeks.

Spread

A multi-contract structure. See multi-leg.

Leg

A single option contract within a multi-leg spread.

Strike price

The price at which an option may be exercised. ITM / ATM / OTM describe its position relative to spot.

BTO / STO / BTC / STC

Acronym	Meaning	Use
BTO	Buy To Open	Enter long position
STO	Sell To Open	Enter short position (write)
BTC	Buy To Close	Exit short position
STC	Sell To Close	Exit long position

Crypto terms

Spot trading

Buying or selling the actual cryptocurrency for immediate settlement.

Perpetual futures (perps)

Derivative contracts tracking spot price with no expiration. Use leverage, charge funding rates, and can be liquidated.

Funding rate

Periodic payment exchanged between long and short perp holders (typically every 8 hours). Positive = longs pay shorts.

Leverage

Borrowed capital amplifying exposure. 5x on $1,000 = $5,000 of exposure.

Leverage amplifies losses as well as gains. A 20% adverse move at 5x = 100% loss (liquidation).

Liquidation

Forced closure of a leveraged position when margin is depleted.

Strategy configuration

Enter direction

Open a position in the signal's direction.

Exit opposite

Close the opposite-side position before opening a new one — useful for flip-style strategies that don't emit explicit exits.

Do nothing

Ignore alerts on this direction.

Pyramiding

Allow multiple entries to accumulate a larger position. Disabled means one position at a time.

Alert-source terms

TradingView variables

Variable	Replaced with
`{{ticker}}`	Instrument symbol
`{{close}}`	Current close price
`{{time}}`	Alert timestamp
`{{interval}}`	Timeframe

Quick start guide — get started with Nyria
Build your first strategy — end-to-end walkthrough
Integrations — connect brokers and monetization providers
Webhook payload reference — every field Nyria accepts
Known limitations — important platform limitations
FAQ — common questions
Troubleshooting — solve common issues

Glossary

On this page