Skip to content
Terminal Ledger Desk
Directory

Mt5 Ctrader Bridge Dealer Architecture

Spotware cTrader Open API (Protobuf) vs cTrader FIX 4.4: Quotas, Auth & Latency

Spotware cTrader uniquely ships every live retail and institutional trading account with both OAuth2 Google Protobuf Open API access (50 msg/sec) and direct FIX 4.4 QUOTE/TRADE credentials—each suited to distinct quant workloads.

By Marcus Thorne, CQFReview not recorded · Updated
Spotware cTrader Open API (Protobuf) vs cTrader FIX 4.4: Quotas, Auth & Latency — Terminal Ledger Desk 2026 quantitative & supervisory data card
Terminal Ledger Desk (MetaTrader 5, cTrader & Liquidity Bridge Server Topology & Execution Logs): Protobuf OAuth2 (50 req/s) vs direct LD4 FIX 4.4 QUOTE/TRADE sockets and Tag 721 hedge closing.Source: Terminal Ledger Desk Institutional Research DeskLicense: CC-BY-4.0

On most multi-asset brokerages, requesting direct FIX 4.4 API credentials requires a $50,000 minimum deposit and $500/month connectivity minimums. Spotware cTrader broke that barrier by baking two native API stacks into every single account across cTrader Desktop, AUS Global cTrader, and Skilling cTrader: cTrader Open API (Google Protocol Buffers over TLS TCP / WebSockets) and cTrader Native FIX 4.4 (QUOTE + TRADE sockets). Choosing the wrong one for your strategy hits hard rate-limit walls or misses critical account metadata!

cTrader Open API (Protobuf v2): Rich Account Metadata & 50 req/s Quotas#

Built on compact binary Google Protocol Buffers (ProtoOAPayloadType) similar to gRPC streaming frameworks, cTrader Open API authenticates via OAuth 2.0 (ClientId, ClientSecret, AccessToken) over Port 5035 (Binary TLS TCP) or Port 5036 (WebSocket WSS for browser apps):

  • Strengths: One single multiplexed TLS connection manages multiple ctidTraderAccountId sub-accounts simultaneously, queries historical M1..MN1 trendbars and raw tick history (ProtoOAGetTickDataReq), modifies Server-Side StopLoss / TakeProfit and TrailingStop flags directly on open positions, and reads exact dynamic margin tiers and swap schedules!
  • Hard Rate-Limit Quotas (Enforced per Connection): Spotware enforces 50 requests per second for non-historical trading/subscription messages and 5 requests per second for historical bar/tick queries! Exceeding 50 msg/s triggers ProtoOAErrorRes (REQUEST_FREQUENCY_EXCEEDED).
Dual-track Spotware cTrader programmatic architecture comparing OAuth2 Protobuf Open API (Port 5035) against dual QUOTE/TRADE FIX 4.4 sockets (Port 5211)
Dual-track Spotware cTrader programmatic architecture comparing OAuth2 Protobuf Open API (Port 5035) against dual QUOTE/TRADE FIX 4.4 sockets (Port 5211)Verified Exhibit

cTrader Native FIX 4.4: Colocated Low-Latency Depth & Execution Focus#

Click Settings -> FIX API inside any cTrader terminal and the platform displays immediate credentials (SenderCompID, TargetCompID=cServer, SenderSubID=QUOTE / TRADE, Host, Port 5201/5211 Plain/TLS) for two dedicated FIX 4.4 sessions:

  • QUOTE Session (SenderSubID=QUOTE): Subscribes via MarketDataRequest (35=V) to receive MarketDataSnapshotFullRefresh (35=W) (Top-of-Book 264=1 or Full Depth-of-Market VWAP Ladder 264=0 via 35=X!).
  • TRADE Session (SenderSubID=TRADE): Submits NewOrderSingle (35=D), OrderCancelRequest (35=F), and queries OrderMassStatusRequest (35=AF) + RequestForPositions (35=AN) with minimal protocol overhead when colocated inside Equinix LD4 near Spotware core!

Critical cTrader FIX Limitation (No Native SL/TP Tags on 35=D): Standard cTrader FIX 35=D operates like institutional interbank FIX—it does NOT accept retail StopLoss or TakeProfit attributes inside NewOrderSingle! In FIX mode, your engine must manage separate resting Stop (40=3) and Limit (40=2) working orders (and cancel the sibling OCO-style upon 35=8 fill)!

