Skip to content

COMPONENT · SOURCE ID 1024

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

    FIXT.1.1 (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. Indicates application version using a service pack identifier. The ApplVerID applies to a specific message occurrence.

  5. Used to support bilaterally agreed custom functionality

  6. 49 SenderCompIDfieldRequired here

    (Always unencrypted)

  7. 56 TargetCompIDfieldRequired here

    (Always unencrypted)

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

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

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

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

  12. 34 MsgSeqNumfieldRequired here

    (Can be embedded within encrypted data section.)

  13. (Can be embedded within encrypted data section.)

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

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

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

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

  18. 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. Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)

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

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

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

  23. 52 SendingTimefieldRequired here

    (Can be embedded within encrypted data section.)

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

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

  26. 213 XmlDatafield

    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

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

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

  29. HopGrpgroup

    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.

Used in messages

Direct parent structures

No parent component or group in this snapshot.