Component
StandardHeader
| ID | 1001 |
| Pedigree | Added FIX.4.0 |
The standard FIX message header
Field | Name | Type | Req'd | Comments | Pedigree |
|---|---|---|---|---|---|
8 | Y | FIX.4.2 (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 | ||
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 | |||
91 | Required when message body is encrypted. Always immediately follows SecureDataLen field. | Added FIX.4.0 | |||
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 an XML-formatted message block (e.g. FIXML). Always immediately follows XmlDataLen field. (Can be embedded within encrypted data section.) See Appendix M – 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 and processed. Can be specified on every message sent. Useful for detecting a backlog with a counterparty. | Added FIX.4.2 | |||
370 | 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") | Added FIX.4.2 |
Used in messages:
- Advertisement
- Allocation
- AllocationAck
- BidRequest
- BidResponse
- BusinessMessageReject
- DontKnowTrade
- ExecutionReport
- Heartbeat
- IOI
- ListCancelRequest
- ListExecute
- ListStatus
- ListStatusRequest
- ListStrikePrice
- Logon
- Logout
- MarketDataIncrementalRefresh
- MarketDataRequest
- MarketDataRequestReject
- MarketDataSnapshotFullRefresh
- MassQuote
- News
- OrderCancelReject
- OrderCancelReplaceRequest
- OrderCancelRequest
- OrderList
- OrderSingle
- OrderStatusRequest
- Quote
- QuoteAcknowledgement
- QuoteCancel
- QuoteRequest
- QuoteStatusRequest
- Reject
- ResendRequest
- SecurityDefinition
- SecurityDefinitionRequest
- SecurityStatus
- SecurityStatusRequest
- SequenceReset
- SettlementInstructions
- TestRequest
- TradingSessionStatus
- TradingSessionStatusRequest
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy