BidRequest

StandardHeader definition & usage →

1. 8 BeginStringStringRequired here

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

2. 9 BodyLengthintRequired here

   (Always unencrypted, must be second field in message)

3. 35 MsgTypeStringRequired here

   (Always unencrypted, must be third field in message)

4. 49 SenderCompIDStringRequired here

   (Always unencrypted)

5. 56 TargetCompIDStringRequired here

   (Always unencrypted)

6. 115 OnBehalfOfCompIDString—

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

7. 128 DeliverToCompIDString—

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

8. 90 SecureDataLenint—

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

9. 91 SecureDatadata—

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

10. 34 MsgSeqNumintRequired here

    (Can be embedded within encrypted data section.)

11. 50 SenderSubIDString—

    (Can be embedded within encrypted data section.)

12. 142 SenderLocationIDString—

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

13. 57 TargetSubIDString—

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

14. 143 TargetLocationIDString—

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

15. 116 OnBehalfOfSubIDString—

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

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

17. 129 DeliverToSubIDString—

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

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

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

20. 97 PossResendBoolean—

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

21. 52 SendingTimeUTCTimestampRequired here

    (Can be embedded within encrypted data section.)

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

23. 212 XmlDataLenint—

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

24. 213 XmlDatadata—

    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 MessageEncodingString—

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

26. 369 LastMsgSeqNumProcessedint—

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

27. 370 OnBehalfOfSendingTimeUTCTimestamp—

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

BidDescReqGrp definition & usage →

1. 398 NoBidDescriptorsGroup count—
2. 399 BidDescriptorTypeint—

   Required if NoBidDescriptors > 0. Must be first field in repeating group.

3. 400 BidDescriptorString—
4. 401 SideValueIndint—

   Refers to the SideValue1 or SideValue2. These are used as opposed to Buy or Sell so that the basket can be quoted either way as Buy or Sell.

5. 404 LiquidityValueAmt—

   Value between LiquidityPctLow and LiquidityPctHigh in Currency

6. 441 LiquidityNumSecuritiesint—

   Number of Securities between LiquidityPctLow and LiquidityPctHigh in Currency

7. 402 LiquidityPctLowfloat—

   Liquidity indicator or lower limit if LiquidityNumSecurities > 1

8. 403 LiquidityPctHighfloat—

   Upper liquidity indicator if LiquidityNumSecurities > 1

9. 405 EFPTrackingErrorfloat—

   Eg Used in EFP (Exchange For Physical) trades 12%

10. 406 FairValueAmt—

    Used in EFP trades

11. 407 OutsideIndexPctfloat—

    Used in EFP trades

12. 408 ValueOfFuturesAmt—

    Used in EFP trades

BidCompReqGrp definition & usage →

1. 420 NoBidComponentsGroup count—
2. 66 ListIDString—

   Required if NoBidComponents > 0. Must be first field in repeating group.

3. 54 Sidechar—

   When used in request for a "Disclosed" bid indicates that bid is required on assumption that SideValue1 is Buy or Sell. SideValue2 can be derived by inference.

4. 336 TradingSessionIDString—

   Indicates off-exchange type activities for Detail.

5. 430 NetGrossIndint—

   Indicates Net or Gross for selling Detail.

6. 63 SettlmntTypchar—

   Indicates order settlement period for Detail.

7. 64 FutSettDateLocalMktDate—
8. 1 AccountString—

StandardTrailer definition & usage →

1. 93 SignatureLengthint—

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

2. 89 Signaturedata—

   Note: Not to be included within SecureData field

3. 10 CheckSumStringRequired here

   (Always unencrypted, always last field in message)