Secure API data lanes, two illuminated evaluation stages, and a weekend maintenance clock on a futures market operations desk
Weekly Roundup

TopstepX Adds an Official API Path: September 14–18, 2026 Recap

TopstepX gains a documented API path, Tradeify 247 clarifies its 2-Step route, and September 19 maintenance shows why scope matters.

$29/mo
API list price
2 stages
Tradeify 247
6%
Static max loss
6 hours
CME window
Sep 23
Rules verified

Reporting window: September 14–18, 2026 Developments verified: September 23, 2026, 7:31 AM MDT Next review: September 25, 2026, or sooner after a cited source changes

Topstep now documents a paid TopstepX API access path for custom tools and automated strategies on eligible simulated accounts. The important limits are as consequential as the new capability: Live Funded Accounts are excluded, order transmission must originate from the trader's personal device, high-frequency trading remains prohibited, and there is no sandbox. Tradeify 247's current 2-Step evaluation is also unusually specific about its two targets, static loss floor, daily-loss calculation and first-payout days. For weekend operators, CME's September 19 notice and TradingView's completed maintenance record show why the exact platform and market scope matter.

Those are the three practical developments worth carrying from September 14–18. Routine discount changes, expired-code cleanup and unresolved Help Center conflicts did not make the cut.

1. Topstep documents a paid API path for TopstepX automation

Topstep's current Help Center now gives traders a complete route to TopstepX API access through ProjectX: create or use a ProjectX Dashboard account, purchase the API subscription, link it to the TopstepX profile, and generate an API key inside TopstepX. This is a material platform change for traders who previously had to work entirely through the graphical platform or supported front ends.

The API can pull live and historical market data, read account state, execute trades and support custom risk controls or automated strategies. One subscription and one API key can cover every eligible account linked to the same ProjectX Dashboard profile. Topstep expressly says traders may build their own bots, subject to its normal trading rules and a prohibition on high-frequency trading.

The subscription is separate from a Trading Combine or funded-account fee. ProjectX lists it at $29 per month; Topstep traders can apply the published topstep code for a continuing 50% rate of $14.50 per month. Billing appears separately as Sim2Funded Solutions. A trader should therefore treat API access as an additional operating cost, not a feature already included in the Topstep subscription.

QuestionTopstep's current answerPractical implication
Eligible stageTrading Combine and Express Funded Account environmentsThe documented route is for simulated TopstepX accounts
Live Funded AccountNot supported through the ProjectX APIAutomation that works in an XFA cannot simply continue after a live call-up
Subscription$29 monthly; published Topstep rate $14.50 monthlyBudget it separately from evaluation and activation costs
Accounts per keyOne linked subscription/key can manage eligible accounts on the profileAccount IDs must be selected carefully for every order
Automated strategiesCustom bots allowed under standard rules; HFT prohibitedAutomation does not waive strategy, conduct or risk rules
Remote executionOrders must originate from the trader's personal device; VPS, VPN and remote order relays are prohibitedA common cloud-hosted bot architecture is not permitted
TestingNo sandbox; use a Practice accountProduction credentials should not be the first test environment

The remote-hosting boundary changes the engineering decision

The closest alternative is manual or semi-manual execution through TopstepX and its native risk controls. API access adds programmable order flow, but Topstep draws a bright line around where that order flow may run. Historical storage, research, backtesting, logging and read-only dashboards may live on a private server. Placing, modifying or cancelling orders—or relaying an automated trigger to an order endpoint—from a VPS, VPN or remote server is not allowed.

That distinction matters because many off-the-shelf trading bots assume an always-on cloud host. A developer should not interpret the existence of an API as permission to deploy that standard architecture. The local machine must remain the origin of trading activity, and the trader remains responsible for every order submitted by the bot.

The API key also carries broad authority. Topstep warns that a key grants full trading access to every eligible account under the linked profile. It should be treated like a password, kept out of public repositories and untrusted third-party tools, and rotated immediately if exposed. There is no Topstep coding support and no endorsement of third-party integrations; ProjectX documentation and the community API channel are the support surfaces.

Stage transition is the biggest operational tradeoff

The most important before-and-after moment is a move from an Express Funded Account to a Live Funded Account. Topstep's documented ProjectX API is available in the simulated environment and is not available for Live. A trader whose process depends on automation needs a separate manual live workflow before accepting that transition. This is not merely a feature gap: it can change execution speed, risk controls, monitoring and the trader's ability to reproduce the same strategy.

The lack of a sandbox adds another constraint. Topstep directs traders to a Practice account for testing, which can exercise the same endpoints and real-time hubs without exposing an evaluation. That still requires careful separation of practice and eligible account IDs. Rate limits, token refresh, reconnection logic, duplicate-order prevention and a manual kill switch should be tested before any live simulated account is connected.

What to verify before acting: current monthly price, subscription renewal, eligible account types, ProjectX linking, API-key scope, practice-account access, rate limits, token refresh, account ID selection, local-device requirement, VPS/VPN prohibition, HFT policy, permitted strategy behavior, risk-rule enforcement, and the manual plan required if Topstep moves the trader to Live.

2. Tradeify 247's 2-Step route is the clearest part of its current lineup

