Execution / Brokers
FIX API brokers: how to choose one
“We offer a FIX API” is a starting point, not a specification. Almost every institutional broker says it; very few will tell you the protocol version, the venue behind the price, the commission, and what happens to your order when the market is fast. This page is the checklist we use before routing a system anywhere.
What a FIX API broker actually provides
A FIX API broker exposes a gateway that speaks the FIX protocol — normally FIX 4.4 in FX and metals — so your system can send orders and receive fills directly, without a platform in between. What that means commercially is that the broker stops being a counterparty in the pricing decision and starts being a route plus a commission.
The account is only one half of the arrangement. The other half is your FIX API connector: the software that holds the session, maps your orders into protocol messages and reconciles the fills. A broker can only be judged once something is actually speaking to it.
The gateway
An endpoint you connect to, with credentials, a session and a documented message set. Ask for the version, not just the word “API”.
The venue
Where your price actually comes from: a prime-of-prime, an ECN pool, or the broker’s own book. This determines the fills.
The commercial model
Commission per lot, any minimum, and whether the spread you see is the venue’s or the broker’s markup.
The nine questions to ask before you open the account
A broker that answers these clearly is worth a test. A broker that deflects any of them has told you something too.
1. Protocol version
FIX 4.4, or something older? Version determines which order types and fields you can use.
2. Order types
Are fill-or-kill and immediate-or-cancel native, or emulated by the platform layer?
3. Route
Is the order internalised, or passed to a liquidity provider? Does the answer change by size?
4. Venue
Which pools price the instrument, and can you restrict routing to one of them?
5. Commission
Stated per lot in currency, not “from”. Plus any minimum charge or minimum volume.
6. Server location
Where is the gateway hosted, and can you co-locate near it? See what colocation changes.
7. Session limits
Maximum order rate, heartbeat interval, and whether they throttle or disconnect on burst.
8. Rejections
What does a rejection look like in the ExecutionReport, and are reject reasons documented?
9. Support
Who answers a FIX-level question at 03:00, and how quickly? This is where retail-grade brokers fail.
FIX API, cTrader and MT4/MT5 bridges
Three arrangements get called “a FIX API account”, and they behave very differently. Understanding the difference saves a lot of money spent on a strategy that was never going to work on the chosen route.
Direct FIX API
Your system talks to the gateway. No platform, no bridge. The shortest path and the most control; requires a connector.
cTrader / FIX-API venues
The venue supports both a retail-friendly platform and an API route. Useful when you want one account that can serve both — see cTrader and the FIX API.
MT4/MT5 bridged
The platform sits in front of the gateway. Convenient, widely supported, and it reintroduces delay plus an opaque fill.
Venue quality is not a protocol feature
Two brokers can both run FIX 4.4 on modern infrastructure and deliver completely different results, because the protocol describes how an order travels and says nothing about the market it lands in. A correctly implemented session pointed at a thin pool will fill you badly, reliably.
That is why the venue question comes before the technology question. In FX and metals there is no single central exchange, so the pools you can reach are the market; the industry’s conduct expectations for that structure are set out in the FX Global Code.
Depth
How much size can be filled at the quoted price before it moves. Ask for the top-of-book depth, not the headline spread.
Diversity
One provider is one opinion. Pools that aggregate several are structurally harder to pick off.
Behaviour in news
Widening is normal; vanishing is not. Test the venue on a scheduled release before you fund it properly.
Pricing: commission, spread and minimums
A FIX API account normally prices as commission plus the venue’s raw spread, rather than one bundled spread. That is better for arithmetic because the two costs are separable and measurable — but it only helps if the commission is stated plainly.
Commission
Fixed per lot. It should be identical on every trade; variable commission is a spread markup wearing a different hat.
Raw spread
Whatever the venue quotes. Sample it during a news event as well as at 10:00, or the average is meaningless.
Minimums
Account size, monthly volume or platform fee. A minimum volume requirement can quietly make a small account uneconomic.
Red flags
None of these is proof of misconduct, but each one is a reason to slow down.
Marketing-page latency
“Zero latency” and “fastest fills” without a measurement methodology. Latency is a number with a definition or it is advertising.
No version, no docs
If the FIX specification is not available on request before you deposit, the API is unlikely to be the product they care about.
Commission “from”
A range that only resolves after you have funded the account is a range that will resolve in the broker’s favour.
No rejection story
A venue that claims it never rejects orders is telling you it always fills them, which is not the same thing.
Bridged, called direct
Ask one question — “is MT4 or MT5 between my system and the gateway?” — and listen carefully.
Minimum volume, high
Requirements designed for institutional flow disqualify a retail-sized account. Better to know before, not after.
How XTRSK chooses a route
XTRSK reviews venue, broker and server location against the strategy before an account trades, and the systems run over FIX 4.4 with direct market access. PULSE-X takes fill-or-kill orders on a controlled latency budget; NIC-X takes displaced prints or nothing at all. The routing review is why the live account is published — the execution can be checked, not assumed.
FIX API broker questions
Do I need a FIX API to be profitable?
No. Plenty of strategies make money on ordinary accounts. The FIX API matters when the strategy depends on the difference between the quoted price and the filled price.
Is a FIX API account expensive?
Commission is usually comparable to a tight spread, and there is no separate licence fee for the protocol. The real cost is the engineering in your connector.
Can I use a FIX API with a small account?
Sometimes. The constraint is usually a broker minimum or a monthly volume requirement rather than the protocol itself. Check before funding.
Which FIX version should I ask for?
Version 4.4 for FX and metals. It is the current practical standard for order routing and carries the time-in-force values you want.
How do I test a broker before committing?
Ask for the specification, open a small live account, log requested versus filled price across a volatile session, and count rejections. See how to evaluate execution.
Further reading
For the protocol specification referenced throughout, see the FIX Trading Community standards and the FIX 4.4 specification. For market-conduct expectations, see the FX Global Code.
This page describes how to evaluate a broker; it is not a recommendation of any firm and it is not investment advice. Trading leveraged FX and metals involves significant risk of loss.
Chat with XTRSK
Chat ready
Start a chat and the XTRSK team will be notified immediately.