Quantitative Distribution · cTrader FIX 4.4 API (FIX)
cTrader FIX 4.4 API (FIX)
01Wire SerializationASCII Tag=Value…02Server-Side SL/TP & TrailingNo (Must manage…03Hedging Position Close KeyPosMaintRptID (…
Capability / Engineering DimensioncTrader FIX 4.4 API (FIX)cTrader Open API (Protobuf)cTrader Automate (cBots C#)
Wire SerializationASCII Tag=Value\x01 (TLS 5211)Binary Google Protobuf (5035/5036)Native .NET In-Terminal / Spotware Cloud
Authentication MechanismPer-Account SenderCompID + PasswordOAuth 2.0 (Multi-Account SaaS ready)Logged-in cTrader Desktop / Cloud ID
Server-Side SL/TP & TrailingNo (Must manage separate 40=3/2 OCO)Yes (stopLoss, trailingStopLoss)Yes (ExecuteMarketOrder params)
Historical Candles & Tick FetchNot Supported (Live stream only)Yes (5 req/sec historical quota)Yes (Bars / Ticks native series)
Hedging Position Close KeyPosMaintRptID (Tag 721) on 35=DProtoOAClosePositionReq(positionId)ClosePosition(position)

cTrader API Ecosystem Comparison: Open API vs FIX 4.4 vs C# Automate (cBots)#

Selecting the right programmatic interface across HFT execution, multi-account copy-trading SaaS, and indicator-driven strategies.

Formula or model from the articleNot independently verified
Bucket_Tokens(t) = min( Capacity_50, Tokens(t_prev) + 50.0 * (t - t_prev) ) - 1.0 [Open API Trade Limiter]
  • FIXCloseHedge : NewOrderSingle(35=D, Side=Opposite, OrderQty=Leaves, PosMaintRptID(721)=OpenPositionID)
  • Worked Rate-Limit Budget for a 12-Pair Multi-Symbol Market Maker on Open API vs FIX:
  • Open API : 50 req/sec / 12 pairs = max 4.16 quote updates/sec per pair (Throttles during NFP -> Use FIX 4.4 for HFT!)
  • Hybrid : Historical warmup of 12 pairs * 4 timeframes = 48 calls / (5 req/s) = 9.6 seconds clean boot via Open API.

Why Port 5035 Raw Protobuf TCP Beats Port 5036 WebSockets by 0.8–2.5 ms#

Developers using Python or Rust SDKs against cTrader Open API often default to wss://live.ctraderapi.com:5036 WebSockets out of convenience. On a colocated LD4 Linux server, switching to raw length-prefixed (4-byte Big-Endian uint32 length + ProtoMessage) TLS TCP on Port 5035 eliminates HTTP/1.1 Upgrade framing and WebSocket payload masking (XOR), shaving 0.8 to 2.5 milliseconds off burst p99 latency! Furthermore, Open API moves through Spotware global proxy layer (~3–12 ms), whereas direct broker-assigned *cTrader FIX `h.p.ctrader.com` endpoints** minimize proxy hops—analyzed alongside our MT5, cTrader & Liquidity Bridge Architecture Guide.

Colocated LD4 wire-to-fill p99 latency across cTrader FIX 4.4 Direct, cTrader C# Cloud cBot, Open API Raw TCP 5035, and Open API WebSocket 5036
Colocated LD4 wire-to-fill p99 latency across cTrader FIX 4.4 Direct, cTrader C# Cloud cBot, Open API Raw TCP 5035, and Open API WebSocket 5036Verified Exhibit

Hybrid Pattern: FIX QUOTE + TRADE Paired With Out-of-Band Open API Reconciliation#

Institutional prop teams trading on cTrader combine both interfaces cleanly: run ultra-lean C++/Rust FIX 4.4 QUOTE + TRADE sockets on the hot execution path, while running a lightweight background Open API Protobuf listener (1 req/min) to audit swap charges, commission tiers, margin changes, and guaranteed server-side emergency StopLoss attachments under UK FCA risk rules!

Size position risk across API accounts in the Algorithmic Kelly Allocation Calculator and Terminal Margin VaR & ES Calculator, and explore all 20 platform deep dives in the MT5, cTrader & Bridge Topic Hub.

Frequently asked questions

How do I close an existing Hedging-account position over cTrader FIX 4.4 instead of opening an opposite hedge?

On a Hedging cTrader account, sending a plain opposite-side NewOrderSingle (35=D) opens a brand-new hedged position! To close existing Position #99182, you MUST include PosMaintRptID (Tag 721=99182) returned in the opening ExecutionReport (or 35=AP PositionReport).

Why did my cTrader FIX MarketDataRequest (35=V) return full incremental updates (35=X) instead of snapshots (35=W)?

In cTrader FIX 4.4, setting MarketDepth (Tag 264) = 1 requests Top-of-Book Spot snapshots (35=W), whereas setting MarketDepth (Tag 264) = 0 requests Full Depth-of-Market ladder updates delivered via MarketDataIncrementalRefresh (35=X) with entry IDs!

Can one cTrader Open API application trade on behalf of 500 different users across multiple cTrader brokers?

Yes! Because cTrader ID (cTID) OAuth 2.0 is federated at the Spotware Open API proxy layer, a single registered Open API ClientId can authenticate tokens across accounts at any participating cTrader broker (subject to per-connection account concurrency caps).

What happens if my Open API client forgets to send ProtoHeartbeatEvent frames?

If no trading or subscription payload flows within the negotiated heartbeat interval (typically 10–25 seconds), failing to transmit ProtoHeartbeatEvent causes the cTrader Open API proxy to terminate the idle TLS socket immediately to reclaim file descriptors.

Publication record

Published
13 November 2026
Updated
14 November 2026
Author
Marcus Thorne, CQF
Review
Review not recorded
Automated fact check
Passed in the stored pipeline record
Source URLs
3 recorded

AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.

Academic & Institutional Attribution

Cite This Research & Embed Live Data Card

Open Attribution License (CC BY 4.0)

Standard academic & institutional research paper citation format.

Marcus Thorne, CQF. (2026, November 14). Spotware cTrader Open API (Protobuf) vs cTrader FIX 4.4: Quotas, Auth & Latency. Terminal Ledger Desk. https://terminalledgerdesk.com/reports/spotware-ctrader-open-api-protobuf-vs-ctrader-fix-4-4-rate-limits
Explore Mt5 Ctrader Bridge Dealer Architecture Hub (20) →

Terminal Ledger Desk Data, Benchmarks & Contributor Records

cTrader Open API (Protobuf) vs cTrader FIX 4.4 Limits | Terminal Ledger Desk