Apex Trader Funding and order flow software: Rithmic access, data and limits

Which system name to enter

A Rithmic connection needs three things: a gateway, a system name, and the credentials for that system. Apex uses a single system name, Apex, for both the evaluation and the funded Performance Account, so the same entry works through the whole account lifecycle. That is not the case everywhere: several firms move you to a different system once you are funded, and entering the evaluation name on a funded account simply fails to log in.

The credentials are the other half. Apex issues a separate Rithmic username and password; the email and password used for the Apex dashboard are not valid at the gateway. Traders who type the dashboard login and get a refusal usually conclude the platform is broken, when the account has simply never been given its Rithmic credentials.

The one-session limit is the real constraint

Rithmic allows one concurrent market-data session per login. This is a Rithmic rule, not an Apex rule, and it applies to every firm on the platform. In practice it means that R | Trader Pro, a charting platform and a second computer cannot all hold the feed at once: the newest connection takes it and the others drop.

For an order flow trader this matters more than it does for someone watching a candlestick chart, because the footprint, the DOM ladder and the liquidity heatmap all read the same market-data session. Apex sells a 2nd Login add-on for traders who want to keep R | Trader Pro open alongside their charts. Without it, the working habit is to close one before opening the other.

What the account can read

Entitlements are set per account, not per platform. If historical data is refused, the gateway answers with a code rather than silence, and the platform should name the refusing step instead of showing an empty chart.

• Live trades with the aggressor side, which is what a footprint chart needs to split volume into bid and ask.
• Depth of market, for the DOM ladder and the liquidity heatmap.
• Historical bars and ticks through the History plant, subject to the entitlements on the account.
• Positions, working orders, fills and P&L through the PnL and Order plants.

Before automating anything

Automation is a separate question from connectivity. A platform being able to place an order on the account does not mean the firm's agreement allows a strategy to do it unattended. Read the account agreement, and ask support in writing if the wording is ambiguous. Senzoukria requires an explicit arming step and a typed confirmation before any strategy can route to a connected account, precisely because that permission belongs to the trader and the firm, not to the software.