The FIX Protocol
The global and open standard enabling the fast, secure and accurate exchange of trading information - reducing complexity, lowering costs and improving reliability across financial markets.
An Introduction to the FIX Protocol
The FIX Protocol is a global, open standard that enables financial institutions to communicate trading information quickly, accurately and securely.
It provides a common “language” that allows firms such as banks, asset managers, exchanges and technology providers to connect and exchange information without needing bespoke connections for each counterparty.
By using a shared standard, the industry reduces cost, complexity and operational risk, while improving speed and reliability. Developed and maintained by the FIX Trading Community, the FIX Protocol has evolved over more than three decades to support a wide range of asset classes and market activities.
Its open, vendor‑neutral nature encourages broad adoption and collaboration, helping firms adapt to new market practices, regulatory requirements and technologies while maintaining efficient and resilient financial markets.
What It Is (and Isn't)
The FIX Protocol is an application‑layer protocol, meaning it defines what business information is being exchanged and what it means, rather than how that information is physically sent across a network.
In practical terms, FIX specifies the structure, content and workflows of trading messages—such as orders, executions and market data—while deliberately remaining independent of any particular network, transport or technology stack.
This separation allows the same FIX business messages to be carried over different transports (for example TCP/IP, multicast or WebSockets), managed using different session models, and encoded in different formats (such as traditional tag‑value, binary or JSON), depending on performance, resilience or integration needs. Details of many of these can be found on our technical standards page.
As a result, FIX can be adapted to a wide range of use cases—from ultra‑low‑latency trading to web‑based and cloud‑native environments—without changing the underlying business meaning of the messages.
How It Works
The FIX Protocol is structured in a layered, modular way to promote reuse, consistency and clarity.
At its core are fields, each identified by a numeric tag and a defined meaning (such as price, quantity or instrument), which form the basic building blocks of all FIX data.
Related fields are grouped into components, which represent logical business concepts (for example, parties, instrument details or allocations) and can be reused across many messages.
Messages are then constructed by combining fields and components to represent specific business events or actions, such as submitting an order, reporting an execution or publishing market data.
Messages are organised into categories (for example, order handling, market data, trade reporting or post‑trade processing), which group related message types and workflows.
This structured approach allows FIX to be both highly standardised and extensible, supporting consistent interpretation while accommodating different asset classes and use cases.
The FIX Protocol initially grew through a series of distinct releases. From 2009, the protocol ("FIX Latest") has been upgraded incrementally through extension packs. These are backwards compatible and can even be used on legacy versions of the Protocol.
Firms are strongly recommended to use FIX Latest. However, to support firms with legacy implementations, FIX Protocol versions 4.2 and 4.4 are still supported by the FIX Trading Community. Other versions are no longer supported but are available in our archive for reference.
How It Evolves
The FIX Protocol is developed through a structured, industry‑driven process that begins with business requirements identified by market participants in FIX working groups.
These groups—made up of buy‑side, sell‑side, venues, vendors and other stakeholders—define the business problem and agree the required workflows and data in plain business terms, which are documented in a formal gap analysis.
This proposal is then translated into detailed technical specifications by FIX's technical standards group and reviewed by FIX's Global Technical Committee to ensure consistency, quality and alignment with existing standards.
The specification then goes through a two to four week public review before being incorporated into the standard.
How the FIX Protocol Saves Money and Reduces Risk
Before the FIX Protocol (FIX) became dominant, firms generally had to build custom point‑to‑point interfaces for each counterparty, maintain multiple proprietary message formats and pay vendor‑specific licensing or integration fees. FIX replaced this with one standard protocol that works across thousands of counterparties and venues, significantly reducing development time, ongoing maintenance costs and vendor lock‑in risk.
Because FIX has been around for over thirty years, there is a vast talent pool of experienced developers, testers, on-boarders, analysts and operations personnel. Plus, FIX is supported by the FIX Trading Community’s expert network of members, ensuring that new asset classes, trading practices, regulatory reporting and post-trade requirements can be accommodated and made available to the industry quickly.
| FIX Protocol | Proprietary APIs | |
|---|---|---|
| Up-front Build Cost | Lower (shared standard, reusable tooling) | Higher (custom per venue/vendor) |
| Ongoing Maintenance Cost | Lower | Higher |
| Counterparty Scaling Cost | Very low marginal cost | Linear (or worse) cost growth |
| Change/Regulatory Cost | Shared across industry | Borne entirely by the firm |
| Vendor Lock-in Risk | Low | High |
| Feature Expansion | Driven by FIX’s >300 firm member base | Borne entirely by the firm |
The FIX Protocol’s Scope and Reach
Asset Class Coverage
Pre-trade Messaging
Trade Messaging
Post-trade Messaging
FIX is also used for regulatory reporting for FINRA TRACE, CTFC, OCC, CIRO (Canada) and ASIC (Australia), and supported by the providers of Europe’s consolidated tapes.
Specifications
FIX Latest
The documents below form the FIX Protocol specification up to extension pack EP284 (later extension packs can be found on our extension packs page)
Machine-readable specifications are also provided below - these cover the full specification up to the latest extension pack
We also recommend FIXimate - the easiest way to navigate the full FIX Protocol specification
Documentation
FIX Latest Specification - Introduction 5.6 MB 5565 downloads
Introduction to FIX Latest and layouts of global components. ...FIX Latest Specification - Infrastructure 743 KB 2555 downloads
Normative specification of the infrastructure business area of FIX Latest. ...FIX Latest Specification - Pre-Trade 5.4 MB 2891 downloads
Normative specification of the pre-trade business area of FIX Latest. ...FIX Latest Specification - Trade 3.2 MB 4824 downloads
Normative specification of the trade business area of FIX Latest. ...FIX Latest Specification - Order State Changes 1.2 MB 3606 downloads
Normative specification of the order state changes of FIX Latest. ...FIX Latest Specification - Post-Trade 4.7 MB 2751 downloads
Normative specification of the post-trade business area of FIX Latest. ...Time Precision Technical Addendum 580.93 KB 6164 downloads
Time Precision Technical Addendum. This Technical Addendum addresses the time precision...Machine-Readable
User Defined Fields
The FIX Protocol has a number of reserved field ranges for user defined fields:
- Tag numbers in the user defined range of 5000 to 9999 have all been allocated (details can be found below).
- User defined fields in the range 8000-8499 are reserved by the GTC for the support of regulatory requirements in supported legacy versions of FIX. User defined fields in the range 8500-8999 are also reserved for future assignment by the GTC.
- In December 2009 the Global Technical Committee Governance Board approved the use of tag numbers in the 20000 to 39999 range for use as user defined tags to be used bilaterally between parties. These tags do not need to be registered.
The GTC's policy with regards to user defined fields is for the community, where possible, to use tags, components or repeating groups from the latest Extension Pack in their legacy FIX implementation when these meet the requirements, as opposed to customised extensions through user defined fields, components or repeating groups.
User Defined Fields - Excel 717.50 KB 3642 downloads
At this time the available tag numbers in the user defined range of 5000 to 9999...
User Defined Fields - PDF 3.27 MB 7930 downloads
At this time the available tag numbers in the user defined range of 5000 to 9999...External Codelists
Legacy Versions
FIX 4.2 Specification with Errata 20010501 1.34 MB 4869 downloads
FIX 4.2 Specification with May 1, 2001 Errata. ...FIX 4.4 Specification with 20030618 Errata 7.50 MB 11917 downloads
Complete Vol. 1 to 7 of the FIX 4.4 Specification with June 18, 2003, Errata. ...Other versions of the FIX Protocol are no longer supported. Legacy specification documents can be found here.
