Insights · Technology
How brokers connect to liquidity: FIX API vs bridge
By Rohan Mehta, Head of Technology & Connectivity · 12 April 2026
Brokers connect to liquidity in three main ways: a direct FIX API session, a liquidity bridge that plugs MT4, MT5 or cTrader into an external feed, or a custom integration. Each routes orders to an aggregated pool of bank and non-bank liquidity — the choice is about latency, control and which platform the broker runs.
Key takeaways
- FIX API is the institutional standard: a direct, low-latency session preferred by funds and firms running their own execution stack.
- A liquidity bridge connects a trading platform (MT4/MT5, cTrader) to an external provider and translates orders into FIX under the hood.
- Both connect to the same thing — an aggregated feed of tier 1 bank and non-bank liquidity with credit and risk applied.
- Most brokers reach tier 1 liquidity indirectly, through a Prime of Prime, integrating once instead of onboarding each bank.
- Latency depends on protocol, colocation and network path — proximity to the matching and aggregation engine matters more than the label on the connection.
The connection options
Four ways a broker plugs into a liquidity feed
Whatever the label, every connection does the same job: it carries streaming prices in one direction and orders, fills and position updates in the other, between the broker's environment and the liquidity provider's aggregation engine. The differences are in the protocol, the latency profile and how much the broker has to build.
1. FIX API
FIX (Financial Information eXchange) is the messaging protocol institutional markets run on. A direct FIX session gives the broker or fund a raw, low-latency pipe to the provider: it can consume full market-depth pricing, send orders with precise instructions, and receive execution reports programmatically. It is the most flexible and fastest option, and the natural choice for firms that operate their own trading, risk or smart-order-routing systems. The trade-off is that FIX assumes engineering resources — someone has to build and certify the integration.
2. MT4 / MT5 liquidity bridge
Most retail-facing brokers run MetaTrader 4 or MetaTrader 5. A liquidity bridge sits between the platform's server and the provider, translating MetaTrader orders into FIX, streaming aggregated pricing back into the platform, and keeping positions in sync. This is how a broker moves its book onto straight-through, A-book execution without replacing the platform its clients already know. Modern bridges also carry risk rules, mark-ups and routing logic.
3. cTrader and other platforms
cTrader and similar ECN-style platforms are built around external liquidity and often speak FIX natively or connect through a lighter bridge. The pattern is the same — the platform distributes aggregated pricing to end clients while orders route out to the provider's pool.
4. Custom integration
Larger brokers, funds and fintech firms sometimes build directly against the provider's FIX or REST endpoints — wiring liquidity into a proprietary front end, an order-management system or an internal aggregator. This gives total control over routing and presentation at the cost of building and maintaining the stack. Our technology and execution pages set out what a custom integration involves.
| Connection | Best for | Trade-off |
|---|---|---|
| FIX API | Funds, prop desks, firms with their own execution stack | Lowest latency & most control; needs engineering to build and certify |
| MT4 / MT5 bridge | Brokers distributing to retail-style clients on MetaTrader | Fast to deploy on a familiar platform; bridge adds a hop and a dependency |
| cTrader / ECN platform | Brokers wanting a native ECN front end | Built for external liquidity; smaller ecosystem than MetaTrader |
| Custom integration | Fintechs and large brokers with proprietary systems | Total control over routing & UX; most to build and maintain |
Illustrative, structural comparison. Specific capabilities vary by provider, platform version and integration.
Under the hood
How aggregation and routing work
The connection is only the last mile. Behind it, a Prime of Prime aggregates multiple bank and non-bank sources into one order book, then routes each order to the venue offering the best available price. The broker sees a single, unified feed; the engine is doing the sorting.
- Aggregation — pricing from several tier 1 banks, ECNs and market makers is combined into one consolidated book, so the broker consumes a deeper, tighter feed than any single source could provide.
- Best bid / offer — the aggregator continuously builds the best available bid and offer across all sources, layering depth behind the top of book.
- Smart order routing — when an order arrives, it is routed to the source (or split across sources) that can fill it best, then passed straight through with no dealing desk taking the other side.
- Credit & risk — the provider applies credit limits, margin and risk parameters at this layer, which is what lets a broker trade without a direct bilateral facility at each bank.
This is the core of the Prime of Prime model and our liquidity solutions: many fragmented sources become one institutional feed you connect to once. For a plainer walk-through of the aggregation step, see the glossary.
Latency basics
Latency, colocation and the network path
Latency is the round-trip time between sending an order and receiving a fill. In fast markets it decides whether you trade the price you saw. Three things drive it, and none of them is simply "FIX vs bridge":
- Protocol overhead — a direct FIX session carries less overhead than an order that first passes through a platform and a bridge, so all else equal FIX is quicker. In practice the difference matters most to latency-sensitive strategies.
- Colocation — hosting your trading servers in the same data centre as the provider's aggregation and matching engine (commonly major financial hubs such as Equinix LD4 in London or NY4 in New York) removes network distance, which is usually the largest single source of latency.
- Network path — cross-connects and direct fibre between your environment and the engine beat routing over the public internet. A well-placed bridge on a short path can outperform a poorly located direct connection.
The practical takeaway: proximity to the engine and a clean network path often matter more than the protocol label. Ask a prospective provider where their engine is hosted and what colocation and cross-connect options exist.
Getting connected
What onboarding looks like
From first conversation to live routing, connecting to an institutional liquidity feed follows a predictable path.
Scope & onboard
Agree entity type, asset classes, expected volumes and connectivity, then complete KYC, due diligence and the commercial and credit terms.
Provision & configure
Receive FIX session credentials or a bridge configuration, with symbols, price feeds, mark-ups and risk parameters set for your book.
Certify in UAT
Test the integration in a staging environment — pricing, order types, fills, rejections and reporting — until the session is certified.
Go live & monitor
Switch to production, route live flow straight through, and track execution quality, exposure and P&L with the provider's tools.
Common questions
Connecting to liquidity, answered
How do brokers connect to tier 1 bank liquidity?
Most brokers connect to tier 1 bank liquidity indirectly, through a Prime of Prime provider that already holds the bank prime brokerage relationships. The broker integrates once — usually over a FIX API session or a platform bridge — and the Prime of Prime aggregates the underlying bank and non-bank feeds, applies credit and risk parameters, and routes orders straight through to the venues. Going direct to a bank requires meeting the bank's capital, credit and volume thresholds, which is out of reach for most firms.
What is a liquidity bridge?
A liquidity bridge is software that connects a trading platform such as MetaTrader 4, MetaTrader 5 or cTrader to an external liquidity provider. It translates the platform's orders into the provider's protocol (typically FIX), streams aggregated pricing back into the platform, and passes fills and position updates in both directions. The bridge is what lets a retail-facing platform operate on straight-through, A-book execution against institutional liquidity.
Is FIX API better than a bridge?
Neither is universally better — they solve different problems. A direct FIX API session gives the lowest-latency, most flexible access and is preferred by funds, proprietary desks and firms running their own execution stack. A liquidity bridge is the practical choice for brokers running MT4, MT5 or cTrader, because it plugs institutional liquidity into a platform their clients already trade on. Many brokers use both: FIX for their core routing and a bridge for platform distribution.
Request liquidity
Connect once. Trade an aggregated feed.
Tell us your platform, asset classes, expected volumes and preferred connectivity — FIX or bridge — and our institutional desk will map an integration and come back with a tailored liquidity proposal.