# cTrader Open API (Protobuf) vs cTrader FIX 4.4 Limits

> Compare Spotware cTrader Open API (Google Protobuf over TCP/WebSocket + OAuth2) against native per-account cTrader FIX 4.4 sessions, rate limits, and DOM depth.

Canonical: https://terminalledgerdesk.com/reports/spotware-ctrader-open-api-protobuf-vs-ctrader-fix-4-4-rate-limits
Last updated: 2026-11-14T19:50:26.521Z

**Publication:** Terminal Ledger Desk
**Category:** Mt5 Ctrader Bridge Dealer Architecture
**Published:** 2026-11-13T21:55:25.915Z
**Author:** Marcus Thorne, CQF (Certificate in Quantitative Finance (CQF), Low-Latency FIX & Matching Engine Architect)
**Reviewer:** Not recorded

## Answer-first summary

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.

## Key takeaways

- Spotware cTrader grants built-in per-account FIX 4.4 (QUOTE + TRADE) and OAuth2 Google Protobuf Open API access with zero $50k institutional deposit gates.
- cTrader Open API enforces 50 req/s non-historical and 5 req/s historical token-bucket quotas—making it ideal for multi-account SaaS, copy-trading, and swing algos.
- cTrader FIX 4.4 omits retail SL/TP fields on 35=D and closes specific hedged positions by passing PositionID inside PosMaintRptID (Tag 721)!
- Use Port 5035 length-prefixed binary TLS TCP instead of Port 5036 WebSockets on Linux backends to eliminate WebSocket XOR framing overhead.

## Related financial entities

- **Financial Information eXchange (FIX) Protocol** (FIX-4.4) — product: Electronic communications protocol initiated in 1992 for international real-time exchange of securities transaction and market data information.
- **gRPC High-Performance RPC Framework** (GRPC-STREAM) — product: High-performance, open-source universal RPC framework developed by Google that runs over HTTP/2, utilizing Protocol Buffers for structured binary messaging.
- **Spotware cTrader Open Platform Architecture** (CTRADER-CORE) — product: High-performance STP trading platform suite developed by Spotware Systems featuring direct FIX engine access, cAlgo C# algorithms, and Open APIs.

## Analysis

On most multi-asset brokerages, requesting direct [FIX 4.4 API](/software/fix-api) credentials requires a `$50,000` minimum deposit and `$500/month` connectivity minimums. **[Spotware cTrader](/engines/spotware-ctrader-architecture)** broke that barrier by baking **two native API stacks** into every single account across [cTrader Desktop](/platforms/ctrader-terminal-97), [AUS Global cTrader](/platforms/aus-global-ctrader-terminal-3), and [Skilling cTrader](/platforms/skilling-ctrader-terminal-31): **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](/engines/grpc-streaming-framework), **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)](/api/figure?type=flow&title=Spotware%20cTrader%20Dual%20API%20Stack%3A%20Open%20API%20vs%20FIX%204.4&subtitle=Combining%20fast%20LD4%20FIX%204.4%20QUOTE%2FTRADE%20execution%20with%20rich%20Protobuf%20Open%20API%20account%20telemetry&steps=1.%20FIX%204.4%20QUOTE%3A%3APort%205211%20TLS%3A%2035%3DV%20-%3E%20Full%20DOM%2035%3DX%7C2.%20FIX%204.4%20TRADE%3A%3APort%205211%20TLS%3A%2035%3DD%20IOC%2FLimit%20-%3E%2035%3D8%7C3.%20Open%20API%205035%3A%3AProtobuf%20OAuth2%3A%20SL%2FTP%2C%20Swaps%20%26%20Bars%7C4.%20Rate%20Limiter%3A%3AToken%20bucket%3A%20%3C%3D50%2Fs%20Trade%2C%20%3C%3D5%2Fs%20Hist&metrics=OPEN%20API%20QUOTA%3A%3A50%20req%2Fs%3A%3A5%20req%2Fs%20on%20historical%20data%7CPROTOBUF%20WIRE%3A%3A~42%20Bytes%3A%3ACompact%20varint%20binary%20order%7CFIX%20DOM%20DEPTH%3A%3A264%20%3D%200%20%2F%201%3A%3AFull%20book%20%2835%3DX%29%20or%20BBO%20%2835%3DW%29%7CMIN%20DEPOSIT%3A%3A%240%20Gate%3A%3ABuilt%20into%20every%20cTrader%20acct)

