FIX Protocol Guides
How FIX works on a real session, with example messages you can open in the parser. For specific error messages, see FIX troubleshooting; for what changed between versions, see FIX version comparisons; for QuickFIX/J, QuickFIX/n and QuickFIX C++, see the QuickFIX guides.
- FIX Order Lifecycle Explained
How a FIX order moves from New Order Single to fill, cancel, replace or reject, with OrdStatus (39) and ExecType (150) at each step and example messages.
- FIX Session Layer Explained
How the FIX session layer works: Logon, heartbeats and TestRequest, sequence numbers, ResendRequest, gap fill and Logout, with example messages.
- FIXT.1.1 and ApplVerID Explained
How FIX 5.0 sessions use FIXT.1.1: BeginString, DefaultApplVerID (1137) on Logon, ApplVerID (1128) per message and the version codes, with examples.
- How to Read a FIX Execution Report
Read a FIX Execution Report (35=8) field by field: ExecType, OrdStatus, quantities, prices and IDs, how to book fills safely and what differs in FIX 4.2.
- FIX Connectivity Checklist for a New Broker or Venue
A checklist for connecting a new FIX counterparty: documents to collect, session settings to agree, certification tests, go-live and the first week.
- From FIX Execution to Settlement: Allocations, Confirmations and MT54x
How a FIX fill becomes a settled trade: allocations (35=J), confirmations (35=AK), settlement instructions and the MT540-MT548 and sese messages after it.
- FIX Connectivity in GCC and MENA Markets: What to Plan For
Before a FIX session goes live with Gulf and regional brokers and exchanges: trading weeks, holidays, three-decimal currencies, Arabic text and settlement.