Indexes

Message Layouts
Session
PreTrade
Trade
PostTrade
Infrastructure

Component

StandardHeader

ID1024
PedigreeAdded FIX.4.0, Updated EP271
The standard FIX message header
Field
Name
Type
Req'd
Comments
Pedigree
8
Y
FIXT.1.1 (Always unencrypted, must be first field in message)
Added FIX.4.0
9
Y
(Always unencrypted, must be second field in message)
Added FIX.4.0
35
Y
(Always unencrypted, must be third field in message)
Added FIX.4.0
1128
Indicates application version using a service pack identifier. The ApplVerID applies to a specific message occurrence.
Added EP-1
1156
Added EP-1
1129
Used to support bilaterally agreed custom functionality
Added EP-1
49
Y
(Always unencrypted)
Added FIX.4.0
56
Y
(Always unencrypted)
Added FIX.4.0
115
Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)
Added FIX.4.0
128
Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)
Added FIX.4.0
90
Required to identify length of encrypted section of message. (Always unencrypted)
Added FIX.4.0
Updated EP195
Deprecated EP195
91
Required when message body is encrypted. Always immediately follows SecureDataLen field.
Added FIX.4.0
Updated EP195
Deprecated EP195
34
Y
(Can be embedded within encrypted data section.)
Added FIX.4.0
50
(Can be embedded within encrypted data section.)
Added FIX.4.0
142
Sender's LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)
Added FIX.4.1
57
"ADMIN" reserved for administrative messages not intended for a specific user. (Can be embedded within encrypted data section.)
Added FIX.4.0
143
Trading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)
Added FIX.4.1
116
Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)
Added FIX.4.0
144
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.)
Added FIX.4.1
129
Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)
Added FIX.4.0
145
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.)
Added FIX.4.1
43
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.)
Added FIX.4.0
97
Required when message may be duplicate of another message sent under a different sequence number. (Can be embedded within encrypted data section.)
Added FIX.4.0
52
Y
(Can be embedded within encrypted data section.)
Added FIX.4.0
122
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.)
Added FIX.4.0
212
Required when specifying XmlData to identify the length of a XmlData message block. (Can be embedded within encrypted data section.)
Added FIX.4.2
213
Can contain a XML formatted message block (e.g. FIXML). Always immediately follows XmlDataLen field. (Can be embedded within encrypted data section.)
See Volume 1: FIXML Support
Added FIX.4.2
347
Type of message encoding (non-ASCII characters) used in a message's "Encoded" fields. Required if any "Encoding" fields are used.
Added FIX.4.2
369
The last MsgSeqNum value received by the FIX engine and processed by downstream application, such as trading system or order routing system. Can be specified on every message sent. Useful for detecting a backlog with a counterparty.
Added FIX.4.2
Number of repeating groups of historical "hop" information. Only applicable if OnBehalfOfCompID is used, however, its use is optional. Note that some market regulations or counterparties may require tracking of message hops.
Added EP-1
Used in messages:

Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy