ZagTrader

FIX Protocol Message 35=l: Bid Response

Bid Response (35=l) is a FIX application message defined in FIX 4.2 to 5.0 SP2. In the FIX 4.4 definition it has 1 required body field and 20 optional fields listed below.

MsgType (tag 35)
l
FIX name
BidResponse
Category
Application
FIX versions
FIX 4.2 to 5.0 SP2

Bid Response in each FIX version

The full field layout as defined in a specific version.

Required fields

Body fields that every Bid Response message must carry in FIX 4.4, in addition to the standard header and trailer.

Field layout

All body fields in the order of the FIX 4.4 definition, with components and repeating groups indented. A field inside an optional component or group is required only when that component or group is present. Later FIX 5.0 service packs add more fields to this message.

TagFieldRequired
390BidIDOptional
391ClientBidIDOptional
Component BidCompRspGrpRequired
420NoBidComponents (repeating group)Required
Component CommissionDataRequired in each entry
12CommissionOptional
13CommTypeOptional
479CommCurrencyOptional
497FundRenewWaivOptional
66ListIDOptional
421CountryOptional
54SideOptional
44PriceOptional
423PriceTypeOptional
406FairValueOptional
430NetGrossIndOptional
63SettlTypeOptional
64SettlDateOptional
336TradingSessionIDOptional
625TradingSessionSubIDOptional
58TextOptional
354EncodedTextLenOptional
355EncodedTextOptional

Standard header and trailer

Every FIX message starts with the standard header, whose required fields are BeginString (8), BodyLength (9), MsgType (35), SenderCompID (49), TargetCompID (56), MsgSeqNum (34) and SendingTime (52), and ends with the trailer field CheckSum (10).

Decode a Bid Response message

All FIX message types · All FIX tags

Field and message data comes from the QuickFIX data dictionaries for FIX 4.0 to 5.0 SP2 and FIXT 1.1, used under the QuickFIX Software License. This product includes software developed by quickfixengine.org (http://www.quickfixengine.org/). Enumerated value names are converted to plain text for reading.