Component
| ID | 1024 |
| Pedigree | Added FIX.2.7 |
Each message, administrative or application, is preceded by a standard header. The header is used to identify the message type, length, destination, sequence number, origination point and time.
Field | Name | Type | Req'd | Comments | Pedigree |
|---|---|---|---|---|---|
8 | Y | FIX.2.7 (Always unencrypted) | Added FIX.2.7 | ||
9 | Y | (Always unencrypted) | Added FIX.2.7 | ||
35 | Y | (Always unencrypted) | Added FIX.2.7 | ||
49 | Y | (Always unencrypted) | Added FIX.2.7 | ||
50 | (Always unencrypted) | Added FIX.2.7 | |||
56 | Y | (Always unencrypted) | Added FIX.2.7 | ||
57 | “ADMIN” reserved for administrative messages not intended for a specific user. (Always unencrypted) | Added FIX.2.7 | |||
90 | Required to identify length of encrypted section of message. (Always unencrypted) | Added FIX.2.7 | |||
91 | Required when message body is encrypted. Always immediately follows SecureDataLen field. | Added FIX.2.7 | |||
34 | Y | (Can be embedded within encrypted data section.) | Added FIX.2.7 | ||
43 | Always required for retransmissions, whether prompted by the sending system or as the result of a resend request. (Can be embedded within encrypted data section.) | Added FIX.2.7 | |||
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.2.7 | |||
52 | Y | (Can be embedded within encrypted data section.) | Added FIX.2.7 | ||
51 | Y | (Can be embedded within encrypted data section.) | Added FIX.2.7 |
Used in messages:
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Service|Privacy Policy