Finance FIX Tech Book

The Financial Information eXchange (FIX) Protocol

It is a series of messaging specifications for the electronic communication of trade-related messages.

Example of FIX message (Tag Value pair)


Fix message divided into 3 main category

  1. Header
    • Fix version
    • sender
    • receiver
    • type of message
  2. Body
    • order type
    • symbol
    • qty
    • price
  3. Footer
    • checksum – used to avoid the transmission error

Let us now understand above example FIX message in detail

(^) caret is a field delimiter

Referring to FIX specification at


Tag Description Valid values
8 Identifies beginning of new message and protocol version. ALWAYS FIRST FIELD IN MESSAGE. (Always unencrypted)


Tag Description Valid values
9 Message length, in bytes, forward to the CheckSum field. ALWAYS SECOND FIELD IN MESSAGE. (Always unencrypted)


Tag Description Valid values
35 Defines message type. ALWAYS THIRD FIELD IN MESSAGE. (Always unencrypted)Note: A “U” as the first character in the MsgType field (i.e. U1, U2, etc) indicates that the message format is privately defined between the sender and receiver.
D = Order – Single [NewOrderSingle]


Tag Description Valid values
34 Integer message sequence number.


Tag Description Valid values
43 Indicates possible retransmission of message with this sequence number
N = Original transmission [OriginalTransmission]


Tag Description Added Depr. Enums from tag Valid values
49 Assigned value used to identify firm sending message. FIX.2.7



Tag Field Name Data Type Union Datatype Description Added Depr. Enums from tag Valid values


Tag Description Valid values
56 Assigned value used to identify receiving firm.


Tag Description Valid values
52 Time of message transmission (always expressed in GMT)


Tag Description Valid values
1 Account mnemonic as agreed between broker and institution.


Tag Description Valid values
11 Unique identifier for Order as assigned by institution. Uniqueness must be guaranteed within a single trading day. Firms which electronically submit multi-day orders should consider embedding a date within the ClOrdID field to assure uniqueness across days.


Tag Description Valid values
21 Instructions for order handling on Broker trading floor
1 = Automated execution order, private, no Broker intervention [AutomatedExecutionNoIntervention]


Tag Description Enums from tag Valid values
55 Ticker symbol


Tag Description Enums from tag Valid values
48 CUSIP or other alternate security identifier


Tag Description Valid values
22 Identifies class of alternative SecurityID


Tag Description Valid values
54 Side of order
1 = Buy [Buy]


Tag Description Added Valid values
38 Number of shares ordered FIX.2.7


Tag Description Valid values
40 Order type.
2 = Limit [Limit]


Tag Description Valid values
44 Price per share


Tag Description Valid values
59 Specifies how long the order remains in effect. Absence of this field is interpreted as DAY.
0 = Day [Day]


Tag Description Valid values
10 Three byte, simple checksum (see Appendix B for description). ALWAYS LAST FIELD IN RECORD; i.e. serves, with the trailing <SOH>, as the end-of-record delimiter. Always defined as three characters. (Always unencrypted)

Different message type

Admin Messages

  • Login
  • Logout
  • Heartbeat

Application Message

  • New order
  • Order cancel
  • Execution
  • All business related messages

Do come back to see more updates on this article.