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.

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
ctidTraderAccountIdsub-accounts simultaneously, queries historicalM1..MN1trendbars and raw tick history (ProtoOAGetTickDataReq), modifies Server-SideStopLoss / TakeProfitandTrailingStopflags directly on open positions, and reads exact dynamic margin tiers and swap schedules! - Hard Rate-Limit Quotas (
Enforced per Connection): Spotware enforces50 requests per secondfor non-historical trading/subscription messages and5 requests per secondfor historical bar/tick queries! Exceeding50 msg/striggersProtoOAErrorRes (REQUEST_FREQUENCY_EXCEEDED).
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:
QUOTESession (SenderSubID=QUOTE): Subscribes viaMarketDataRequest (35=V)to receiveMarketDataSnapshotFullRefresh (35=W)(Top-of-Book264=1or Full Depth-of-Market VWAP Ladder264=0via35=X!).TRADESession (SenderSubID=TRADE): SubmitsNewOrderSingle (35=D),OrderCancelRequest (35=F), and queriesOrderMassStatusRequest (35=AF)+RequestForPositions (35=AN)with minimal protocol overhead when colocated inside EquinixLD4near 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)!
| Capability / Engineering Dimension | cTrader FIX 4.4 API (FIX) | cTrader Open API (Protobuf) | cTrader Automate (cBots C#) |
|---|---|---|---|
| Wire Serialization | ASCII Tag=Value\x01 (TLS 5211) | Binary Google Protobuf (5035/5036) | Native .NET In-Terminal / Spotware Cloud |
| Authentication Mechanism | Per-Account SenderCompID + Password | OAuth 2.0 (Multi-Account SaaS ready) | Logged-in cTrader Desktop / Cloud ID |
Server-Side SL/TP & Trailing | No (Must manage separate 40=3/2 OCO) | Yes (stopLoss, trailingStopLoss) | Yes (ExecuteMarketOrder params) |
| Historical Candles & Tick Fetch | Not Supported (Live stream only) | Yes (5 req/sec historical quota) | Yes (Bars / Ticks native series) |
| Hedging Position Close Key | PosMaintRptID (Tag 721) on 35=D | ProtoOAClosePositionReq(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.
- 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.
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
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-limitsRelated Mt5 Ctrader Bridge Dealer Architecture & Institutional Briefings
Explore Mt5 Ctrader Bridge Dealer Architecture Hub (20) →Mt5 Ctrader Bridge Dealer Architecture
MetaTrader 5, cTrader & Liquidity Bridge Server Topology & Execution Logs GuideMt5 Ctrader Bridge Dealer Architecture
MT5 Netting vs Hedging Position Ledgers: Orders, Deals, CloseBy & Margin MathMt5 Ctrader Bridge Dealer Architecture
OTC FX Last-Look Hold Windows: FX Global Code Principle 17 & Firm Liquidity TCAMt5 Ctrader Bridge Dealer Architecture
Margin Stop-Out Liquidation Engines: Tick Evaluation, Smart Partial Close & NBPMt5 Ctrader Bridge Dealer Architecture
PAMM, MAM & Copy-Trading Engines: Master-to-Child Allocation Latency & SlippageMt5 Ctrader Bridge Dealer Architecture
FX Swap Rollover Engines: Triple-Wednesday T+2 Settlement & Tom-Next Batch MathMt5 Ctrader Bridge Dealer Architecture
WebAssembly & WebGL Browser Trading Terminals: Holding 16.6ms 60-FPS Frame BudgetsMt5 Ctrader Bridge Dealer Architecture
Prime-of-Prime Net Open Position (NOP) Gates: Credit Throttling in FX BridgesMifid Rts6 Pretrade Kill Switch Controls
NMS Limit Up-Limit Down (LULD) Plan: Reference Price Bands, Limit States & 5-Minute PausesMifid Rts6 Pretrade Kill Switch Controls
CME Globex Velocity Logic & Dynamic Circuit Breakers: Sub-Second Futures Volatility GuardsMifid Rts6 Pretrade Kill Switch Controls
CFTC Regulation 1.73: FCM Automated Pre-Execution Clearing Credit Screens & Give-Up LimitsMifid Rts6 Pretrade Kill Switch Controls
Options Market-Maker Mass Quote Risk (MMR): Rolling Delta, Vega & Percentage-Swept Purge Triggers
Terminal Ledger Desk Data, Benchmarks & Contributor Records
CC BY 4.0 Open Data
Open Institutional Datasets (CSV / JSON) →
Download desk-compiled quantitative series & schemas.
2026 Reference Matrix
2026 Institutional Benchmarks & Thresholds →
Statutory capital, clearing, margin & rate conventions.
Editorial Records
Authors & Review Records →
View named contributors where those records are available.
Complete Index
Master Research & Dossier Archive →
Browse all published briefings by topic pillar & date.
