FIX 4.4
Connect automated and institutional order workflows through an established trading protocol.
[ Integration overview ]
Receive executable prices, request firm quotes, send orders and consume execution reports without maintaining a separate integration for every venue.
Conceptual flow. Client schemas and supported fields are supplied during integration.
[ What you can build ]
Connect automated and institutional order workflows through an established trading protocol.
Bring quote and execution workflows into broker, exchange, wallet and application backends.
Consume executable two-way prices for the instruments enabled for your relationship.
Request a price for a defined instrument, direction and quantity, with explicit validity.
Submit supported IOC and FOK orders with client identifiers and deterministic responses.
Carry acknowledgement, fill and status information into your customer and operational records.
[ Sandbox access ]
Explore the Stelaxis trading environment and see how pricing, orders, controls and post-trade activity fit together. When you are ready to connect systems, we will scope API access around your actual flow.
[ Available now ]
Use the web environment for an initial product review. API credentials and configured instruments are provided separately for qualified integrations.
[ Request to record ]
Use one integration for the pricing and execution path, then retain the same trade context as the transaction moves into controls, settlement and reconciliation.
Connect to the agreed environment and request the instruments and pricing modes enabled for your account.
Consume an executable stream or send an RFQ with the instrument, side and quantity.
Submit the order or accept the quote and receive a defined acknowledgement, fill or rejection.
Use execution identifiers and reports to support customer records, settlement and reconciliation.
[ Path to production ]
We start with your customer journey, markets, expected sizes, geography and settlement model. That defines the appropriate commercial relationship and a focused technical certification plan.
[ Defined before production ]
Enabled instruments, pricing modes and supported order types.
Expected volumes, typical order sizes and applicable limits.
Supported assets, currencies, wallets and operational cut-offs.
Contracting entity, eligibility, jurisdiction and relevant service terms.
Availability depends on instrument, jurisdiction, client eligibility, onboarding and the agreed contracting entity.
[ Start with your use case ]