Route futures alerts to NinjaTrader

NinjaTrader is the futures execution path. Install the local bridge, paste its webhook URL on Connections, and optionally enable a cloud inbound webhook for TradingView or custom bots.

NinjaTrader

Local bridge, not OAuth

NinjaTrader does not offer a cloud OAuth flow like Schwab. Trade Desky stores your forward_url — the public URL of your trade-desky-ninjatrader receiver (for example a Cloudflare tunnel). The receiver requires HTTPS when cloud-hosted trade-receiver must reach your PC. Orders ping that URL when futures are the target.

Diagram: desktop watcher or inbound webhook to trade-receiver, tunnel, local tray receiver, NinjaTrader 8
Alerts enter Trade Desky cloud, then forward to your local bridge and NinjaTrader 8.

Quick setup (Sim101 first)

  1. Download the bridge

    Get Trade Desky NinjaTrader via the Windows installer on the download page (or portable ZIP). Copy add-ons into Documents\NinjaTrader 8\bin\Custom\AddOns\, compile, and open the Trade Desky panel. Select Sim101 and click Start Listener.

    NinjaTrader Add-On panel mock showing Sim101 selected, Start Listener, and live trading off
    Start on Sim101 with live trading unchecked until tests pass.

  2. Run the webhook receiver

    Launch Webhook Receiver from the Start Menu (or WebhookReceiver.exe). It lives in the Windows system tray — no CMD window. Right-click for status, logs, or quit. Note the local webhook URL (default http://127.0.0.1:5088/webhook). Keep dry_run: true until Sim101 fills look correct.

    System tray receiver status showing listening URL and dry_run reminder
    Receiver listens in the system tray; use Open logs from the menu if you need details.

  3. Expose HTTPS when cloud must reach your PC

    Use Cloudflare Tunnel or ngrok when trade-receiver runs remotely and must POST to your Windows machine. Same-machine local dev can target http://127.0.0.1:5088/webhook without a tunnel.

    Diagram showing Trade Desky cloud connecting through a tunnel to local receiver
    Tunnel required for remote cloud → local PC; optional for all-local testing.

  4. Connect on Trade Desky

    Subscribe on Pricing, open Connections, paste your HTTPS forward URL, optionally add the bridge secret and account label, then run Test.

    Mock of Trade Desky Connections page with NinjaTrader forward URL and inbound webhook URL
    Forward URL is the bridge endpoint; inbound webhook is separate for TradingView or bots.

Full walkthrough with go-live checklist: NinjaTrader setup guide.

Inbound JSON webhook

Separate from the NT bridge URL: Trade Desky can issue a cloud webhook URL. External systems POST JSON to that endpoint. Parsed futures route to NinjaTrader when it is connected and set as default. Options still go to Tradier or Schwab when those are connected.

NinjaTrader FAQ
  • Does NinjaTrader use OAuth in Trade Desky? No. You run the trade-desky-ninjatrader bridge on your machine and paste its webhook URL into Connections. Account selection happens inside NinjaTrader.
  • Can I route futures alerts to NinjaTrader? Yes. When NinjaTrader is connected and set as default, parsed futures intents from desktop alerts or your inbound JSON webhook can forward to your local bridge.
  • What is the inbound webhook for? TradingView, Discord bots, or custom systems can POST JSON to your Trade Desky webhook URL. We parse with AI and route futures to NinjaTrader when it is your execution target.
  • When do I need a cloud tunnel? Only when hosted trade-receiver must reach your local Windows receiver over the internet. Same-machine local testing can POST to 127.0.0.1 without a tunnel; production forward URLs still need HTTPS.

Your next alert could be an order.

Start in paper, connect your broker, and go live when you’re ready.

Get started