SecurityTypeRequest

StandardHeader definition & usage →

1. 8 BeginStringStringRequired here

   FIX session profile (Always unencrypted, must be first field in message)

2. 9 BodyLengthLengthRequired here

   (Always unencrypted, must be second field in message)

3. 35 MsgTypeStringRequired here

   (Always unencrypted, must be third field in message)

4. 1128 ApplVerIDString—

   Indicates application version using a service pack identifier. The ApplVerID applies to a specific message occurrence.

5. 1156 ApplExtIDint—
6. 1129 CstmApplVerIDString—

   Used to support bilaterally agreed custom functionality

7. 49 SenderCompIDStringRequired here

   (Always unencrypted)

8. 56 TargetCompIDStringRequired here

   (Always unencrypted)

9. 115 OnBehalfOfCompIDString—

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

10. 128 DeliverToCompIDString—

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

11. 90 SecureDataLenDeprecated FIX.5.0SP2Length—

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

12. 91 SecureDataDeprecated FIX.5.0SP2data—

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

13. 34 MsgSeqNumSeqNumRequired here

    (Can be embedded within encrypted data section.)

14. 50 SenderSubIDString—

    (Can be embedded within encrypted data section.)

15. 142 SenderLocationIDString—

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

16. 57 TargetSubIDString—

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

17. 143 TargetLocationIDString—

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

18. 116 OnBehalfOfSubIDString—

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

19. 144 OnBehalfOfLocationIDString—

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

20. 129 DeliverToSubIDString—

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

21. 145 DeliverToLocationIDString—

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

22. 43 PossDupFlagBoolean—

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

23. 97 PossResendBoolean—

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

24. 52 SendingTimeUTCTimestampRequired here

    (Can be embedded within encrypted data section.)

25. 122 OrigSendingTimeUTCTimestamp—

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

26. 212 XmlDataLenLength—

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

27. 213 XmlDataXMLData—

    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

28. 347 MessageEncodingString—

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

29. 369 LastMsgSeqNumProcessedSeqNum—

    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.

30. HopGrpRepeating groupCount tag 627—

    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.

    HopGrp definition & usage →

    1. 627 NoHopsGroup count—
    2. 628 HopCompIDString—
    3. 629 HopSendingTimeUTCTimestamp—
    4. 630 HopRefIDSeqNum—

StandardTrailer definition & usage →

1. 93 SignatureLengthDeprecated FIX.5.0SP2Length—

   Required when trailer contains signature. Note: Not to be included within SecureData field

2. 89 SignatureDeprecated FIX.5.0SP2data—

   Note: Not to be included within SecureData field

3. 10 CheckSumStringRequired here

   (Always unencrypted, always last field in message)