Nyria Docs

Migrate from TradersPost

Move your TradingView, Discord, and broker setup from TradersPost to Nyria in 10 minutes. Your existing alerts work as-is — no template rewrites.

This guide moves your live setup from TradersPost to Nyria without rewriting any TradingView alerts or broker permissions. Most users finish in under 15 minutes.

What's different about Nyria: unlimited bots, no per-bot tier caps, no required JSON template, true multi-leg options on Schwab/ tastytrade/Tradier/Alpaca, and allocation-based pricing ($100 per $10k of max entry size — flat, regardless of bot count).

Before you start

You'll need:

  • Your existing TradersPost broker connections (Schwab, tastytrade, Tradier, Alpaca, Binance) — you'll re-authorize them on Nyria
  • Your TradingView alert messages (or Discord channel)
  • Your strategy logic (what fires entry, what fires exit)

Don't disconnect TradersPost yet. Run both side-by-side on paper trading first.

Step 1 — Sign up for Nyria

Go to app.nyria.io and create an account. Free tier includes unlimited paper trading. No credit card required.

Step 2 — Connect your broker

Pick the same broker you used on TradersPost.

BrokerAuth methodSetup time
Charles SchwabOAuth2 min
tastytradeOAuth2 min
TradierAPI key1 min
AlpacaAPI key1 min
BinanceAPI key2 min

Nyria connects via the same official OAuth or API key as TradersPost. Your funds and credentials stay at the broker. Nyria stores only the access token, never the broker username/password, and never has withdraw permissions.

Step 3 — Map your TradersPost strategy to Nyria

TradersPost uses two concepts (Strategy + Subscription) to Nyria's two concepts (Strategy + Bot):

TradersPostNyriaNotes
StrategyStrategySame thing — your trade logic
SubscriptionBotA strategy deployed to an account with size + filters
Broker connectionIntegrationSame
Webhook URLWebhook URLEach Nyria strategy has one
Position-sizing ruleBot configPer-bot setting

Quick mapping

  1. Create a Nyria Strategy with the same name as your TradersPost Strategy.
  2. Set the alert source (TradingView / Discord / Custom webhook).
  3. Configure entry, exit, and (if options) legs — same logic you used in TradersPost.
  4. Deploy a Bot to the broker integration you connected in Step 2.
  5. Copy the Nyria webhook URL from the strategy's Integration tab.

Step 4 — Replace the webhook URL in your alert source

Your existing alert message works as-is — no rewrites required.

TradingView

  1. Open the alert in TradingView (Alt+A from the chart)
  2. Replace the TradersPost webhook URL with the Nyria URL
  3. Leave the message body unchanged
  4. Save

Nyria parses any reasonable text or JSON format:

long entry SPY
{
  "ticker": "{{ticker}}",
  "action": "{{strategy.order.action}}",
  "sentiment": "{{strategy.market_position}}"
}
BUY 1 SPY 6/19 $500 CALL @ 1.50

All three of the above will parse correctly. You don't have to pick one of Nyria's templates because there are none.

Discord

If you were using a third-party Discord→webhook forwarder for TradersPost, you can drop it. Nyria has native Discord:

  1. Invite the Nyria bot to your Discord server
  2. Pick the channel in the Nyria UI
  3. Send a test message

Telegram

Coming soon — until Telegram ships, route those alerts via TradingView, Discord, or your strategy's custom webhook URL.

Step 5 — Validate alerts

In your Nyria strategy:

  1. Go to Integration tab
  2. Click Validate Alerts
  3. Paste two example alerts: one entry, one exit
  4. Click Validate

Nyria parses both and shows what it understood (instrument, side, size, option legs if any). Adjust and re-validate until it's right.

Step 6 — Paper trade for a week

This is the most important step. Deploy your bot to the Nyria Paper integration first.

  • Same alerts, same strategy logic, simulated fills
  • Compare against TradersPost's behavior in parallel
  • Confirm position lifecycle: entry, exit, no-position scenarios

When you're happy, switch the bot's integration to the live broker.

Step 7 — What about multi-leg spreads?

If you ran single-leg options on TradersPost (which is all they support), Nyria handles that the same way — except you can now also build multi-leg spreads.

Vertical spread example

In the Nyria strategy editor:

  • Leg 1: BUY · CALL · Delta 0.30 · DTE 7–45
  • Leg 2: SELL · CALL · Delta 0.20 · DTE 7–45 (same expiration)

One alert fires both legs as a single multi-leg order at Schwab, tastytrade, Tradier, or Alpaca.

SPX iron condor example

  • Leg 1: BUY · PUT · Strikes-away -10 (long protective)
  • Leg 2: SELL · PUT · Delta 0.16 (short put)
  • Leg 3: SELL · CALL · Delta 0.16 (short call)
  • Leg 4: BUY · CALL · Strikes-away +10 (long protective)

Nyria automatically rewrites SPX to SPXW before order placement (PM-settled root) — you don't have to handle that in Pine Script.

Step 8 — Cancel TradersPost (when you're ready)

After 5–10 successful Nyria trades and no surprises, cancel your TradersPost subscription. No "migration fee" or porting step on our side — once your webhook URL points at Nyria, you're done.

Pricing comparison

TradersPost ProNyria Pro
Monthly cost$84.15/mo (annual)$100/mo per $10k max entry
Bot countTier-gatedUnlimited
Asset classesTier-gatedAll included
Multi-leg optionsSingle-leg onlyUp to 4 legs (10 on tastytrade)
SchwabWaitlistLive
Annual billing15% offCancel anytime

At one bot with $10k max entry size, Nyria costs ~$16/mo more than TradersPost Pro. At three bots across stocks + options + crypto, Nyria is cheaper AND supports the spreads TradersPost can't.

Troubleshooting common migration issues

"My alert validates on Nyria but the order isn't firing"

Check:

  • Bot is Active (not paused)
  • Broker integration is Connected (not Reauth required)
  • Strategy is Active
  • The alert's instrument matches the bot's selected instruments

"My TradersPost JSON template is rejected on Nyria"

It's not rejected — Nyria parses any format. If you want, send the exact JSON you used on TradersPost. Nyria will read ticker, action, etc. and infer the rest from your strategy config.

"Multi-leg orders are failing"

The OCC option symbol must be correct on each leg. If you're using TradingView Pine variables, ensure your Pine code outputs full OCC strings (or use Nyria's internal selection by delta/DTE/strike).

"Schwab won't connect"

Schwab OAuth requires you to authorize Nyria via Schwab's portal. Click Connect Schwab in Nyria's Integrations page and follow the Schwab redirect. If you have a corporate Schwab account, your admin may need to approve third-party apps.

What's next?