TradingView strategy → PickMyTrade → Tradovate (prop)

1. Overview — the stack

TradingView’s native Tradovate broker connection is manual click-trading only. It will not auto-execute strategy alerts. Tradovate also does not accept TradingView webhooks directly. PickMyTrade (and similar bridges) receive the webhook, parse JSON, and place orders on Tradovate via their integration.

2. TradingView strategy setup

Strategy vs indicator

• Strategy (strategy()): can call strategy.entry, strategy.exit, strategy.close, strategy.order. Backtests in Strategy Tester. Alerts can fire on order fills (recommended for PickMyTrade automation).
• Indicator (indicator()): uses alertcondition() and/or alert() for signals. You hard-code buy/sell in the alert message (or build dynamic JSON in Pine). No built-in fill emulation.

PickMyTrade supports both. For strategies, their docs say select “Order fills only” so alerts fire when the broker emulator executes an order — not for every custom alert() message.

How strategy alerts work (official TV)

• Creating an alert copies the strategy to TradingView servers; chart edits do not update the running alert — recreate the alert after changes.
• Alerts fire for realtime fills only (not historical bars).
• Rate limit: alert stops if it triggers more than 15 times in 3 minutes.
• Useful placeholders: {{strategy.order.action}}, {{strategy.order.contracts}}, {{strategy.order.price}}, {{strategy.order.alert_message}}, {{strategy.market_position}}, etc.

Webhooks (official TV)

• Alert Notifications → enable Webhook URL → HTTPS POST of the message body.
• Valid JSON → application/json; otherwise text/plain.
• Requires 2FA enabled. Only ports 80/443. No IPv6. Remote must respond within ~3 seconds.
• Paid plan required for webhooks. PickMyTrade docs say Pro / Pro+ / Premium (not free Basic).
• Delivery can fail — check alert log “Webhook status.”

Pine patterns for broker JSON

1. Placeholders in alert dialog — paste PickMyTrade JSON using {{strategy.order.action}} etc. (simplest with PMT’s Generate Alert).
2. alert_message= on orders — attach per-order JSON in Pine; set alert message to {{strategy.order.alert_message}}; trigger = Order fills.
3. alert() at runtime — build JSON string in code; trigger = “Any alert() function call.”
4. alertcondition() — fixed/placeholder messages for indicators (less flexible for dynamic sizing).

3. PickMyTrade connection

What it is: a cloud, no-code bridge that turns TradingView (or manual) signals into broker orders. Marketed heavily for Tradovate futures and prop-firm multi-account copy trading. Claims ~<200 ms processing on their side; 24/7 cloud (no VPS). Not a broker / not a custodian of funds.

Setup steps (from PMT docs / product pages)

1. Create PickMyTrade account; start free trial.
2. Connect Tradovate (demo, live, or prop-issued login). Configure default risk (SL/TP/sizing) in PMT.
3. In PMT: Generate Alert → select account → copy JSON + webhook URL.
4. In TradingView: create alert on strategy/indicator → paste JSON into Message → Notifications → Webhook URL = https://api.pickmytrade.trade/v2/add-trade-data (exact URL from docs; no trailing spaces).
5. For strategies: choose Order fills only.
6. Test on a 1-minute chart / Tradovate demo → verify PMT Alert Log → confirm order in Tradovate → then point at prop account.

Account / API requirements

• TradingView paid plan with webhooks + 2FA.
• Tradovate account credentials (prop firm usually provides these — you connect that login to PMT).
• PMT provides a token and account_id embedded in generated JSON (rotate via their Refresh Token docs if needed).
• Market data subscription on Tradovate may be required for orders (PMT has a “404 / market data” troubleshooting doc).
• One PMT subscription covers unlimited accounts under the same broker login; different logins need additional subscriptions (per PMT FAQ).

Pricing (note conflicting pages)

Common pitfalls (from PMT debugging docs)

