Futures automation
Use your existing TradingView strategy to send entry and exit instructions for supported futures contracts.
Turn strategy alerts into futures orders on a ProjectX-based account that explicitly permits cloud API execution. Configure contract sizing, supported protective brackets and independent account routes in AlgoWay.
$9/month · $90/year · 14-day free trial · Unlimited alerts · One trading account per regular connection
Not for TopstepX: remote order routing is prohibited. Read the rules.
Use your existing TradingView strategy to send entry and exit instructions for supported futures contracts.
Send supported stop-loss, take-profit and trailing bracket instructions; confirm tick units and provider support.
Choose the authorized provider, account and order size for each connection.
Distribute signals with Clone Mode to separately authorized connections, with account-specific sizing.
AlgoWay handles server-side webhook routing for eligible providers; no local desktop bridge is needed.
Check your connection, contract and execution responses before enabling a live strategy.
One regular subscription covers one connected trading account, with unlimited TradingView alerts and symbols.
Monthly billing. One account with execution settings, logs and test tools.
Annual billing for the same regular connection.
Available for eligible new connections. Test your strategy and account setup before subscribing.
Clone Mode supports a main route and up to two additional configured routes; each destination requires its own active connection unless covered by All-in-One. All-in-One is $69/month or $690/year. Broker and TradingView charges are separate.
Your strategy generates the signal; AlgoWay sends the order to the authorized provider endpoint. ProjectX technology alone does not establish that a firm permits external cloud execution.
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.
Check whether your ProjectX-based provider permits third-party API execution for the specific evaluation or funded account.
Use the provider’s account portal and keep the API key private; distinguish the trading account ID from a platform username.
Set Source to TradingView and Destination to ProjectX, then select Broker/Prop Firm and Demo or Live.
Enter Username (Email), API Key and the Account ID where required. The connected account must be the one authorized for automated execution.
Test one permitted micro futures contract with minimal JSON; confirm active orders, brackets and flat behavior in the destination before increasing size.
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.
{
"ticker": "MNQ1!",
"order_action": "buy",
"order_contracts": 1,
"order_type": "market"}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.
Use only a provider and account that expressly allows remote API execution. Select its correct endpoint and credentials. Verify whole-contract sizing, bracket tick distances and the provider's trading restrictions before enabling automation.
On an account that expressly permits remote API execution, send a one-contract MNQ test entry, confirm the protective bracket and test the closing signal. Verify the contract cap, session and drawdown rules before live use. This example is not intended for TopstepX.
Verify provider URL selection, username format, API key and Demo/Live environment.
Use the explicit Account ID supplied by the provider when the login exposes multiple accounts.
Check whether the configuration uses ticks, points or an absolute price before submitting an order with a bracket.
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.
TopstepX is a trading environment built on ProjectX technology. Different firms can offer ProjectX-compatible execution through different endpoints and account rules.
No. Topstep prohibits remote-server order routing, and Live Funded Accounts cannot use its ProjectX API. AlgoWay cloud routing is not permitted for TopstepX.
It can execute a strategy consistently, but it cannot guarantee profitable results or compliance with firm-specific restrictions.
The AlgoWay ProjectX handler includes a trailing-stop bracket route. Verify tick conversion and support in the actual provider environment.
AlgoWay supports multi-route workflows, but each ProjectX account must be authorized and configured with its own account limits.
For separate strategies, compare Tradovate and Rithmic configuration; their credentials and account handling cannot be copied into a ProjectX API route.
Confirm your provider permits cloud API routing before starting a trial.
Choosing execution for a ProjectX-based or prop-futures account? Start with Best TradersPost alternatives for futures traders and AlgoWay vs TradersPost for account and signal-routing differences.