Rithmic: futures connectivity, APIs and account controls

The product family serves several users: traders placing orders, developers building applications, and brokers or FCMs administering accounts. Funding evaluators also use its account-management and simulation tools. These roles share infrastructure but have different production, account and market-data requirements.[1][4]

Rithmic separates initial development from production conformance. Developers can build against Rithmic Test without completing conformance first. Its published process then requires review before connecting to production systems, including Rithmic 01 and Rithmic Paper Trading, and to an FCM ID. After acceptance, live credentials and associated fees are arranged with the broker or FCM. The paper-trading label therefore does not make production API access unrestricted.[2]

Rithmic also publishes third-party connection guides. Their practical value is the environment and account configuration they describe. An integration should be matched to the selected platform version, broker and data entitlement; a product appearing in a directory is only the starting point for that configuration.[9]

The reviewed public material directs pricing, market-data subscriptions and partnership enquiries to the sales team. It did not establish one tariff covering every API, application and brokerage relationship. Rithmic’s API onboarding sequence separately directs developers to their FCM or broker for live credentials and fees. A broker-advertised end-user price should therefore be identified as that broker’s offer, with its included services, rather than republished as Rithmic’s universal price.[7][2]

For a commercial comparison, separate the Rithmic service, the account provider’s charges, exchange-data entitlements and any third-party application licence. A combined customer bill can contain several of these layers. The relevant question is which charges are included under the proposed configuration; an unavailable public price is not a zero charge.

R|Manager supports an FCM, introducing-broker, user and account hierarchy, along with account modes and administrative permissions. Its SFTP interface can automate account and user operations through CSV files. The documented workflow uploads a complete file before moving it into the processing location, then checks the returned error output. This makes the completion record important: a transferred file and a successfully processed account change are different operational states.[4]

Rithmic places risk enforcement in its infrastructure, where configured controls can continue operating when a trader’s application disconnects. The FCM-facing material also describes position monitoring, account restrictions and reports for downstream workflows. The brokerage’s implementation needs to preserve the hierarchy under which those controls operate.[6]

A useful acceptance exercise follows a complete order through submission, acknowledgement, amendment or cancellation, execution and reconciliation. Reconnect handling should establish the last known order state before another instruction is sent.

The contact page says response times vary with ticket volume and urgent platform issues receive priority. It publishes no fixed response clock. An account restriction or risk rejection may also require the broker or FCM. Identifying the account provider, environment, timestamps and order identifiers gives the receiving team a more useful incident record than the application name alone.[7][5]

This is a technology-provider profile. Rithmic’s broker-facing model operates through FCM relationships: the FCM manages accounts and delegates authority to the introducing broker. Trading eligibility, clearing arrangements and the customer’s account permissions belong to that relationship. Access to the software alone does not establish an exchange account or clearing membership, and this profile makes no financial-authorisation claim for Rithmic’s software supply.[5]

The official contact page identifies Rithmic, LLC at 1 Ramland Road, Orangeburg, New York. R|Trader Pro, R|Manager and the API families are products within its trading and administration offering.[7][1]

Operator

Rithmic, LLC

Service scope

Market data, order routing, account administration and server-side risk infrastructure for futures trading applications and account providers.

Customer types

Futures commission merchants; Introducing brokers; Trading application developers; Funding evaluators; Traders accessing broker or FCM accounts

Delivery

Hosted; API

Pricing publication

Not disclosed

Platforms

R|Trader Pro; R|Manager; R|Trade Execution Platform; Exchange Simulator

Integrations

R|API+; R|Protocol API; R|Diamond API; SFTP account-operation interface

Pricing scope

No universal tariff established; pricing, market-data and subscription enquiries use the published sales and billing routes.

Implementation

API development uses a test environment, followed by conformance for production. Live credentials and fees are arranged with the broker or FCM; Diamond has additional infrastructure and eligibility requirements.

Support

Topic-based public forms; the contact page says response time depends on ticket volume and prioritises urgent platform issues.

Permissions and regulatory scope

Technology supply through broker and FCM relationships. No financial-services authorisation is asserted for Rithmic; client account permissions and clearing arrangements are separate.

Provider metadata checked 20 Oct 2026Source 1Source 2Source 3Source 5Source 7Source 4

The Exchange Simulator uses live exchange data with a simulated matching engine. It can support strategy practice and application development, while simulated fills remain separate from live queue position and execution outcomes. Its page advertises a single 14-day trial per signup, followed by a paid continuation route. R|Trader Pro and third-party platforms are supported for the demo; web and mobile trading interfaces are excluded from demo access.[8]

The simulator page publishes weekday maintenance from 5:20pm to 5:45pm Eastern Time, Monday to Friday, and weekend maintenance from Friday night until approximately noon Eastern Time on Sunday. Those are the page’s stated maintenance windows, not an uptime commitment for every separately contracted service.[8]