The standard FIX message header
Added in protocol FIX.4.0
See in: FIX.4.0, FIX.4.1, FIX.4.3, FIX.4.4, FIX.5.0, FIX.5.0SP1, FIX.5.0SP2, FIX.5.0SP2 EP240, FIXT.1.1.
Field or Component | Name | Description | Is Required | Added | Is Deprecated |
---|---|---|---|---|---|
8 | BeginString | FIX.4.2 (Always unencrypted, must be first field in message) | Y | FIX.4.0 | |
9 | BodyLength | (Always unencrypted, must be second field in message) | Y | FIX.4.0 | |
35 | MsgType | (Always unencrypted, must be third field in message) | Y | FIX.4.0 | |
49 | SenderCompID | (Always unencrypted) | Y | FIX.4.0 | |
56 | TargetCompID | (Always unencrypted) | Y | FIX.4.0 | |
115 | OnBehalfOfCompID | Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.) | FIX.4.0 | ||
128 | DeliverToCompID | Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.) | FIX.4.0 | ||
90 | SecureDataLen | Required to identify length of encrypted section of message. (Always unencrypted) | FIX.4.0 | ||
91 | SecureData | Required when message body is encrypted. Always immediately follows SecureDataLen (90) field. | FIX.4.0 | ||
34 | MsgSeqNum | (Can be embedded within encrypted data section.) | Y | FIX.4.0 | |
50 | SenderSubID | (Can be embedded within encrypted data section.) | FIX.4.0 | ||
142 | SenderLocationID | Sender’s LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.) | FIX.4.1 | ||
57 | TargetSubID | “ADMIN” reserved for administrative messages not intended for a specific user. (Can be embedded within encrypted data section.) | FIX.4.0 | ||
143 | TargetLocationID | Trading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.) | FIX.4.1 | ||
116 | OnBehalfOfSubID | Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.) | FIX.4.0 | ||
144 | OnBehalfOfLocationID | Trading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.) | FIX.4.1 | ||
129 | DeliverToSubID | Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.) | FIX.4.0 | ||
145 | DeliverToLocationID | Trading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.) | FIX.4.1 | ||
43 | PossDupFlag | Always required for retransmitted messages, whether prompted by the sending system or as the result of a resend request. (Can be embedded within encrypted data section.) | FIX.4.0 | ||
97 | PossResend | Required when message may be duplicate of another message sent under a different sequence number. (Can be embedded within encrypted data section.) | FIX.4.0 | ||
52 | SendingTime | (Can be embedded within encrypted data section.) | Y | FIX.4.0 | |
122 | OrigSendingTime | Required for message resent as a result of a ResendRequest. If data is not available set to same value as SendingTime (Can be embedded within encrypted data section.) | FIX.4.0 | ||
212 | XmlDataLen | Required when specifying XmlData to identify the length of a XmlData message block. (Can be embedded within encrypted data section.) | FIX.4.2 | ||
213 | XmlData | Can contain a XML formatted message block (e.g. FIXML). Always immediately follows XmlDataLen (212) field. (Can be embedded within encrypted data section.) See Appendix M – FIXML Support |
FIX.4.2 | ||
347 | MessageEncoding | Type of message encoding (non-ASCII characters) used in a message’s “Encoded” fields. Required if any “Encoding” fields are used. | FIX.4.2 | ||
369 | LastMsgSeqNumProcessed | The last MsgSeqNum value received and processed. Can be specified on every message sent. Useful for detecting a backlog with a counterparty. | FIX.4.2 | ||
370 | OnBehalfOfSendingTime | Used when a message is sent via a “hub” or “service bureau”. If A sends to Q (the hub) who then sends to B via a separate FIX session, then when Q sends to B the value of this field should represent the SendingTime on the message A sent to Q. (always expressed in UTC (Universal Time Coordinated, also known as “GMT”) | FIX.4.2 |
Used in messages
- Advertisement (7)
- Allocation (J)
- AllocationInstructionAck (P)
- BidRequest (k)
- BidResponse (l)
- BusinessMessageReject (j)
- DontKnowTrade (Q)
- Email (C)
- ExecutionReport (8)
- Heartbeat (0)
- IOI (6)
- ListCancelRequest (K)
- ListExecute (L)
- ListStatus (N)
- ListStatusRequest (M)
- ListStrikePrice (m)
- Logon (A)
- Logout (5)
- MarketDataIncrementalRefresh (X)
- MarketDataRequest (V)
- MarketDataRequestReject (Y)
- MarketDataSnapshotFullRefresh (W)
- MassQuote (i)
- News (B)
- OrderCancelReject (9)
- OrderCancelReplaceRequest (G)
- OrderCancelRequest (F)
- OrderList (E)
- OrderSingle (D)
- OrderStatusRequest (H)
- Quote (S)
- QuoteAcknowledgement (b)
- QuoteCancel (Z)
- QuoteRequest (R)
- QuoteStatusRequest (a)
- Reject (3)
- ResendRequest (2)
- SecurityDefinition (d)
- SecurityDefinitionRequest (c)
- SecurityStatus (f)
- SecurityStatusRequest (e)
- SequenceReset (4)
- SettlementInstructions (T)
- TestRequest (1)
- TradingSessionStatus (h)
- TradingSessionStatusRequest (g)