Infrastructure
The protocol both sides already speak
It is not fashionable and it is not going anywhere. For order flow, defined sequence handling and a specified recovery path matter more than an elegant interface.
See it live
One session, three message streams
Price, trade and recovery flows documented with real message samples, so certification starts from what the connection actually sends.
Getting connected
Four stages, and the second one is where problems are found
- 01
Configure
Session credentials, heartbeat intervals, supported message types and the symbol set are agreed and documented before anything connects.
- 02
Certify
A structured test against the real message flow, including the failure paths. Certification is not a formality — it is where the mismatched assumptions surface.
- 03
Shadow
The session runs against live pricing without routing real orders, so behaviour under actual market conditions is observed before anything is at stake.
- 04
Go live
Orders begin flowing, with both sides retaining complete message logs from the first message onwards.
FAQ
FIX API: common questions
6 short answers to what teams ask before a demo.
Because it is what institutional counterparties already speak, and because the sequence and recovery semantics are exactly what an order flow needs. For configuration and reporting a modern interface is better; for order entry FIX remains the right tool.
Yes, and it is worth the time rather than an obstacle to it. Certification is where mismatched assumptions about message handling surface — finding them there is considerably cheaper than finding them in production.
Sequence numbers are used to establish what was missed and a resend recovers it. This is precisely why the protocol persists: the recovery path is defined rather than improvised.
On both sides, in full. When there is a question about what was sent and when, the answer should come from a log rather than from two parties recalling it differently.
Yes, per session. Taking the entire symbol set when you trade twenty instruments wastes bandwidth on your side and processing on ours, and neither of us benefits.
No. BridgeX handles the connection for you and presents one interface. Direct FIX is for desks that want to reach the pricing themselves without a layer in between.
Still have a question?
A specialist will answer it directly, with your set-up in mind.
Ask a specialistBring your engineer to the certification
It is the stage where assumptions about message handling get corrected, and doing it properly is what makes go-live uneventful.