Skip to main content

which broker accounts work with edgeful algo automation?

full compatibility reference for edgeful algo automation — supported brokers, which contract symbols to use, prop firm guidance, TradingView paper trading, and what isn't currently supported.

Written by Brad

summary: edgeful's algo automation works with Tradovate, NinjaTrader, and ProjectX futures broker accounts on the all access plan. here's the full compatibility matrix, which contract symbol to use for each broker, prop firm guidance, and what isn't currently supported.

edgeful's algos execute trades through TradingView's brokerage integration. when your alert fires in TradingView, the order goes to whichever broker account you have connected. here's what's supported.

plan requirement: algo automation is an all access plan feature. the essential plan includes all reports, WIP, the screener, edgeful AI, and the TradingView and NinjaTrader indicators, but not automated execution through TradingView.

fully automated vs. manual (alert-based) execution

worth clearing up front, because it's the piece new members most often misunderstand: on the 3 supported brokers, the edgeful algos are fully automated. you set up a TradingView alert once, point it at your edgeful webhook URL, and when the strategy's conditions hit, the order routes to your broker and fills on its own — no clicking, no manual entry.

if your broker isn't one of the supported 3, you're not locked out of edgeful — you just run alert-based (manual) instead. TradingView still fires the same alert, but it notifies you rather than placing the trade, and you enter the position, stop, and target yourself on your broker's platform. same signals and same levels either way; the only difference is whether the fill happens automatically or by hand.

compatibility at a glance

before you read the table, understand that compatibility runs through two independent gates, and both have to pass:

  • gate 1 — infrastructure: is the broker technically supported? automation only routes through TradingView's brokerage integration to Tradovate, NinjaTrader, and ProjectX. if your broker isn't one of those, there's no automated path. you run and execute manually.

  • gate 2 — policy: do your prop firm's own terms permit automated webhook trading? even on supported infrastructure, your firm's rules decide whether automation is allowed. some firms permit full automation, some require manual execution, and some restrict trading in the first minutes of the session (which affects ORB).

edgeful guarantees neither firm compatibility nor policy. gate 1 is on the infrastructure, gate 2 is on your firm's T&Cs. check both before you connect.

last verified: July 2026

broker / account

supported for algo automation?

contract symbol for TradingView alerts

notes

Tradovate

yes

front-month (e.g. NQM2026)

NinjaTrader brokerage account

yes

front-month

the brokerage account, not the NinjaTrader platform

ProjectX (incl. Topstep, TopstepX, and ProjectX-based prop firms)

yes

continuous (e.g. NQ1!)

continuous symbols required — do not use front-month. requires a ProjectX API key (may carry a separate fee — see below)

Rithmic connection

no

automation doesn't route to Rithmic. this is about the connection platform, not the prop firm — many firms (Apex included) also let you connect via Tradovate, which does automate. a Rithmic-only connection runs/executes manually

Interactive Brokers (IBKR)

no

doesn't route to Interactive Brokers; run/execute signals manually

TradeStation

no

doesn't route to TradeStation; run/execute signals manually

MetaTrader (MT4 / MT5)

no

not supported — automation routes through TradingView to futures brokers only; run the data and trade manually in MetaTrader

XM and other retail CFD / forex brokers

no

CFDs aren't currently supported — the team is evaluating expansion; run/execute manually

TradingView paper trading

no

automation only fires through a connected live or funded broker account; execute signals manually

supported broker accounts

the 3 broker accounts compatible with edgeful algo automation are:

  • Tradovate

  • NinjaTrader (brokerage account, not the platform)

  • ProjectX (includes Topstep / TopstepX and any other ProjectX-based prop firm)

note: what matters is the platform your account connects through, not the prop firm's name. many prop firms let you choose your platform — Apex, for example, offers both Rithmic and Tradovate. if your account is on Tradovate, NinjaTrader, or ProjectX it connects and automates the same as a standard account on that platform; only a Rithmic connection can't be automated. so before assuming a firm is unsupported, check which of these platforms your account actually uses.

can I point the webhook at my own broker or router?

no. the webhook URL edgeful generates is fixed — it routes through TradingView's brokerage integration to the specific Tradovate, NinjaTrader, or ProjectX account you connected in the automation dashboard. you can't redirect it to a custom router, a relay, a third-party signal service, or an unsupported broker. there's no setting that repoints the webhook somewhere else.

so if your broker isn't one of the supported 3, the fix isn't a different webhook target — it's connecting a supported account, or running the signals manually. the same applies to fanning one alert out to several brokers at once: automation fires to the single connected account behind that webhook, not to an arbitrary list of endpoints.

connecting ProjectX / Topstep — the API key and fees

ProjectX-based accounts (Topstep, TopstepX, and other ProjectX prop firms) connect a little differently from Tradovate and NinjaTrader: you need a ProjectX API key. you generate the key from your Topstep or ProjectX account, then use it to connect that account in edgeful's automation dashboard and generate your webhook — that webhook goes into your TradingView alert exactly like any other.

on fees: API access on ProjectX is provided by your prop firm, not by edgeful — and some firms (Topstep included) charge a separate fee for API access. edgeful doesn't add anything on top of your all access subscription, but check your firm's current pricing so you know whether the API key carries its own cost. it's not a dealbreaker for automation; it's just worth knowing before you connect.

which contract to reference in your TradingView alert (critical)

the symbol you point your TradingView alert at depends on which broker you're connected to. get this wrong and your orders will be rejected silently.

  • Tradovate → use the current front-month contract (e.g., NQM2026, ESU2026). do not use the continuous symbol. Tradovate executes on a specific contract, and the continuous symbol (NQ1!) can mismatch the broker's active contract during a roll, causing rejected orders.

  • NinjaTrader → use the current front-month contract (e.g., NQM2026, ESU2026). same reasoning as Tradovate. NinjaTrader routes to a specific contract, so your alert needs to be on that specific contract too.

  • ProjectX (Topstep, TopstepX, and all ProjectX-based prop firms) → use the continuous contract (e.g., NQ1!, ES1!, MGC1!). ProjectX requires continuous symbols for live trading. do not use the specific front-month contract. the connection will not route correctly.

rule of thumb: Tradovate / NinjaTrader = front-month. ProjectX = continuous. get it wrong and orders are rejected silently. if you switch broker accounts, update your alert symbol accordingly.

for the full explanation of how edgeful handles rollovers and what to update when a contract rolls, see futures contract rollovers.

prop firms — what to check first

many edgeful members successfully use the algos with prop firm funded accounts, but the key is checking your firm's terms and conditions before you connect. prop firms vary significantly in what they allow. some permit fully automated trading, some require manual execution, and some restrict trading in the first minutes of the session (which affects ORB).

we don't make recommendations on specific prop firms or guarantee compatibility with any particular firm's rules. what we can tell you is that the automation works through standard TradingView webhook alerts — whether that's allowed is up to your firm's terms.

the algo analyzer includes a prop firm simulator that can help you model your algo's behavior against common challenge rule sets — useful for evaluating whether your settings fit within a firm's parameters before you go live.

for setting up multiple funded accounts or running different algo configurations per account, see using edgeful algos with prop firms and multiple accounts.

can I test edgeful algos on TradingView paper trading?

no. edgeful's algo automation does not fire through TradingView's paper trading broker. automated execution only works through a connected live or funded broker account on Tradovate, NinjaTrader, or ProjectX.

if you want to forward-test an algo without risking live capital, connect a demo account on Tradovate or a sim / evaluation account with a prop firm that uses one of the supported platforms.

troubleshooting Topstep and TopstepX connections

Topstep and TopstepX both run on ProjectX, so the continuous-contract rule above applies. if you're connecting a Topstep or TopstepX account and running into a failed connection or errorCode=3, here's how to work through it.

1. try your username instead of your email

the most common cause of this error is using your email address to connect instead of your Topstep username. they're not always the same, so try entering your username and see if that resolves it.

2. try your email instead of your username

if you've been using your username and it's not working, try your email address instead. some accounts are configured differently depending on when they were created.

3. check your API key

if both login methods fail, the issue may be your ProjectX/Topstep API key. double-check that the key you're using is correct and hasn't expired. you can regenerate a new one from your Topstep/ProjectX account and try again.

4. still not connecting?

if none of the above works, reach out through the in-app chat in edgeful. when you do, include:

  • what platform or software you're trying to connect through

  • any error messages or codes you're seeing (besides errorCode=3)

  • whether this connection has worked for you before, or if this is the first time setting it up

that info helps the team diagnose the issue faster.

brokers and connections that aren't currently supported

a few come up often. here's where they stand:

  • TradingView paper trading: not supported. the algos only fire through a connected live or funded broker account. use a Tradovate demo or a sim / evaluation account on a supported prop firm for forward-testing.

  • Rithmic: a Rithmic connection can't be automated — TradingView's webhook integration doesn't route to Rithmic directly. important nuance: this is about the connection platform, not the prop firm. several firms (Apex included) let you choose your platform, so an account you might think of as "Rithmic" can often be connected through Tradovate instead — and that does automate. check which platform your account uses: if it's Tradovate, NinjaTrader, or ProjectX you're supported; only a Rithmic-only connection has to be run and executed manually.

  • Interactive Brokers (IBKR): not currently supported.

  • TradeStation: not currently supported.

  • MetaTrader (MT4 / MT5): not currently supported. edgeful's automation routes through TradingView to a connected futures broker, and that path doesn't reach MetaTrader. you can still run every edgeful report and place the trades manually in MetaTrader, you just can't automate them through edgeful. if MetaTrader support matters to you, share that through Discord or the in-app chat.

  • XM and other retail CFD / forex brokers: not currently supported. CFDs fall outside the TradingView → futures broker path edgeful's automation relies on. the team is actively evaluating expanding compatibility, so share feedback through Discord or the in-app chat if this matters to you.

if there's a broker you'd like to see supported, share that feedback through Discord or via the in-app chat. we factor in member requests.

related articles

Did this answer your question?