Provider-specific endpoint
The ProjectX connection form selects the actual broker or prop provider, including TopstepX where available.
PROP FUTURES & API
TradingView to ProjectX and TopstepX: automate with account rules in mind
ProjectX is an execution API used by several futures prop providers. Each provider has its own endpoint, credentials, accounts and restrictions, so the first task is selecting the correct environment rather than assuming every ProjectX login is interchangeable.
A real integration guide, with execution rules and test scenarios.
ProjectX is an API family, not a single prop account
ProjectX powers order infrastructure for multiple futures providers. A correct username and API key are not enough when the route points at the wrong firm endpoint. AlgoWay exposes a provider choice that determines where authentication and orders will be sent.
TopstepX is a prominent ProjectX-based trading environment, but it is not a universal label for every ProjectX account. In AlgoWay, the Broker/Prop Firm selection and Demo/Live setting matter independently of the API key.
API key authentication
Use the username and API key issued for that provider, not an Rithmic or Tradovate login.
Futures-oriented execution
Contract choice, bracket parameters and account-level limits must remain consistent with the firm’s current rules.
Connect the right ProjectX provider and TopstepX account
Verify that the chosen provider and your particular account permit third-party API execution. The AlgoWay ProjectX form requires provider, Demo/Live environment, account credentials and an API key; it is not a universal pass to every firm on the list.
Confirm API availability
Check whether your ProjectX-based provider permits third-party API execution for the specific evaluation or funded account.
Generate the provider API key
Use the provider’s account portal and keep the API key private; distinguish the trading account ID from a platform username.
Choose ProjectX in AlgoWay
Set Source to TradingView and Destination to ProjectX, then select Broker/Prop Firm and Demo or Live.
Provide login and account selection
Enter Username (Email), API Key and the Account ID where required. The connected account must be the one authorized for automated execution.
Send a small test
Test one permitted micro futures contract with minimal JSON; confirm active orders, brackets and flat behavior in the destination before increasing size.
TradingView MNQ alert example for a ProjectX route
The JSON supplies a single MNQ entry instruction. Bracket distances and risk settings are evaluated separately; the example must not be interpreted as an instruction that bypasses prop-firm rules or automatically places every exit.
Example message sent by TradingView
{
"ticker": "MNQ1!",
"order_action": "buy",
"order_contracts": 1,
"order_type": "market"}ProjectX contracts and account IDs depend on the provider. Make sure MNQ1! resolves correctly and the chosen endpoint is authorized before enabling live execution.
MNQ1! is continuous-chart shorthand. Confirm the ProjectX contract mapping and current expiry, then inspect the executed order for symbol, side and whole-contract quantity.
Provider API access, brackets and evaluation limits
The provider is part of the route
The AlgoWay form lists multiple ProjectX-compatible providers. Changing a username while leaving the previous provider endpoint selected is not the same as changing accounts. Select the right firm and environment first, then authenticate.
The API key is not a universal brokerage token
An API key is scoped by the issuing provider. It may have access to a particular account type or set of endpoints. Incorrect keys, usernames containing unexpected characters and account IDs are common reasons for authentication failures.
Tick distances and bracket orders need contract context
ProjectX supports bracket-style stop/target behavior and a trailing stop path in the current AlgoWay handler. The handler converts supported trailing distance to integer ticks; using a chart value in points as if it were ticks can put a stop at the wrong distance. Confirm the destination’s instrument tick size and units.
Evaluation constraints can override a good backtest
An automated strategy can exceed a prop firm’s max contract count or daily drawdown limit without any code error. The broker may also restrict trading around a session end or news event. Configure the route to respect the account rules; do not treat a successfully accepted order as proof of compliance.
One TradingView signal does not define every exit
Strategy alerts often contain only entry and opposite-direction actions. Decide whether exits are controlled by TradingView, the destination bracket, or a supported management instruction. Two independent stop managers can conflict after partial fills.
ProjectX / TopstepX route validation
| Setting | Purpose | Verification |
|---|---|---|
| Provider | TopstepX or another provider supported in the route | Wrong endpoint rejects otherwise valid credentials |
| Environment | Demo or Live, matching account type | A demo account ID is not a live account ID |
| API Key | Issued for that provider and trading user | Check permission and expiry before blaming alert JSON |
| Contract size | Integer MNQ/MES/ES/NQ quantities | Keep prop firm contract limits separate from strategy quantity |
| Bracket settings | Price or tick distances accepted by the destination | Compare resulting protective orders with the intended distance |
Example: MNQ signals in a permitted TopstepX evaluation
A strategy watches MNQ on TradingView and submits one-contract entry signals. The intended account is a TopstepX evaluation with a contract cap and loss limit specified by the firm. In AlgoWay, choose the appropriate ProjectX provider, API environment and account ID, then test one MNQ order with an appropriate protective bracket.
The useful goal is repeatable rule-following, not a promise to pass the evaluation. Check whether your firm permits the API, whether its drawdown is calculated intraday or end-of-day, and whether a strategy must stop before the session close. Keep those conditions outside the assumptions of a backtest.
ProjectX authentication and contract troubleshooting
API authentication error
Verify provider URL selection, username format, API key and Demo/Live environment.
Wrong account is chosen
Use the explicit Account ID supplied by the provider when the login exposes multiple accounts.
Stop distance surprises
Check whether the configuration uses ticks, points or an absolute price before submitting an order with a bracket.
Firm rejects external execution
A ProjectX API integration does not grant permission contrary to the firm’s current evaluation or funded-account rules.
Distinguish an AlgoWay delivery error from a ProjectX API rejection. Check the selected provider, Demo/Live choice, API permission, target account and the provider-specific error response before resending an alert.
ProjectX and TopstepX automation questions
Is TopstepX the same as ProjectX?
TopstepX is a trading environment built on ProjectX technology. Different firms can offer ProjectX-compatible execution through different endpoints and account rules.
Can TradingView connect to TopstepX with AlgoWay?
Yes, where the TopstepX API account is authorized and the correct ProjectX provider and account are selected in AlgoWay.
Can automation help me pass a prop challenge?
It can execute a strategy consistently, but it cannot guarantee profitable results or compliance with firm-specific restrictions.
Does ProjectX support trailing orders?
The AlgoWay ProjectX handler includes a trailing-stop bracket route. Verify tick conversion and support in the actual provider environment.
Can the same signal be routed to several accounts?
AlgoWay supports multi-route workflows, but each ProjectX account must be authorized and configured with its own account limits.
Futures automation resources beyond ProjectX
For separate strategies, compare Tradovate and Rithmic configuration; their credentials and account handling cannot be copied into a ProjectX API route.
Validate ProjectX permission and account selection first
Start by confirming your prop firm permits the connection and that an order lands in the selected account. Then assess bracket behavior and applicable evaluation limits.
