Indexes

Message Layouts
Session
PreTrade
Trade
PostTrade

  • Documentation

  • Component

    StandardHeader

    ID1024
    PedigreeAdded FIX.2.7, Updated FIX.4.1

    Each administrative or application message, is preceded by a standard header. The header identifies the message type, length, destination, sequence number, origination point and time.

    Two fields helps with resending messages. The PossDupFlag is set to Y when resending a message as the result of a session level event (i.e. the retransmission of a message reusing a sequence number). The PossResend is set to Y when reissuing a message with a new sequence number (e.g. resending an order). The receiving application should process these messages as follows:

    • PossDupFlag—if a message with this sequence number has been previously received, ignore message, if not, process normally.
    • PossResend—forward message to application and determine if previously received (i.e. verify order id and parameters).
    Field
    Name
    Type
    Req'd
    Comments
    Pedigree
    8
    Y
    FIX.4.1 (Always unencrypted, must be first field in message)
    Added FIX.2.7
    Updated FIX.4.1
    9
    Y
    (Always unencrypted, must be second field in message)
    Added FIX.2.7
    Updated FIX.4.0
    35
    Y
    (Always unencrypted, must be third field in message)
    Added FIX.2.7
    Updated FIX.4.0
    49
    Y
    (Always unencrypted)
    Added FIX.2.7
    56
    Y
    (Always unencrypted)
    Added FIX.2.7
    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.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
    50
    (Can be embedded within encrypted data section.)
    Added FIX.2.7
    Updated FIX.3.0
    142
    Trading partner 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.2.7
    Updated FIX.3.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.2.7
    Updated FIX.4.1
    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
    Deprecated FIX.4.0
    122
    Required for message resends. If data is not available set to same value as SendingTime (Can be embedded within encrypted data section.)
    Added FIX.4.0

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