Automate futures entries and exits
Send TradingView alerts for supported market and pending orders and position-closing commands.
Automate your TradingView futures strategy on an authorized Rithmic account. Route micro and standard contracts with independent account sizing and no desktop execution bridge.
14-day free trial for eligible new connections · One account per regular subscription · Unlimited alerts
Example workflow
Illustrative workflow. Broker permissions, Rithmic access requirements and firm rules apply.
Send TradingView alerts for supported market and pending orders and position-closing commands.
Route instruments such as MES, ES, MNQ and NQ when available to your account. Use whole-contract quantities and verify the active contract.
Use Reverse/Netting to define how opposite signals affect an existing futures position.
Distribute alerts through Clone Mode to individually authorized accounts with their own settings.
AlgoWay routes orders through its server-side Rithmic integration using your configured system and account.
Use Check Connection and Logs and Test to confirm account access and inspect the order responses.
Prop firm accounts: Tradeify lists a Rithmic route; confirm your provider, account stage and permission for external automated execution. Apex Trader Funding prohibits automated entries; do not use AlgoWay for that purpose on Apex accounts. Rithmic access fees or broker-specific requirements are separate from AlgoWay.
Use the same strategy across separately configured futures accounts with Clone Mode. Start with one connection and expand only when needed.
Compare futures automation tools >>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.
Rithmic credentials are scoped to an execution environment. Selecting Rithmic Paper Trading when your broker account is on another system can fail even with a correct username and password. The route also needs the intended trading account and a symbol that resolves to an executable contract.
This page explains the architecture and trading decisions behind that integration. For screen-by-screen configuration, including supported systems, order fields and connection screenshots, use the separate Rithmic setup manual linked below.
Rithmic 01, Paper Trading, 04 Colo and Test are examples of distinct systems; the choice must match your supplied login.
One MES or MNQ contract is a discrete position unit. Fractional final futures quantities are rejected.
The current AlgoWay Rithmic connector uses a net-position model rather than independent long/short hedged positions.
Begin with the Rithmic System named by your broker or prop provider, not a default guessed from the platform name. AlgoWay exposes system, user ID, password and optional account ID fields and provides a Check Connection control.
Verify that your User ID and password work in R|Trader with the Rithmic system actually assigned to the login.
Choose TradingView as source and Rithmic as destination. Complete Rithmic System, User ID, Password and optional Account ID.
Use the form validation before saving. A multi-account login requires explicit account selection.
Determine whether the source uses a continuous chart symbol or the current tradable contract. Apply Symbol Mapping when needed.
Begin with one micro contract, then check buy, flat and opposite-signal semantics in account order history and route logs.
An alert can describe a TradingView continuous futures chart, but the Rithmic destination must resolve the actual execution contract. Keep the payload small while proving connection and contract selection.
{
"ticker": "MES1!",
"order_action": "buy",
"order_contracts": 1,
"order_type": "market"}The route, not an extra platform_name field, chooses Rithmic. In multi-account use, create a separate connection for each account and confirm how MES1! is mapped to the current expiry.
Select the Rithmic system and exact trading account before routing orders. Use whole futures contracts and verify the active contract month. Rithmic uses net positions; configure opposite signals and closing behavior accordingly.
A TradingView strategy produces a long MES alert with one contract. The personal account and an evaluation account may have different order caps, permitted sessions and daily loss limits. Create separately configured destination routes and account IDs instead of expecting a shared login to imply one shared risk profile.
For an account tied to a prop firm, confirm that external API routing is permitted by that firm. Verify that a flat alert leaves zero MES exposure and that the exchange contract month is correct. Only then test pending orders, stop adjustments and multi-account distribution.
Confirm the User ID/password combination and selected Rithmic System in R|Trader first.
Set Account ID when one login exposes more than one trading account.
Use whole futures contracts after all multipliers and sizing rules.
Verify contract month, permissions and any required Symbol Mapping.
A Rithmic login problem is diagnosed by the configured system and account, not by changing strategy JSON repeatedly. Check connection results first, then account permissions, then contract mapping and actual execution status.
The current Rithmic form uses User ID, password, system and optional account ID, rather than a separate API-key field.
The route sends alerts to the configured server-side Rithmic integration; a desktop TradingView chart does not need to remain open to transmit an already active alert.
The current connector uses net futures positions. Reverse/Netting is the intended execution model.
Continuous futures symbols can be resolved by AlgoWay, subject to contract availability, route permissions and mapping.
The dedicated Rithmic webhook guide includes screen-by-screen setup and field references; this page explains workflow decisions and risk implications.
The existing Rithmic setup guide is the detailed technical manual. This page instead explains when and why system/account selection and chart-to-contract mapping matter.
Connect your authorized futures account and validate a test order before going live.
If you are evaluating Rithmic, Tradovate or ProjectX routes, read our TradersPost alternatives for futures traders. The AlgoWay vs TradersPost comparison covers the wider trading automation workflow.