Rithmic API

Rithmic API: R|API+, R|Protocol and conformance

Rithmic is the order-routing and market-data backbone behind many futures prop-firm accounts. Its API lets a program trade those accounts directly, after passing a certification process.

Start now See pricing

Quanify routes orders to Tradovate today; the Rithmic connector is on the roadmap.

R|API+ and R|Protocol at a glance

R|API+ is a native C++ and .NET library used by most desktop platforms. R|Protocol is Protocol Buffers over a persistent connection, usable from any language. There's no REST layer.

Interfaces: R|API+ (C++/.NET library) and R|Protocol API (protobuf over a socket)
Auth: Rithmic login per user, against a named system (the firm's environment)
Identity: Accounts are FCM/IB/account triples; contracts are exchange plus symbol
Orders: Market, limit, stop, stop-limit, brackets; per account, with your own order tag
Events: Order state, fills, position and P&L updates streamed on the session
Access: A passed conformance test before a production login is issued

Production access needs a passed conformance test, and scheduling it takes calendar time.

01
Get test-system access
Test-system logins come first. Everything is built and exercised there.
02
Build the client
A long-running process on a maintained protobuf toolchain, with heartbeat, reconnect and resubscribe handled.
03
Pass conformance
A scripted session: your program connects, subscribes, manages orders and handles edge cases while Rithmic staff watch.
04
Go to production
Production logins follow conformance. Each prop firm is its own Rithmic system with its own login.

The work beyond conformance

After certification, the hard parts look like any broker API.

Session and heartbeat: Miss a heartbeat and the server drops you. Reconnect means log in, resubscribe and re-request working orders.
Order tags: De-duplication, retries and fill matching key on your tag. Sloppy tags make a partial look like a rejection.
Fills, not orders: One order, many fill reports. Build position from fills and reconcile from the snapshot after a gap.
Per-firm systems: Each firm is a separate system and login, so copying across firms means several sessions.
Firm rules: Trailing drawdown and news restrictions are enforced by the firm. The API accepts orders the firm fails you for.
Always connected: The process has to stay up whenever the market is open.

Where Quanify stands on Rithmic

Quanify routes live orders to Tradovate today, and Rithmic is on the roadmap because it opens more prop firms. Routing, sizing and copy logic are broker-neutral; the missing piece is the R|Protocol client and conformance. When it ships, Rithmic accounts take the same per-account multiplier.

If your leader is on Tradovate, connect it today. Building your own Rithmic client means weeks on the test system before the conformance appointment.

Rithmic trade copier

Questions

Common questions

Short answers to what traders ask first. Anything else, the Help Center has it.

What is the Rithmic API?

Rithmic's programming interfaces for trading and market data: R|API+, a native C++ and .NET library, and R|Protocol API, a Protocol Buffers message protocol over a persistent connection. Both let a program log in, subscribe to data, place and manage orders and receive fills on Rithmic-cleared accounts.

Do I need Rithmic's approval to use the API?

Yes. Production access requires passing a conformance test against Rithmic's test system, in which your program has to handle a scripted set of order scenarios correctly. Test-system access comes first; production logins follow conformance.

Does Apex use the Rithmic API?

Apex accounts on Rithmic are reachable through the Rithmic API with a login for Apex's system. Whether an Apex account may be traded by a program or copied is an Apex rule; check the current rulebook.

Does Quanify support Rithmic today?

Not for live order routing yet. Quanify routes to Tradovate today and Rithmic is on the roadmap.

Is a Rithmic trade copier different from a Tradovate one?

The idea is the same: one account's fills become sized orders on the others. Rithmic uses a streaming session per firm system with certified clients; Tradovate uses a websocket session per login.

More on automation

Automated futures trading softwareAutomate a futures strategy on your own Tradovate accounts. A webhook fires, Quanify sizes and checks it, and the order reaches your broker.Futures trading automation for your live accountsAutomate any futures strategy on Tradovate. Send a webhook and Quanify checks, sizes and routes it. No VPS, no glue code.Futures trading bot: run your own strategyA futures trading bot is a strategy plus an executor. Quanify is the executor: your rule fires a webhook, it's checked and sized, the order goes out.NinjaTrader automated trading without NinjaScriptAutomating a NinjaTrader account from a TradingView alert or HTTP request without NinjaScript: how the webhook route works and where Quanify stands.ProjectX API: the platform under TopstepXThe ProjectX Gateway API behind TopstepX: what it exposes, what building on it takes, and how automation and copy trading fit prop-firm rules.TopstepX API: automating without building the execution layerWhat automating a TopstepX account takes, where the hard parts are, and how to route a strategy to it without writing an execution layer.Trading strategies on QuanifyRun your own futures strategy through a webhook, or add a published Quanify strategy with its forward record. How strategies work and are measured.TradingView webhook to broker: alerts to live ordersSend a TradingView alert to one webhook. Quanify resolves the contract, sizes the order, applies your guards and routes it to Tradovate.Tradovate API: what building on it takesWhat building on the Tradovate API involves: OAuth, WebSocket sessions, contract resolution and reconnects, and what you get by skipping it.

Start on a simulated account. Go live when it earns it.

Set up in minutes
Nothing to download
Paper account for testing

By providing your email, you agree to our Terms of Service and Privacy Policy.