Which futures trading API you can use is settled by access gates, not features: as of November 2026, Tradovate's API (application programming interface, the door a program uses to send orders and read account data) needs your own live funded account holding at least $1,000 plus a $25 a month add-on, and Rithmic and CQG make your application pass a conformance test before it reaches production. The big qualification is your account type. Prop and evaluation accounts are shut out of Tradovate's API, and Topstep's ProjectX API, $29 a month, is closed to Live funded accounts and to any bot trading from a VPS.
Your account type picks your futures API before any feature does. Tradovate's API Access article, as quoted by Autoview, asks for a $1,000 funded brokerage balance plus $25 a month and excludes prop and evaluation accounts; Topstep charges $29 a month for ProjectX API access but bars Live funded accounts and any trading from a VPS. Rithmic and CQG add a conformance test with no published duration, so budget time as well as money.
Which futures trading APIs can a retail trader actually get?
A personal trader can get the Tradovate, Interactive Brokers and TradeStation APIs with a funded brokerage account, the ProjectX API through Topstep, and Rithmic or CQG only after a conformance test. NinjaTrader's network API, TradeAPI, is sold to businesses, not to individuals.
Every route passes three gates in order: account type, approval (a minimum balance, a business integration or a conformance test, where the vendor watches your program place, change and cancel orders) and the monthly fee.
The table puts each gate side by side, with "not published" wherever the vendor states nothing.
| API | Gate | Published API fee | Prop accounts | Market data |
|---|---|---|---|---|
| Tradovate | Live brokerage account, $1,000 minimum | $25 a month add-on | Excluded (prop and evaluation) | Separate CME licence, fee not published |
| Rithmic (R|API+, R|Protocol, R|Diamond) | Dev kit, test system, conformance, via an FCM | Set by the FCM (Ironbeam: $25 a month plus $0.10 per contract) | Not published | Ironbeam Level 1 from $3.00 per exchange a month |
| ProjectX (TopstepX) | Subscription; orders from your own device | $29 a month ($14.50 with code) | Live funded excluded | Not stated |
| CQG Web API and FIX Connect | Formal conformance; FIX by questionnaire | Add-on $45 real-time or $245 trading; Web API and FIX on request | Not published | Exchange fees extra |
| Interactive Brokers TWS API | Funded account; TWS or IB Gateway running | None published | Not published | Paid subscriptions required |
| TradeStation API | Funded account; key on request | None published | Not published | Not stated |
| NinjaTrader NinjaScript | Runs inside the desktop platform | Plans $0, $99 a month or $1,499 once | Depends on the firm's platform | Not stated |
| NinjaTrader Connect TradeAPI | Business integration, 6 to 12 weeks | Not published | Built for firms | Part of the product |
| Webhook layer (TradingView alerts) | Paid plan, two-factor authentication | Set by the receiving service | Where the firm's rules permit | Your charting plan |
Compiled by Phoenix Technologies from each vendor's documentation, help center or a broker's published schedule, read November 19, 2026. Tradovate figures come from Tradovate's API Access article as quoted by Autoview, because Tradovate's own page did not load.
Read the "Prop accounts" column first. Only ProjectX documents API trading on prop accounts, and it carves out Live funded; every other cell reads excluded, not published or depends on the firm.
What does the Tradovate API require?
Tradovate issues an API key only to a live, funded Tradovate brokerage account with at least $1,000 in it, and the API Access add-on costs $25 a month. Tradovate's API Access article, as quoted by Autoview, says: "Prop firm and evaluation accounts are not eligible for API access."
That settles the most common misreading: paying the $25 add-on does not turn a prop dashboard into an API account, because a prop balance is not a Tradovate brokerage balance. CrossTrade reports the same exclusion in a post dated November 12, 2026.
The second myth is the trick a vendor blog suggests: fund to $1,000, get the key, then withdraw. Tradovate does not publish whether a key stays active once the balance falls below $1,000, so trying it bets a working bot on an unpublished policy.
The first-year arithmetic: 12 months at $25 is $300 in fees, and the $1,000 balance is capital you tie up rather than spend, so the cash committed in year one is $1,300. Streaming market data through the API needs a separate CME licence whose fee Tradovate's article does not quote. How the two main connections differ is in Rithmic versus Tradovate connections.
How do you get Rithmic API access?
You request a Rithmic dev kit, build against Rithmic's test system, pass a conformance review, and only then receive production credentials through the FCM (futures commission merchant, the broker that holds your account). Ironbeam, one such FCM, says developers should "request a Rithmic dev kit, build and test their application against the Rithmic test system, and pass conformance review before receiving production credentials".
Rithmic offers three API families, per Ironbeam: R|API+ for C++ and .NET, R|Protocol API built on Google Protocol Buffers, and R|Diamond API, which Ironbeam calls the highest-performance option. R|Protocol is the Python coder's route, because Ironbeam calls it "language-agnostic and OS-agnostic". A 2026 RFC on the NautilusTrader GitHub adds that it runs over WebSockets, which our guide to WebSocket, FIX and REST connections explains.
Conformance certifies the application, not you. The same RFC describes Rithmic monitoring session logs while the app runs prescribed scenarios: order placement, modification, cancellation and disconnect recovery. A pass earns a four-character prefix tied to an app_name.
That prefix settles the myth that bridges skip conformance: tools that offer Rithmic access without a test certified their own app_name, so you skip the test only by running their application, not your code. Rithmic publishes no conformance duration, fee or per-user licence price in any source we could read, and the "$100 per user ID" figure on some sites has no traceable primary source.
The "$500 minimum" some sites attach to Rithmic is Ironbeam's broker rule, beside its $25 monthly connection fee and $0.10 per contract routing; other FCMs price Rithmic differently. The R|Diamond figure ranked lists repeat, "less than 250 microseconds" from market data read to order release, describes a co-located setup, according to Optimus Futures; no vendor publishes a home or VPS latency for any API here.
What does the ProjectX API cost, and which Topstep accounts can use it?
TopstepX API Access costs $29 a month, or $14.50 with the 50% code Topstep gives its traders, and Live funded accounts are excluded. Topstep's help center, last updated September 17, 2026, states: "No, Live funded accounts are not allowed to trade through the ProjectX API."
The rule most API roundups miss is about where your code runs. Topstep states that "The use of VPS, VPNs, and remote servers is prohibited by Topstep's Terms of Use", and adds: "Your server can watch and record, but it cannot trade." Our check of VPN and VPS rules at prop firms covers the other firms.
A paid API key does not change where your code is allowed to run.
Inside those limits, Topstep allows custom bots through the API, subject to its platform rules and its ban on high-frequency trading. The ProjectX Gateway documentation accepts only API-key login, and a session token lasts 24 hours before requests fail with HTTP 401, so an overnight bot must log in again. The story of ProjectX and TopstepX covers which firms used the platform.
What do CQG, Interactive Brokers, TradeStation and NinjaTrader require?
CQG requires a formal conformance test and lists $1,090 a month for the stack that carries its API Trading add-on, while Interactive Brokers and TradeStation need a funded account and publish no API fee on the pages we read. NinjaTrader's NinjaScript runs inside its desktop platform, and its network API is a business product.
CQG
CQG's Web API testing page states: "We require a formal conformance test before any API-powered application can connect to our production environment." CQG's monthly price sheet lists the Integrated Client at $595, CQG Trading at $250 more, and an API add-on of $45 for real-time data or $245 for trading, the latter requiring CQG Trading or CQG Spreader. Both API add-ons carry a footnote: "Requires questionnaire and exchange approvals to determine actual pricing." So $1,090 is the list starting point, not a quote. CQG Quotes Only takes a $35 real-time API add-on, Web API and FIX Connect are "Contact us for pricing", and FIX starts with an enterprise questionnaire. The CQG and Rithmic feed comparison covers the data side.
Interactive Brokers
The IBKR TWS API is not a cloud endpoint. Interactive Brokers' TWS API documentation says it "requires network connectivity to a running instance" of TWS or IB Gateway. For market data, IBKR lists trading permissions, a funded account (except forex and bonds) and live market data subscriptions. So the claim that IBKR's API is free is half true: no API fee is published, but your code sees no live price without a funded account and paid subscriptions.
TradeStation
TradeStation's API FAQ says you need a TradeStation account, and a funded account holder requests a key by email. That page states no minimum balance, so check TradeStation's account-opening terms for the current funding requirement. The API covers stocks, options and futures.
NinjaTrader
NinjaScript is a C# framework for indicators and strategies that run inside NinjaTrader, which is free for charting, backtesting and simulation. Plans are $0, $99 a month or $1,499 once, and the pricing page does not say which plan runs NinjaScript strategies on a live account.
NinjaTrader Connect's TradeAPI, the REST and WebSocket product that ranks for "futures trading api", is aimed elsewhere. NinjaTrader Connect says: "If you're building a consumer-facing trading product and need regulated futures behind it, you're the target user." Its path of access, build and test, UAT validation and go-live takes most partners 6 to 12 weeks, depending on scope and readiness.
What are the rate limits of each futures API?
The published limits in the table below run from 64 requests a minute on TradeStation's account endpoints to 3,000 messages a minute into a local IBKR TWS, but they count different things, so they are not a speed ranking. Rithmic and CQG publish no rate limit in any source we could read.
The table converts each published quota to a per-minute figure and keeps its scope beside it.
| API | Published limit | Per minute | Scope | Over the limit |
|---|---|---|---|---|
| Tradovate (NT Connect docs) | 5,000 per hour | 83.33 on average | Per authenticated user, all endpoints, per hour | HTTP 429, plus p-tickets |
| ProjectX | 200 per 60 seconds | 200 | All endpoints except history bars | HTTP 429 |
| ProjectX history bars | 50 per 30 seconds | 100 | POST /api/History/retrieveBars | HTTP 429 |
| TradeStation accounts | 320 per 5 minutes | 64 | Accounts, balances, positions, order details | HTTP 429 |
| TradeStation quotes and bars | 500 per 5 minutes | 100 | Quote and bar streams | HTTP 429 |
| IBKR TWS | 50 messages per second | 3,000 | Messages into one TWS, shared by all clients | Not stated in fetched docs |
| Rithmic, CQG | Not published | Not published | Not published | Not published |
Computed by Phoenix Technologies from the NT Connect rate limits page, the ProjectX Gateway rate limits, TradeStation's rate limiting overview and IBKR's TWS API introduction, read November 19, 2026; method: quota divided by window in minutes, rounded to two decimals.
Tradovate's limit now lives in NinjaTrader's NT Connect partner documentation, where the old Tradovate partner site redirects. The docs list the authenticated-user limit as 5,000 an hour, 5,000 a minute and 5,000 a second, so a burst can pass 83 requests in one minute and the hourly figure is the one that binds. Separate per-endpoint caps, such as 5 access-token requests an hour, run on what the docs call "a rolling one-hour window, not a fixed hourly reset."
The trap experienced coders know is the penalty ticket. Tradovate's partner docs on penalty tickets say "P-tickets don't come back as an error": they arrive as HTTP 200 OK with a p-ticket field, and the client must wait and resend. Code that checks only the status code believes the order went through; backoff handling is in why automation gets throttled.
Worked example: one signal, 20 accounts
Take an illustrative trader with 20 accounts who sends each signal as three requests per account: one entry, one stop, one target.
- Requests per signal: 20 accounts x 3 = 60.
- Tradovate: 5,000 divided by 60 is 83.33, so 83 full signals an hour (4,980 requests); an 84th would need 5,040. Because prop accounts are excluded, these are 20 personal Tradovate accounts under one user.
- ProjectX: 200 divided by 60 is 3.33, so 3 signals a minute (180 requests) if all 20 accounts share the 200-a-minute budget; a 4th would need 240.
- Spread evenly, Tradovate's hour allows 1.38 signals a minute, and order changes, retries and status checks also count, so real headroom is lower.
What does a futures API cost per month, and is market data included?
Published API fees run from $25 a month (Tradovate's add-on, or Ironbeam's Rithmic connection fee before routing) to $1,090 a month at list price for CQG's Integrated Client stack with API trading. Wherever a vendor addresses it, exchange market data is billed on top.
| Route | Monthly | Annual | What it buys |
|---|---|---|---|
| Tradovate API add-on | $25 | $300 | API key on a funded account ($1,000 held, not spent) |
| Ironbeam Rithmic connection | $25 plus $0.10 per contract | $300 plus routing | Rithmic connection for Ironbeam clients |
| TopstepX API | $29 ($14.50 with code) | $348 ($174 with code) | API access for eligible Topstep accounts |
| CQG Integrated Client, CQG Trading, API Trading | $1,090 | $13,080 | Trading through CQG's API |
| IBKR, TradeStation | None published | None published | Funded account required |
Computed by Phoenix Technologies from the fees above; method: annual = monthly x 12, CQG = $595 + $250 + $245. Exchange data fees are excluded for every row. CQG's API add-ons are list prices subject to a questionnaire and exchange approvals.
CQG's listed stack costs 43.6 times Tradovate's add-on, a price set for firms, not one bot.
Rithmic's cost at Ironbeam scales with volume: an illustrative 400 contracts a month adds $40 in routing to the $25 connection fee, $65 in all, plus Level 1 non-professional data from $3.00 per exchange a month. How CME bills data used by programs rather than screens is in CME market data fees explained.
Can you use an API on a prop firm account?
Only where the firm documents it: Topstep publishes a paid ProjectX API for its accounts except Live funded, and Tradovate excludes every prop and evaluation account from its own API. We could not read another firm's API policy for this piece, so check the firm's own rules before you write code.
Three routes are documented. The first two are the firm's own API where it publishes one, as Topstep does, and an approved platform with built-in automation, such as NinjaScript where the firm offers NinjaTrader. Firm-by-firm rules on bots are in our guide to automated trading rules at prop firms.
The third is a webhook layer: any program sends orders to a URL, and a service places them. TradingView's webhooks need a paid plan, two-factor authentication and port 80 or 443, and they cancel any request the receiving server takes longer than three seconds to process. Which plan you need is in TradingView for prop futures, and keeping accounts in step is in one TradingView strategy on many accounts.
A trade copier with a webhook input is one such layer. Thor's webhook API takes futures orders from any program, from a TradingView alert to a Python bot, at one private URL and places each on every account that follows it; its separate REST API, for reading and flattening positions, allows 100 requests a minute per key. Entries go in at market, there are no resting limit or stop entries, and it is built for strategy orders, not high-frequency trading. Any server-side layer, a copier included, still has to fit the firm's rules: Topstep's ban on servers that place orders rules it out there, as our check of VPN and VPS rules explains.
Which futures API should you choose?
Choose by account type first and need second: a personal live account opens every broker API, a prop evaluation narrows you to the firm's own API or a layer its rules permit, and a Topstep Live funded account closes the ProjectX API. Then test the rate limit against your requests per signal.
- If your account is a prop or evaluation account, rule out Tradovate's API first, whatever balance the dashboard shows.
- If you trade at Topstep, run the ProjectX API from your own device, never a VPS, and never on a Live funded account.
- If you code in Python and want Rithmic, plan for R|Protocol and a conformance timeline nobody publishes, or run a certified third-party application.
- If your personal Tradovate balance is under $1,000, compare IBKR or TradeStation, and price their data subscriptions before you call them free.
- If one signal fans out to many accounts, divide the vendor's limit by accounts times requests per account; if that leaves fewer signals than your busiest minute needs, cut requests per signal before adding accounts.
- If you need resting limit or stop entries, or high-frequency order flow, a webhook copier is the wrong tool; call the broker's API directly.
- If you are building a product for other traders, NinjaTrader Connect's TradeAPI or CQG FIX Connect are the routes, with 6 to 12 weeks or a questionnaire ahead of you.
Go deeper
- API Rate Limits: Why Your Automation Gets Throttled at the Worst Possible Moment
- Automated and Algo Trading on Futures Prop Firms: Bots, EAs and the Rules
- How Trade Copiers Talk to Your Broker: WebSocket, FIX and REST
- Can You Use a VPN or VPS With a Prop Firm? 11 Firms Checked
Frequently asked questions
Is there a free futures trading API?
Not in a useful sense for live trading. Interactive Brokers and TradeStation publish no API fee on the pages we read, but both want a funded account, and IBKR also requires paid live market data subscriptions before the API returns prices. NinjaTrader is free for charting, backtesting and simulation, and its pricing page does not say which plan runs NinjaScript strategies live.
Which futures API works best with Python?
Any API that speaks a web protocol can be called from Python, and the routes that do are documented. Rithmic's R|Protocol API uses Google Protocol Buffers, which Ironbeam calls language-agnostic and OS-agnostic, so it is Rithmic's route for Python. ProjectX and TradeStation publish rate-limited web APIs, and the IBKR TWS API talks to a TWS or IB Gateway program you run yourself.
How long does Rithmic conformance take, and what does it cost?
No public figure exists. No Rithmic page we could read states a duration, a fee or a per-user API licence price, and the $100 per user ID figure on some sites has no traceable primary source. CQG does not publish its conformance duration or fee either.
Does the Tradovate API work on Apex or other prop firm accounts?
No. Tradovate's API Access article, as quoted by Autoview, makes prop firm and evaluation accounts ineligible whatever the balance, so any prop account on Tradovate is outside its API. We could not read Apex's help center for this piece, so check the firm's own automation rules for the routes it does allow.
Do you need a CME licence to place orders through the Tradovate API?
According to CrossTrade, Tradovate staff told traders on Tradovate's forum that the licence is only required for market data over the API, not for order placement or account reads. Tradovate's article itself does not quote the licence fee. Treat both the scope and the price as something to confirm with Tradovate before you build.
How long does a ProjectX API session token last?
24 hours from issue. After that, requests fail with HTTP 401 and your program must log in again with its API key, which is the only supported way to obtain a token. If you cannot find where to generate a key, the ProjectX docs tell you to contact your firm.
Can you get higher rate limits on the Tradovate API?
Only as a high-volume integration with an established partnership, according to NinjaTrader's NT Connect partner documentation. For an individual key, plan around 5,000 requests an hour per user ID. Over the limit, the server stops handling requests for a period and answers each new one with a 429 status code.
Does one TopstepX API key cover several accounts?
Yes. Topstep's help center says one subscription and one API key cover every eligible account under your ProjectX Dashboard profile. Live funded accounts are not eligible, so the key does not reach them.
Sources
- Topstep Help Center (2026), TopstepX™ API Access
- ProjectX Gateway API documentation (2026), Rate Limits
- NinjaTrader (NT Connect partner API documentation) (2026), Rate Limits
- NinjaTrader (NT Connect partner API documentation) (2026), Penalty Tickets (p-tickets)
- CQG (2026), Monthly Price Sheet
- Interactive Brokers (2026), TWS API v9.72+: Introduction
- TradeStation API documentation (2026), Rate Limiting Overview
- NinjaTrader Connect (2026), TradeAPI: Futures Trading API (REST + WebSocket)
- Ironbeam (2026), Rithmic Futures Trading at Ironbeam: Platforms, Data & APIs
- Autoview (quoting Tradovate support) (2026), Tradovate API access: what you need before any bridge works