Home · The Ordane Journal · Rules and Mechanics · Prop Firm API Trading Rules: What to Verify Before You Automate
Prop Firm API Trading Rules: What to Verify Before You Automate
What Is Prop Firm API Trading, and Who Owns the Risk?
Prop firm API trading allows custom software to connect directly to a trading platform to execute automated strategies. CME Group defines an application programming interface as routines, protocols, and tools that specify how software components interact (CME Request Center Glossary, retrieved 2026-09-03). Traders remain fully responsible for the associated execution risks.
Ordane accounts operate on simulated capital. No live funds are traded and no deposits are accepted.
In one sentence: Prop firm API trading lets custom software place orders automatically, but the trader retains full liability for any system malfunctions, errant trades, or connectivity issues that occur during execution.
An automated trading system is a narrower idea. CME Group defines it as a trading method in which a computer makes decisions and enters orders without a person entering those orders (CME Group Glossary, retrieved 2026-09-03). API access is the door. An automated trading system is one thing you can walk through that door with. A human clicking a script-assisted button is not the same as a machine deciding and firing on its own, and a prop firm's rules can treat the two differently even when both use the same API.
Topstep (prop firm) documentation shows the door is real: TopstepX API access can execute trades directly through the TopstepX account (TopstepX API Access, retrieved 2026-09-03). That is a direct, documented capability, not a workaround. But direct execution changes who clicks the button. It does not change who answers for the result.
CME Group states plainly that market participants are responsible for monitoring their own automated trading systems (CME Group RA0913-5 - Wash Trades Prohibited, retrieved 2026-09-03). That is not a prop firm house rule. It is the standard the broader futures industry applies to anyone running code against a live order book, and it exists because the failure modes are structural, not incidental. A dropped connection, a duplicated order, a stale price feed: none of these are hypothetical edge cases. They are the named risks of running unattended software against a market.
Topstep's own combine rules confirm where that liability lands. Automated strategies are permitted in the Trading Combine subject to conditions, but Topstep will not help set up or troubleshoot the strategy, and no exceptions are made for errant trades or system malfunctions (Trading Combine Parameters, retrieved 2026-09-03). Read that clause twice. Permission to automate and protection from the consequences of automating are two separate things, and the first does not imply the second.
API Trading versus an Automated Trading System
Treat "API access is allowed" and "automation is allowed" as two different permissions that happen to overlap. A trader might be authorized to route manually placed orders through an API for speed, while a fully autonomous system making its own entry and exit decisions triggers a different set of restrictions, or none of the same protections. The account rules rarely spell this distinction out in one sentence. You have to read the API document and the account-stage document separately and compare them.
Why Direct Account Execution Does Not Transfer Responsibility
Direct execution through TopstepX is a convenience, not an indemnity. The firm's documented no-exception clause for errant trades and malfunctions means the trader who builds, runs, or licenses the automated system carries the downside of a bug, a bad fill, a runaway loop, or a connectivity gap, even when the API is fully sanctioned and working exactly as designed on the firm's side.
Which Hidden Rules Can Make Permitted Automation Noncompliant?
A general statement that "automated strategies are permitted" is not the same as a clean bill of health for whatever you plan to run. Two documented restrictions sit underneath that general permission, and both are the kind of detail that a summary page omits.
First, Topstep's API-access terms prohibit using remote servers for trading activity (TopstepX API Access, retrieved 2026-09-03). A strategy that is perfectly legal running from your own machine can become a rules violation the moment it runs from a VPS or a cloud instance, not because the strategy itself changed, but because of where the code executes.
Second, permission is not uniform across account stages. Automated strategies are permitted in a Live Funded Account, but automated trading through the ProjectX API is specifically prohibited in that account type (Live Funded Account Parameters, retrieved 2026-09-03). A route that is open in the Trading Combine can close the moment the account graduates, and the account holder finds out only if they read the Live Funded Account terms separately from the Trading Combine terms.
| Check | Trading Combine evidence | Live-account evidence | Authorized route | Restriction | Responsibility |
|---|---|---|---|---|---|
| Automated strategy permission | Permitted with conditions; Topstep will not help set up or troubleshoot the strategy, and no exception is made for errant trades or malfunctions | Permitted, but automated trading through the ProjectX API is prohibited | TopstepX API access, which executes trades directly through the account | ProjectX API automation is blocked once the account reaches Live Funded status | Trader retains full liability for the automated system's orders |
| Remote-server usage | Prohibited under the API-access terms | Same prohibition applies; the source does not carve out an exception by stage | No authorized remote-server route is documented | Running the strategy from a remote server is out of bounds regardless of stage | Monitoring duty stays with the trader, consistent with the industry standard CME applies to automated systems |
Remote-Server and Device Restrictions
The remote-server prohibition is written into the API-access documentation itself, not buried in a separate device policy. Anyone hosting a strategy off their own machine, whether for uptime or convenience, is reading the wrong page if they check only the account-stage rules and skip the API-access terms.
Permission Can Change by Account Stage and API
The Live Funded Account carving out ProjectX API automation specifically, while leaving general automated strategies permitted, shows that "automation" is not one gate. It is at least two: which API you use, and which account stage you are in. Clearing one does not clear the other.
Can You Rely on the Same API Access at Every Stage?
Current documentation and future availability are two different claims, and the ledger only supports the first. What is confirmed today is that Topstep does not currently provide a sandbox environment for its API (TopstepX API Access, retrieved 2026-09-03), and that access conditions already differ between the Trading Combine and the Live Funded Account, as shown above. Neither fact says anything about whether that access will look the same next quarter, and no claim here should be stretched into one about the firm's long-term business continuity or solvency. Verify what is documented now, and re-verify before you rely on it again later.
Why Current Access Is Not a Continuity Guarantee
An account holder who builds a strategy around today's API terms is building on today's terms only. The stage-by-stage differences already documented (Trading Combine versus Live Funded Account) are proof that these rules move. Treat the current rulebook as the current rulebook, not as a forward commitment.
What the Absence of a Sandbox Prevents You From Testing
No sandbox environment means no consequence-free place to run a new script against the platform before it touches a real evaluation or funded account. Every test of connection handling, order acknowledgment, or error recovery happens against the account that is subject to the no-exception liability clause above. That single documented gap changes how carefully a trader should stage a rollout, because there is no safety net between "looks right in a local test" and "running against the account that pays the consequences of a malfunction."
How Much Does Prop Firm API Access Cost?
Topstep lists API Access at $29 per month (TopstepX API Access, retrieved 2026-09-03), billed separately from the trader's Topstep subscription (TopstepX API Access, retrieved 2026-09-03). That is a documented, dated figure for one firm, not an industry-wide price, and it should not be read as what every prop firm charges for API access.
Declared inputs for this check: a $29 monthly TopstepX API access charge, billed separately from the trading subscription, a $0 cost for a sandbox environment because none currently exists, and 12 months in a calendar year. Worked arithmetic: $29 + $0 = $29 confirmed monthly cost of the authorized API route, with no parallel testing environment to absorb early mistakes before they reach the live-scored account.
| Cost item | Amount | Basis |
|---|---|---|
| TopstepX API access, monthly | $29 | Documented rate, billed separately from the trading subscription |
| Sandbox environment cost | $0 | No sandbox is currently offered |
| Projected annual API cost at the current rate | $348 | $29 across 12 months, unchanged from the documented monthly figure |
Over 12 months at the documented rate, that becomes $348 a year, a recurring cost that sits on top of whatever the account itself already charges. A trader comparing prop firms on evaluation price alone will miss this line entirely, which is exactly the kind of recurring charge worth checking against a firm's broader fee schedule before signing up.
The Documented Monthly API Charge
$29 a month is the number on record for one firm, retrieved directly from that firm's own help documentation. Any comparison to another prop firm's API pricing needs its own sourced figure; this article does not have one to offer for a market-wide table, and inventing one would break the same rule this article is asking traders to apply to prop firms.
API Billing versus the Main Subscription
Because API access is billed separately from the trading subscription, a trader auditing total monthly cost has to add two line items, not one. This is the same category of hidden recurring charge that shows up elsewhere in prop firm fee structures, worth checking against a dedicated review of a firm's recurring charges beyond the up-front evaluation price.
How Can You Verify API Rules Before Automating an Account?
Confirm each of the following before a single automated order touches a real evaluation or funded account. Seven steps, in order:
- Confirm the account explicitly permits automated strategies, not just API access in general.
- Identify the specific authorized API or execution route by name, not by assumption.
- Match that permission to the current account stage: what is allowed in an evaluation account is not automatically allowed once the account is funded.
- Check for a remote-server or hosting restriction written into the API documentation itself.
- Verify whether a sandbox or test environment exists before running new code against the real account.
- Record the separate API fee, its billing cycle, and whether it is billed apart from the main subscription.
- Preserve the exact wording of the malfunction and errant-trade liability clause, dated, in case the rule changes later.
That last step matters as much as the first. Saving the dated terms you agreed to, before a firm updates its page, is the only way to prove what you were told when you automated the account. That habit of preserving rules and purchase terms before they change is worth applying to every prop firm purchase, not just the API clause. Once the API check clears, the same discipline extends into a broader audit of the firm itself: its payout history, its rulebook versioning, and whether its other rules are as clearly documented as its API terms. And when an automated order goes wrong, the documented system-failure risk described here is a different question from whether a firm manipulates trade outcomes; the two should never be conflated when deciding who is responsible for a bad fill.
Ready to deploy your automated strategy? Review the Ordane Rulebook and understand our execution clauses before you trade.
Prop Firm API Trading FAQ
Do prop firms allow API trading?
Some do, under conditions. Topstep documents TopstepX API access that can execute trades directly through the account, and separately permits automated strategies in both the Trading Combine and the Live Funded Account, subject to the restrictions and liability rules documented above.
Which prop firms allow API trading?
Topstep is the documented example in this article, with API access priced and billed separately as shown above. Whether another specific firm allows API trading is a question to verify against that firm's own current documentation, not to assume from one firm's policy.
How much does prop firm API access cost?
Topstep's documented rate is $29 per month, billed separately from the trading subscription. That figure is specific to one firm and one date; it is not a market average.
Do prop firms offer an API sandbox?
Topstep currently does not provide a sandbox environment for its API. That means testing happens against the real account, not a consequence-free copy of it.
Who is responsible when an automated trade fails?
Under Topstep's documented terms, the trader is responsible, without exception, for errant trades or system malfunctions. This matches the standard CME Group applies more broadly: market participants are responsible for monitoring their own automated trading systems.
Sources
- CME Group, definitions and glossary entries for application programming interface and automated trading systems. cmegroup.com and cmegroup.com/education Retrieved 2026-09-03.
- CME Group, Advisory on wash trades and market participant monitoring responsibilities. cmegroup.com, RA0913-5 Retrieved 2026-09-03.
- Topstep, TopstepX API access documentation, including direct execution capability, separate billing, remote-server prohibition, and the absence of a sandbox environment. help.topstep.com Retrieved 2026-09-03.
- Topstep, Trading Combine Parameters, on automated strategy permissions and errant trade liability. help.topstep.com Retrieved 2026-09-03.
- Topstep, Live Funded Account Parameters, on restrictions to ProjectX API automation in the funded account stage. help.topstep.com Retrieved 2026-09-03.