FIX API access to institutional liquidity
Connect your stack over FIX 4.4 or 5.0 and execute against aggregated Tier-1 pricing — production-parity sandbox before commitment, documented message coverage, and certification run by an engineer rather than a ticket queue.
How it works
What the integration actually involves
Most FIX integrations fail on the unglamorous parts: session management, symbol mapping and what happens when the connection drops. Those are the parts documented here.
Sessions and message coverage
FIX 4.4 and 5.0 native. Quote, order entry, execution report and drop-copy sessions, with the supported message types and tags documented up front rather than discovered during certification.
Production-parity sandbox
Sandbox credentials issued before commercial commitment, running the same behaviour as production — not a stub that agrees with everything. You certify against what you will actually trade on.
Symbol mapping and reconnection
Symbol mapping agreed and documented for your instrument set. Sequence-reset and reconnection behaviour specified, so a dropped session at 03:00 is a known procedure instead of an incident.
Alternatives when FIX is not the fit
MetaTrader-based venues get a battle-tested MT5 bridge; HTTP-first stacks get REST plus a low-latency WebSocket with OpenAPI docs. Many firms start on the bridge and add FIX as they scale.
Before you connect
What we need to start certification
Connectivity follows onboarding — your entity is a client first, then we integrate. The technical requirements below are what make certification fast once that is done.
- A completed institutional onboarding, since credentials are issued to an onboarded entity.
- Your FIX engine and version, or the OMS/EMS you are connecting from.
- Source IPs for allow-listing, and whether you need cross-connect or will reach us over the public internet.
- The instrument set you intend to trade, so symbol mapping is prepared before certification rather than during it.
- A named technical contact who can run the certification session — this is the single biggest driver of how fast it completes.
Technical questions
What engineering teams ask
- Which FIX versions and message types are supported?
- FIX 4.4 and 5.0 native, covering quote, order entry, execution report and drop-copy sessions. The supported message types and tags are documented and shared before certification, so you are not reverse-engineering behaviour from rejects.
- Is the sandbox the same as production?
- Yes — that is the point. A sandbox that behaves differently from production moves the discovery of bugs to your first live session. Credentials are issued before commercial commitment.
- How long does certification take?
- Typically days rather than weeks once onboarding is complete and symbol mapping is agreed. What stretches it is almost always waiting on the counterparty's technical contact, which is why we ask for a named one.
- Are we buying a liquidity feed over FIX?
- No. The FIX session is how your onboarded entity sends us orders to execute — we act as intermediary in the execution of your transactions, which is what our FSC Investment Dealer licence authorises. It is a connection to execute through us, not a wholesale feed to redistribute.
Ready to start certification?
Talk to our institutional team. Sandbox credentials are issued before any commercial commitment.