• Free TradingView plan → webhook never leaves TV.
• Broken JSON (smart quotes, trailing commas).
• Wrong/stray-space webhook URL; http instead of https.
• Symbol mismatch (TV continuous vs Tradovate front month) — see Risks.
• Strategy alert not set to Order fills only.
• IP pool / “valid IP not found” errors (PMT IP Management docs).
• Missing Tradovate market data subscription.

4. Tradovate + how PMT talks to it

• Tradovate (NinjaTrader Group / Payward ecosystem) is a cloud futures platform and FCM-related brokerage stack used heavily by prop traders.
• Native TV ↔ Tradovate: manual trading from charts; does not run strategies or accept webhooks.
• PickMyTrade path: TV webhook → PMT cloud → PMT’s Tradovate integration places the order. You do not write Tradovate WebAPI yourself for the no-code path.
• Rithmic vs Tradovate: Many props offer both. PMT also supports Rithmic and others. This guide focuses on Tradovate credentials from a prop firm.
• Tradovate Prop: Official directory lists many firms offering Tradovate Prop accounts — you keep one platform UI across firms.
• Demo first: PMT docs explicitly recommend Tradovate demo for testing automation.

5. Futures prop firms using Tradovate

Official Tradovate Prop directory (prop.tradovate.com/find-a-prop-firm, fetched 2026-09-18) lists many firms offering Tradovate Prop, including among others: Apex Trader Funding, Take Profit Trader, Tradeify, TradeDay, Lucid Trading, FundedNext Futures, Top One Futures, Elite Trader Funding, Blue Guardian Futures, AquaFutures, My Funded Futures (listed; page noted “coming soon” style for some), and others.

PickMyTrade marketing names Apex, Lucid, MyFundedFutures, Tradeify, Alpha Futures, Topstep (via Tradovate or ProjectX in some pages), Blue Guardian, FundedNext, etc. Topstep platform status is conflicting across third-party 2026 reviews (some say TopstepX-only / no Tradovate; PMT still lists Topstep). Verify with Topstep directly if that is your firm.

Automation / bot policies (sampled — verify yourself)

6. End-to-end checklist

1. Choose & read the prop firm TOS Confirm Tradovate availability, automation / third-party bridge policy, news rules, flat-by time, drawdown type. Prefer written support confirmation.
2. Accounts & subscriptions TradingView Pro+ (or plan with webhooks) + 2FA. PickMyTrade trial. Tradovate demo for dry run. Prop eval credentials only after policy check.
3. Write / load Pine strategy Prefer non-repainting logic. Use strategy.entry / exit / close. Decide whether exits live in Pine or as PMT SL/TP.
4. Connect Tradovate demo to PickMyTrade Link account, set risk defaults, note token / account_id.
5. Generate alert JSON + webhook in PMT Copy exact webhook URL. Map symbol (prefer explicit front-month or PMT-mapped root like NQ/MNQ).
6. Create TradingView alert Strategy → Order fills only → paste JSON → enable Webhook → create. Do not edit strategy without recreating alert.
7. Paper test Force a quick signal (e.g. 1m chart). Check: TV alert log webhook status → PMT alert log → Tradovate order/fill → position & brackets.
8. Validate symbol, size, SL/TP, timezone Confirm front month, micro vs mini, quantity caps vs prop rules, session times (CME / firm flat times often America/New_York).
9. Only then switch to prop Tradovate login Re-generate alert if account_id changes. Start tiny size. Supervise early sessions (especially if firm bans unattended bots).
10. Ops hygiene Monitor webhook failures, contract rollover (PMT rolls continuous ~4 days before expiry but you must close/roll positions yourself), token refresh, and firm rule updates.

7. Sample alert JSON & Pine snippets

Clearly marked as examples derived from PickMyTrade / TradingView docs. Replace tokens; do not paste secrets into public charts.

