Glossary
Plain definitions of Nyria terms, such as strategy, bot, broker connection, webhook token and total entry allocation, each linked to the pages that use it.
This glossary explains, in a sentence or two each, the words Nyria uses in the app and the trading, options and crypto words around them, with links to the pages where each one matters.
Nyria terms
Webhook token
The secret at the end of a strategy's webhook URL. Its field name is tokenHash. Anyone with it can send alerts to the strategy. If it leaks, rotate it on the strategy's Integration tab: the old URL stops working at once.
Where it's used: Custom webhook setup, TradingView setup, Your first strategy, Alert sources, Webhook reference.
Broker connection
Your sign-in (OAuth) or API key at one broker, which lets Nyria call that broker for you.
- One connection per broker per account type, so a paper and a live Tradier connection are two connections.
- Schwab, Tradier (live) and tastytrade connect by signing in at the broker. Tradier (paper) and Alpaca connect with credentials you paste.
- The status changes to Disconnected when Nyria can no longer use the connection: an expired sign-in, credentials the broker refused, or a failed refresh. The Integrations page shows it, with a Reconnect button.
Where it's used: Integrations and the broker setup pages (for example Schwab, Tradier, tastytrade, Alpaca).
Brokerage account
One account at your broker, under a broker connection.
- One Schwab or tastytrade connection can hold several accounts (for example IRA, individual and joint). Each is its own brokerage account with its own account number.
- A bot trades one brokerage account.
- Removing the last account on a connection removes the connection too.
Where it's used: Integrations, Bots, and the broker setup pages that cover picking an account (for example Schwab setup, tastytrade setup).
Strategy
The rules for how alerts are read and traded. Bots place the trades.
A strategy includes:
- Alert source: where alerts come from (TradingView, Discord, Telegram, TrendSpider or a custom webhook)
- Asset type: Stocks, Options or Crypto
- Market type: for Crypto, Spot or Futures (crypto perpetuals, simulated on Nyria Paper)
- Trading behavior: how entries and exits map to broker orders
- Tickers: which tickers can be traded
- Who can copy it: Public, Premium (sold through Nyria, Whop or Stripe) or Private
- Alert format: example alerts, checked before bots can be deployed
Where it's used: Strategies, Your first strategy, Trading behavior, Multi-leg options strategies, Crypto perpetuals.
Bot
A bot places a strategy's trades in one of your broker accounts, at your budget per entry.
A bot includes:
- The brokerage account it trades
- A budget per entry, or an exact number of shares or contracts where the strategy allows it
- Some or all of the strategy's tickers
- One override, Force market orders, and its own Active or Paused status
You can deploy several bots from the same strategy with different broker accounts and sizing.
Where it's used: Bots, Your first strategy, FAQ, Trading behavior.
Paid access
A grant that lets one person deploy bots on one Premium strategy.
- One grant per strategy per purchase: one plan bought through Nyria, one Whop pass, one Stripe subscription, or one manual grant.
- Access can be active, paused, revoked or expired. When the subscription ends, access is revoked and the person's bots on that strategy move to Closing only. Exits still run, and new entries do not.
- Tied to the paid tier it came from, such as a Whop pass tier.
Where it's used: Whop for customers, Integrations, Strategies.
Payment provider
A creator's connection to Whop or Stripe, which Nyria reads to grant and revoke paid access.
- A creator can have several payment providers (for example one Whop and one Stripe) and sell different strategies through each.
- Selling through Nyria needs no payment provider: Nyria takes the payments and pays the creator out through Stripe.
Where it's used: Integrations (seller sections), and the Whop and Stripe seller guides linked from there.
Alert source
The service that sends alerts to Nyria. Each strategy has one: TradingView, Discord, Telegram, TrendSpider, or a custom webhook.
- The alert source sets how alerts are read. A TradingView text alert is read differently from a Discord channel message.
- Known limitations lists each source's delays.
Where it's used: Alert sources, and the guides for TradingView, Discord, Telegram, TrendSpider and custom webhooks.
Paper
Simulated trading: orders fill against a simulated balance, and no real money moves. Nyria has two kinds:
- Nyria Paper: Nyria's built-in paper broker, simulated end to end. A market order fills at the ask to buy and the bid to sell. Nyria Paper says when a limit order fills.
- Broker paper or sandbox: Tradier and Alpaca have their own paper API. Select the broker's card, then Connect paper account. Schwab and tastytrade are live-only on Nyria, so use Nyria Paper for them.
Where it's used: Paper trading, Quick start, FAQ, Integrations, and each broker setup page (for example Tradier setup, Alpaca setup).
Live
Real-money trading against a real brokerage account. The opposite of paper.
A bot on a paper account doesn't move to a live one by itself. Deploy a new bot on the live account, or edit the bot and pick it.
Where it's used: Quick start, Integrations, Risk disclosure, every broker setup page.
Multi-leg
An options order with more than one contract, sent to the broker as one order. Nyria supports up to 4 legs on every broker that takes multi-leg orders.
Common multi-leg structures:
- Vertical spread (2 legs): same expiration, different strikes
- Iron condor / iron butterfly (4 legs): two vertical spreads, one on each side
Every leg in a Nyria spread shares one expiration and one quantity. Structures across two expirations are not supported.
On most strategies the legs come from the strategy's leg rules. Only a strategy with Contract selection: Provided in alert reads them from the alert, as a legs array. See the webhook reference for the schema.
Where it's used: Multi-leg options strategies, Webhook payload reference, Migrate from TradersPost, What you can trade, each options-capable broker setup page (for example Schwab setup, Tradier setup, tastytrade setup).
OCC
The standardized option symbol format defined by the Options Clearing Corporation. Example: SPY271217C00780000 = SPY, expires Dec 17, 2027, call, strike $780.
Format: <ROOT><YY><MM><DD><C|P><strike × 1000 padded to 8>. The full 21-character form pads the root to 6 characters with spaces.
You never type one: give the ticker, expiration, strike and side, and Nyria builds it.
Where it's used: Webhook payload reference, Migrate from TradersPost, Schwab setup, Tradier, tastytrade setup, Alpaca setup.
Trading terms
Budget per entry
The most one entry spends, set on the bot.
- Dollar budget: for example $500 per entry
- Number of shares (or contracts, or coins), on strategies that enable it
Total entry allocation
Your total entry allocation is every live bot's budget per entry, added up. It's the most your live bots could put in at once.
Two live bots at $4,000 and $6,000 per entry make $10,000, which is the $100 tier. At $6,000 each they make $12,000, which moves you to the $20,000 tier at $200 a month.
Bots on Premium strategies from creators count toward their set pricing tier instead.
Nyria Pro is priced on it, and it has to fit inside your plan. It isn't money Nyria holds. See pricing and limits.
Webhook
An address that another service sends data to. Each Nyria strategy has a webhook URL that ends in its webhook token.
Options terms
From my rules
With Contract selection set to this, Nyria picks the option contract from the strategy's rules (delta target, DTE window, strike offset). TradingView options strategies always use it.
Provided in alert
With Contract selection set to this, the alert names the strike, option type (call or put) and expiration. A Discord or Telegram entry with no date takes the nearest listed expiration. Webhook alerts send the contracts as a legs array.
DTE
Days to expiry, counted in trading days. 0 DTE expires today; 30 DTE is about 6 weeks out. A Nyria strategy accepts a DTE range from 0 to 31.
Spread
An options position of more than one contract, traded as one order. See multi-leg.
Leg
A single option contract within a multi-leg spread.
Crypto terms
Perpetual futures (perps)
Futures contracts that track a coin's spot price and never expire. A position uses leverage, pays or receives funding, and can be liquidated.
Funding rate
A payment between the long and short holders of a perpetual, usually every 8 hours. When the rate is positive, longs pay shorts. When it's negative, shorts pay longs.
Leverage
Borrowed money that lets a position be larger than the margin backing it: $1,000 of exposure at 5x needs $200 of margin. In Nyria the bot's budget is the exposure, so leverage changes the margin, not the position.
Leverage multiplies losses as well as gains. A 20% move against you at 5x is a 100% loss (liquidation).
Liquidation
The exchange closing a leveraged position because its margin has run out.
Strategy configuration
Enter position
Opens a position in the alert's direction.
Exit long position / Exit short position
Closes the other side's position. This side never opens a position of its own, and the other side's Close on exit alerts has to be on. Use it when one side's alert is your exit for the other.
Do nothing
Ignores entry alerts for this direction.
Pyramiding
Adding to an open position with further entries. Turn on Allow multiple entries on the strategy to allow it. With it off, the strategy holds one position at a time.
Alert-source terms
TradingView variables
| Variable | Replaced with |
|---|---|
{{ticker}} | The chart's ticker |
{{close}} | Current close price |
{{time}} | Alert timestamp |
{{interval}} | Timeframe |
Repainting
An indicator or strategy that shows different entries and exits on past bars than it fired live. A repainting strategy can look profitable in a backtest and lose money live.
Webhook URL
A strategy's own address for receiving alerts. It ends in the strategy's webhook token.
Log and status terms
Each log row carries one of six badges, plus the raw log line.
Sent
On a strategy log, the alert went out as an order from at least one bot.
Placed
On a bot log, the broker, or Nyria Paper, accepted the order. Placed isn't filled. The row has the broker order id and the quantity and price.
Logged
Anything else that happened, described in the row.
Skipped
Nothing was bought or sold, and nothing is wrong, for example an exit with no position to close.
Needs attention
Something is left for you, such as a position whose exit failed.
Failed
Processing stopped for that alert or bot, for example not enough buying power or a broker rejection.
Disconnected
Your broker connection needs reconnecting because Nyria could not refresh or use it. Bots on it place no orders, exits included, until you select Reconnect on the Integrations page.
Related
- Quick start: get started with Nyria
- Your first strategy: an end-to-end walkthrough
- Paper trading: what a simulated fill does and does not prove
- Pricing and limits: every price and cap in one place
- Integrations: connect brokers, Whop and Stripe
- Webhook reference: every field Nyria accepts
- When an order fails: how to recover
- Known limitations: what Nyria does not do
- FAQ: common questions
- Troubleshooting: common problems and fixes