Tradeify 247 now publishes a dedicated 2-Step route across 10K, 25K, 50K and 100K account sizes. Phase 1 requires 10%; Phase 2 requires 5%. Both phases use a fixed 6% maximum-loss floor and a 3% daily-loss calculation based on the previous closing balance captured at 22:00 UTC. The breach check uses live equity, so an unrealized loss can end the account before a position is closed.

SizeList pricePhase 1 targetPhase 2 targetDaily lossStatic maximum loss
10K$100$1,000$500$300$600
25K$200$2,500$1,250$750$1,500
50K$350$5,000$2,500$1,500$3,000
100K$580$10,000$5,000$3,000$6,000

There is no minimum-day requirement in either evaluation phase. Evaluation profit does not carry into the next phase or funded account, so the 50K path is not one continuous $7,500 climb. It is a $5,000 target from a fresh Phase 1 base, followed by a separate $2,500 target from a fresh Phase 2 base.

The funded account starts again at the purchased base balance and keeps the 6% static floor. Tradeify 247 says the 2-Step funded route has no payout lock, an 80% base profit split and a $100 minimum request. Before the first payout, however, the trader needs three profitable days, each closing at least 0.5% above that day's starting point. On a 50K account, that is three $250-or-better days. The profitable-day requirement applies only after funding, not during either evaluation phase.

This is the practical tradeoff against the closest current alternative, the 1-Step route: two resets and 10%/5% targets cost more time than a single phase, but the 2-Step route has lower targets per phase and the current dedicated guide clearly states no payout lock. Current first-party pages conflict on the 1-Step funded payout lock and minimum-day treatment, so this recap does not settle that comparison by inference.

What to verify before acting: exact checkout price, phase reset behavior, 22:00 UTC daily snapshot, live-equity breach calculation, 6% fixed floor, account-review and KYC sequence, base funded balance, three 0.5% profitable days, $100 request minimum, 80% split, optional add-ons, maximum combined funded allocation, platform, instrument access, and the current written terms attached to the purchased account.

3. September 19 maintenance showed why scope matters, not a blanket outage

CME's September 14 notice said it would temporarily extend the Saturday maintenance window for specified 24/7 markets on September 19 from 2:00 AM to 8:00 AM Central Time. The official notice named CME Crypto Futures, CME Crypto Options, Event-Based Contracts and Event Contracts II. After that one-day extension, CME said the standard Saturday window would return to 2:00–4:00 AM CT.

TradingView's current status record shows its planned September 19 maintenance began at 07:03 GMT and finished at 07:38 GMT. At the September 23 verification, TradingView listed its website, data feeds, alerts, charts and trading component as operational. The recorded TradingView work therefore fell inside CME's published 2:00–8:00 AM Central window, but the two first-party records describe different surfaces.

SurfacePublished windowStated scopeTrader action
CME GlobexSep 19, 2:00–8:00 AM CTNamed 24/7 crypto and event-market channelsConfirm whether the intended contract, firm and platform are actually affected
TradingViewSep 19, 07:03–07:38 GMTCompleted planned maintenance recordCheck the live component status before attributing a trading issue to the platform

Neither record establishes a blanket prop-firm outage. CME's notice does not establish that a given prop firm offers the named contracts, and TradingView's completed maintenance record does not establish a trading-component outage. A trader should verify the exact firm platform, instrument permission, maintenance conversion to local time, open-order behavior and support channel instead of extrapolating from a generic status headline.

What to verify before acting: contract and market-data channel, prop-firm permission, platform maintenance notice, local-time conversion, whether order entry or only the public website is affected, status-page changes, resting-order handling, risk-limit reset, and the firm's incident/escalation procedure.

What stayed out of this recap

  • GOAT Funded Futures' new Daily Payouts material was not used because current first-party pages conflict on whether the payout processing fee is 2% or 3%. That requires written reconciliation.
  • Funded Futures Family's Premier+ pages conflict on whether funded accounts have no consistency rule or a 40% consistency rule. The recap does not choose between them.
  • Tradeify 247's 1-Step pages conflict on payout-lock and minimum-day treatment; only the separately consistent 2-Step path is summarized.
  • Topstep Labs purchase chronology remains an existing-page human-review issue and was not recycled as a new weekly development.
  • Routine public-code changes, owner-code housekeeping and short-lived offers were excluded as editorial topics.
  • Reviewed CFTC releases did not establish a prop-firm closure, payout freeze or new retail-prop enforcement action during the reporting window.

What to watch September 23–25

  1. Whether Topstep publishes a dated API launch announcement, changes eligible account stages, or clarifies local-device enforcement.
  2. Whether Tradeify 247 reconciles its 1-Step funded terms.
  3. Whether GOAT Funded Futures reconciles the 2% versus 3% payout-fee conflict.
  4. Whether Funded Futures Family reconciles Premier+ funded consistency.
  5. Whether CME or TradingView publishes a post-maintenance impact notice or related operational change.

Current Firm Offers and Direct Links

Open the firm in a new tab with the recorded ComparePropFirms commercial link. Use the displayed code when applicable, and confirm the final price and terms before paying.

Official sources and verification