What Is the FIX Protocol? Financial Information Exchange Explained

Search Fintrev

Search our guides, reviews and glossary.

The Financial Information eXchange (FIX) protocol is an open, non-proprietary messaging standard that lets financial institutions send trade-related information to each other electronically and in real time. It defines a common format for orders, cancellations, execution reports, quotes, allocations and related messages. A fund, a broker and an exchange can therefore exchange instructions without building a separate custom link for every counterparty.

How the FIX Protocol Works

FIX works in two layers. The session layer manages the connection itself: logging on, sending heartbeats to confirm both sides are alive, numbering every message in sequence and resending anything that was missed. The application layer carries the business content: a new order, a request to cancel, a fill, a rejection.

In the classic tag=value encoding, every message is a string of numbered fields. Each field has the form tag=value, and fields are separated by a non-printing delimiter character (SOH, ASCII 1). A few tags appear in almost every message:

• 8 (BeginString): the protocol version, such as FIX.4.4
• 35 (MsgType): what the message is, for example A for logon, 0 for heartbeat, D for a new order, F for a cancel request, G for a cancel/replace, 8 for an execution report
• 49 and 56 (SenderCompID, TargetCompID): who is sending and who is receiving
• 34 (MsgSeqNum): the message sequence number
• 10 (CheckSum): a simple integrity check at the end

In practice, the software that handles sessions, sequencing and parsing is called a FIX engine, and a live link between two parties is called a FIX connection or FIX session.

Interpreting a FIX Message

Tag 54 is the side (1 buy, 2 sell), 38 is the order quantity, 40 is the order type (1 market, 2 limit), 44 is the limit price and 55 is the symbol. On execution reports, tag 39 (OrdStatus) shows where the order stands: 0 new, 1 partially filled, 2 filled, 4 canceled, 8 rejected.

Example of the FIX Protocol

Hypothetical example, simplified, with | standing in for the SOH delimiter. A fund wants to buy 1,000,000 EUR/USD with a limit of 1.0850. Its system sends a New Order Single:

8=FIX.4.4|35=D|49=FUNDA|56=BROKERB|34=215|11=ORD-0001|55=EUR/USD|54=1|38=1000000|40=2|44=1.0850|...|10=123|

The broker accepts it with an execution report (35=8, 39=0, new). If half the amount fills at 1.0849, a second report shows 39=1 with the fill details; when the remainder fills, a final report shows 39=2. The client order ID in tag 11 (ORD-0001) ties every message back to the original instruction. That chain from new order, through partial fill, to filled is the FIX order lifecycle. Before completion, the fund can send 35=F to cancel or 35=G to amend.

Who Uses the FIX Protocol

Buy-side firms such as mutual funds and investment managers, sell-side investment banks and broker-dealers, stock and futures exchanges and electronic communication networks (ECNs) all use FIX. It is also used for U.S. regulatory reporting and runs over almost any common network technology.

The gain is fewer manual steps. Before FIX, indications of interest could be lost while a caller was on hold or routed to the wrong trader. Electronic messages cut that phone and paperwork traffic and leave a timestamped, sequenced record of each instruction.

In retail and professional forex, some brokers offer a FIX API as an alternative to platform-based trading. It lets algorithmic traders connect their own systems directly to the broker’s pricing and order handling. It appeals to latency-sensitive approaches such as arbitrage, where shaving delay off order routing matters.

Limitations of the FIX Protocol

• Flexibility creates dialects. The standard allows custom tags and optional fields. Counterparties often publish their own “rules of engagement,” so connecting to a new broker usually still requires certification and testing.
• Text encoding is verbose. Tag=value messages are human-readable but larger and slower to parse than binary formats. The community developed alternatives such as FAST and Simple Binary Encoding (SBE) for high-throughput uses.
• Security sits outside the classic protocol. Traditional FIX sessions do not encrypt messages themselves. Firms protect them with private lines, VPNs or TLS.
• It is infrastructure, not protection. FIX transmits a stop-loss or limit order faithfully, but it does not guarantee a fill, a price or the counterparty’s conduct.

FIX vs. Related Terms

• FIX vs. SWIFT: SWIFT is the standard for back-office messaging such as payments and settlement instructions between banks. FIX is the front-office standard for orders and executions.
• FIX vs. an API in general: A broker’s REST or WebSocket API is proprietary to that broker. FIX is a shared standard, so the same message structure works across many counterparties.
• FIX vs. an FX “fix”: In currency markets, “the fix” also refers to a benchmark exchange rate set at a specific time of day. That benchmark has nothing to do with the messaging protocol.

FAQs

The Bottom Line

FIX matters most to institutions and algorithmic traders who route orders electronically across many counterparties, including forex traders using a broker's FIX API for low-latency access. It removes manual phone steps and leaves a sequenced record of every instruction. Connecting still requires testing each counterparty's rules of engagement and adding security such as TLS or VPNs, and FIX does not guarantee a fill or a price.