Skip to content
FIXtags

COMPONENT · SOURCE ID 1001

StandardHeader

Definition

The standard FIX message header

This is a reusable definition. Requiredness is relative to this structure; its use and conditions in a message remain on that message's page. Version links browse the other dictionary, not an assumed equivalent component.

Direct members

  1. 8 BeginStringfieldRequired here

    FIX.4.2 (Always unencrypted, must be first field in message)

  2. 9 BodyLengthfieldRequired here

    (Always unencrypted, must be second field in message)

  3. 35 MsgTypefieldRequired here

    (Always unencrypted, must be third field in message)

  4. 49 SenderCompIDfieldRequired here

    (Always unencrypted)

  5. 56 TargetCompIDfieldRequired here

    (Always unencrypted)

  6. 115 OnBehalfOfCompIDfield—

    Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)

  7. 128 DeliverToCompIDfield—

    Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)

  8. 90 SecureDataLenfield—

    Required to identify length of encrypted section of message. (Always unencrypted)

  9. 91 SecureDatafield—

    Required when message body is encrypted. Always immediately follows SecureDataLen field.

  10. 34 MsgSeqNumfieldRequired here

    (Can be embedded within encrypted data section.)

  11. 50 SenderSubIDfield—

    (Can be embedded within encrypted data section.)

  12. 142 SenderLocationIDfield—

    Sender's LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)

  13. 57 TargetSubIDfield—

    "ADMIN" reserved for administrative messages not intended for a specific user. (Can be embedded within encrypted data section.)

  14. 143 TargetLocationIDfield—

    Trading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)

  15. 116 OnBehalfOfSubIDfield—

    Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)

  16. 144 OnBehalfOfLocationIDfield—

    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.)

  17. 129 DeliverToSubIDfield—

    Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)

  18. 145 DeliverToLocationIDfield—

    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.)

  19. 43 PossDupFlagfield—

    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.)

  20. 97 PossResendfield—

    Required when message may be duplicate of another message sent under a different sequence number. (Can be embedded within encrypted data section.)

  21. 52 SendingTimefieldRequired here

    (Can be embedded within encrypted data section.)

  22. 122 OrigSendingTimefield—

    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.)

  23. 212 XmlDataLenfield—

    Required when specifying XmlData to identify the length of a XmlData message block. (Can be embedded within encrypted data section.)

  24. 213 XmlDatafield—

    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

  25. 347 MessageEncodingfield—

    Type of message encoding (non-ASCII characters) used in a message’s "Encoded" fields. Required if any "Encoding" fields are used.

  26. 369 LastMsgSeqNumProcessedfield—

    The last MsgSeqNum value received and processed. Can be specified on every message sent. Useful for detecting a backlog with a counterparty.

  27. 370 OnBehalfOfSendingTimefield—

    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")

Used in messages

Direct parent structures

No parent component or group in this snapshot.