## 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](/engines/fix-protocol-standard) 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)!

| Capability / Engineering Dimension | **cTrader `FIX 4.4` API** ([FIX](/software/fix-api)) | **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](/platforms/ctrader-terminal-97) 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.

```formula
Bucket_Tokens(t) = min( Capacity_50, Tokens(t_prev) + 50.0 * (t - t_prev) ) - 1.0 [Open API Trade Limiter]
FIX_Close_Hedge : 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](/reports/mt5-ctrader-liquidity-bridge-server-topology-execution-logs-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](/api/figure?type=bars&title=cTrader%20Programmatic%20Interface%20p99%20Execution%20Latency%20%28LD4%29&subtitle=Order%20dispatch%20to%20ExecutionReport%20%2F%20ProtoOAExecutionEvent%20receipt%20inside%20Slough&steps=cTrader%20FIX%204.4%20Direct%20TLS%3A%3A2.4%20ms%20p50%20%20%205.9%20ms%20p99%7COpen%20API%20Raw%20TCP%20%28Port%205035%29%3A%3A4.8%20ms%20p50%20%20%2011.2%20ms%20p99%20%28Proxy%20hop%29%7COpen%20API%20WebSocket%20%28Port%205036%29%3A%3A6.1%20ms%20p50%20%20%2014.5%20ms%20p99%20%28WS%20frame%29%7CRemote%20Home%20C%23%20Automate%20cBot%3A%3A45.0%20ms%20p50%20%20%2098.0%20ms%20p99%20%28ISP%20WAN%29&metrics=FIX%20SL%2FTP%20RULE%3A%3AClient%20OCO%3A%3ANo%20SL%2FTP%20tags%20on%20FIX%2035%3DD!%7CMULTI-ACCOUNT%3A%3AOpen%20API%3A%3A1%20OAuth%20token%20-%3E%20N%20accounts%7CHEARTBEAT%20REQ%3A%3A10%E2%80%9330%20Sec%3A%3AProtoHeartbeatEvent%20%2F%2035%3D0%7CPOSITION%20ID%20TAG%3A%3ATag%20721%3A%3APosMaintRptID%20closes%20hedge!)

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

Institutional prop teams trading on [cTrader](/software/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](/standards/fca) risk rules!

Size position risk across API accounts in the [Algorithmic Kelly Allocation Calculator](/calculators/algorithmic-kelly-allocation-calculator) and [Terminal Margin VaR & ES Calculator](/calculators/terminal-margin-var-es-calculator), and explore all 20 platform deep dives in the [MT5, cTrader & Bridge Topic Hub](/topics/mt5-ctrader-bridge-dealer-architecture).

- [MT5 Netting vs Hedging Position Ledgers: Orders, Deals, CloseBy & Margin Math](/reports/mt5-netting-vs-hedging-account-position-ledger-margin-recalculation)
- [Prime-of-Prime Net Open Position (NOP) Gates: Credit Throttling in FX Bridges](/reports/prime-of-prime-nop-net-open-position-credit-throttling-in-bridges)

## 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.


## Source URLs

- https://help.ctrader.com/open-api/proxies-endpoints/
- https://help.ctrader.com/fix/
- https://protobuf.dev/programming-guides/proto2/

## Citation

- APA: Marcus Thorne, CQF. (2026). 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
- Canonical article: [Spotware cTrader Open API (Protobuf) vs cTrader FIX 4.4: Quotas, Auth & Latency](https://terminalledgerdesk.com/reports/spotware-ctrader-open-api-protobuf-vs-ctrader-fix-4-4-rate-limits)
- Site research index: [Terminal Ledger Desk](https://terminalledgerdesk.com/llms-full.txt)
