Rithmic connection and gateways: systems, access points, subscriptions

Senzoukria connects to Rithmic directly through R | Protocol with your own login: a system name identifies the firm, a gateway URL identifies the entry point, and the chart subscribes to the selected contract as soon as the connection is ready.

Senzoukria · Documentation · Updated September 2026

Where to find it

Where
Broker Connections → Add connection → a Rithmic rail; fields System name, Access point, Gateway URL
Default gateway
Chicago (core), wss://rprotocol.rithmic.com:443
Test gateway
wss://rituz00100.rithmic.com:443, serves only the system Rithmic Test
Access points
13 listed by the backend; Colo75 is colocation only

What it does

A Rithmic profile carries a system name, a gateway URL, a username and a password kept in the OS keychain. The system name is not an account type: it is the identifier of the firm on Rithmic's side. The same login presented to another firm's system is unknown there, and Rithmic replies rp_code 13 (permission denied), the same code as a real entitlement refusal. This is why the wizard applies environment, system and gateway as one block and checks the system against the broker's catalog.

The Access point select rewrites the single Gateway URL field; nothing else is stored. Every access point serves the same systems, only the network route changes, and the closest is not automatically the fastest. Chicago (core) is the default and the only path proven end to end in production. Rithmic Test lives on its own gateway, so the select is disabled when the system is Rithmic Test; switching environment keeps a chosen regional access point only when the new environment also targets production.

On the chart, the Rithmic footprint watches the live connection state. As soon as a connection is ready it subscribes to the selected contract, unsubscribes the previous one when you change symbol, and treats a subscribe that races an intentional disconnect as expected rather than as an error. Rithmic attribution is displayed on every surface that shows their data.

Systems by broker

System names preset by the catalog (production gateway unless stated)
BrokerEnvironmentsSystem name
Apex Trader FundingEvaluation · Performance Account (PA)Apex
Lucid TradingEvaluation · LucidPro (Funded)LucidTrading
4PropTraderEvaluation · Performance (Funded)Rithmic Paper Trading
BluSky, BulenoxEvaluation · FundedRithmic Paper Trading
Take Profit TraderEvaluation · PRO+ (Funded)Rithmic Paper Trading · Rithmic 01-US
AMP FuturesDemo · LiveRithmic Paper Trading · Rithmic 01
Rithmic (Direct)Rithmic Test (UAT) · Rithmic Paper Trading · Rithmic 01Rithmic Test on the UAT gateway; the other two on production
Custom (Rithmic)Configure manuallyAny system and gateway you enter

Access points

  • Chicago (core), the default: wss://rprotocol.rithmic.com:443.
  • Regional entries, alphabetically: Cape Town, Frankfurt, Hong Kong, Ireland, Mumbai, New York, Sao Paulo, Seoul, Singapore, Sydney, Tokyo, each on its own wss://rprotocol-<code>.rithmic.com:443 host, the code being the site (za, de, hk, ie, in, nyc, br, kr, sg, au, jp).
  • Colo75, listed last and labelled colocation only: its hostname resolves to a private network, so an ordinary internet connection can only time out on it. Keep Chicago unless your machine is hosted inside that facility.
  • Custom appears in the select only as the reflection of a URL outside the list (UAT, manual entry, legacy profile); selecting it rewrites nothing.
  • Fetch live system list from gateway queries the URL currently typed; the returned list is tied to that URL and disappears if you change the gateway.

Limits and pitfalls

  • A free Rithmic demo with live market data cannot connect: Rithmic excludes demo accounts from the R | Protocol API. Prop-firm accounts on the same system names work because they are paid accounts with a data subscription.
  • Rithmic allows one concurrent market-data session per login: close R | Trader Pro or another platform first, or buy the firm's second-login add-on.
  • Rithmic Test is for development only; its feed is throttled and partially synthetic.
  • rp_code 13 only says the login was refused at that step; it does not tell whether the user, the password, the system name or the entitlement is the cause. The preflight diagnostic separates them.
  • Market data is billed by the provider and the firm; the app does not include a data subscription.

This page in other languages

Frequently asked questions

Which system name do I type for a prop firm not in the list?
Choose Custom (Rithmic), enter the gateway, then use Fetch live system list from gateway and pick the system the firm gave you. The live list from the gateway has authority over the built-in catalog.
Will Tokyo be faster than Chicago from Asia?
Not necessarily. The access point changes the network route, not the systems served. Measure with the preflight diagnostic before switching, and keep Chicago (core) as the reference.
Why is the Access point select greyed out?
The system name is Rithmic Test, which only exists on the dedicated UAT gateway. Moving it to a production access point would fail at login.

Keep reading

Strategy researchTest a trading strategy, from observation to challenge rulesDefine an observation, question it with the copilot, write a rule and explore costs, drawdown and fictional challenge limits in an interactive example.Quant · Start hereQuant trading for beginners: from idea to backtestDefine a testable rule, choose suitable data and evaluate later periods after costs.Order flow · HubOrder flow trading: the complete guideThe hub. What order flow is, what it shows — aggression, delta, imbalance, absorption, liquidity — and the tools that read it, each linked to a full guide.