{
  "symbol": "NQ",
  "date": "{{timenow}}",
  "data": "{{strategy.order.action}}",
  "quantity": "{{strategy.order.contracts}}",
  "risk_percentage": 0,
  "price": "{{close}}",
  "tp": 0,
  "percentage_tp": 0,
  "dollar_tp": 0,
  "sl": 0,
  "dollar_sl": 0,
  "percentage_sl": 0,
  "trail": 0,
  "trail_stop": 0,
  "trail_trigger": 0,
  "trail_freq": 0,
  "update_tp": false,
  "update_sl": false,
  "breakeven": 0,
  "token": "your_token_here",
  "pyramid": true,
  "reverse_order_close": false,
  "account_id": "your_account_id"
}

https://api.pickmytrade.trade/v2/add-trade-data

//@version=6
strategy("Example EMA cross (demo)", overlay=true, pyramiding=0)

fast = ta.ema(close, 9)
slow = ta.ema(close, 21)
plot(fast, "Fast")
plot(slow, "Slow")

longCond  = ta.crossover(fast, slow)
shortCond = ta.crossunder(fast, slow)

if longCond
    strategy.entry("L", strategy.long)
if shortCond
    strategy.entry("S", strategy.short)

// Optional: attach per-fill JSON and use {{strategy.order.alert_message}}
// strategy.entry("L", strategy.long, alert_message='{"data":"buy","symbol":"MNQ"}')

• Condition: your strategy → Order fills only
• Message: PMT-generated JSON (or {{strategy.order.alert_message}})
• Notifications: Webhook URL = PMT endpoint; enable 2FA on TradingView account

8. Risks & gotchas

• Prop TOS / automation: Account loss and confiscated profits if you violate bot / copy / HFT rules. Vendor “compatible” ≠ firm approval.
• Webhook reliability: TradingView documents that webhooks may fail; monitor alert log. Bridge downtime = missed exits (dangerous without broker-side brackets).
• Latency: TV alert → internet → PMT → Tradovate. PMT claims <200 ms internal processing; end-to-end still depends on TV and market. Not HFT-suitable; some firms ban HFT anyway.
• Partial fills / slippage: Strategy tester ≠ live/sim prop fills. MFFU explicitly bans exploiting sim fill advantages.
• Symbol mapping: Continuous (NQ1!) vs root (NQ) vs dated (NQH2026). PMT advises specifying precise contracts when possible; continuous rollover in PMT (~4 days before expiry) may differ from TV/broker; you must close/roll positions before expiry.
• Micro vs mini: Charting NQ while sizing MNQ (or vice versa) is supported via PMT symbol field — easy to mis-size vs prop contract limits.
• Timezone / sessions: Prop flat times often US/Eastern. Pine timenow / exchange timezone mismatches can fire outside allowed windows.
• Strategy alert freeze: Server copy does not pick up chart edits — recreate alerts after Pine or input changes.
• Rate limits: TV stops alerts at >15 triggers / 3 minutes; Tradovate “Too Many Requests” docs exist on PMT.
• Secrets in webhooks: TV warns not to put passwords in webhook bodies; PMT tokens in alert messages are sensitive — treat like API keys.
• Copy trading across prop accounts: Some firms (e.g. MFFU device/copy rules; Apex per secondary sources) restrict mirroring between accounts or traders — even if PMT can multi-account.

9. Sources & links

Primary pages fetched or searched for this guide (2026-09-18). Prefer primary firm docs over vendor blogs when they conflict.

• TradingView — Strategy Alerts
• TradingView — How to configure webhook alerts
• TradingView Pine — Alerts FAQ (JSON examples)
• PickMyTrade — Configuring TradingView Alerts (updated Sep 8, 2026)
• PickMyTrade — JSON alert configuration
• PickMyTrade — Automating TradingView Strategies
• PickMyTrade — Contract Rollover Rule
• PickMyTrade — TradingView to Tradovate
• PickMyTrade — Pricing
• PickMyTrade — Webhook debugging
• Tradovate — Find a Prop Firm
• My Funded Futures — Fair Play / Prohibited Practices
• TradeDay — Automated, Algo and Bot Trading
• Apex — Prohibited Activities (fetch blocked here; verify in browser)
• PickMyTrade blog — Apex automation rules 2026 (vendor interpretation — not official Apex)
• TradersPost blog — Apex guide / automation caveats