ZagTrader

FIX Protocol Message 35=BH: Confirmation Request

Confirmation Request (35=BH) is a FIX application message defined in FIX 4.4 to 5.0 SP2. In the FIX 4.4 definition it has 3 required body fields and 25 optional fields listed below.

MsgType (tag 35)
BH
FIX name
ConfirmationRequest
Category
Application
FIX versions
FIX 4.4 to 5.0 SP2

Confirmation Request in each FIX version

The full field layout as defined in a specific version.

Required fields

Body fields that every Confirmation Request 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
859ConfirmReqIDRequired
773ConfirmTypeRequired
Component OrdAllocGrpOptional
73NoOrders (repeating group)Optional
11ClOrdIDOptional
37OrderIDOptional
198SecondaryOrderIDOptional
526SecondaryClOrdIDOptional
66ListIDOptional
Component NestedParties2Optional
756NoNested2PartyIDs (repeating group)Optional
757Nested2PartyIDOptional
758Nested2PartyIDSourceOptional
759Nested2PartyRoleOptional
Component NstdPtys2SubGrpOptional
806NoNested2PartySubIDs (repeating group)Optional
760Nested2PartySubIDOptional
807Nested2PartySubIDTypeOptional
38OrderQtyOptional
799OrderAvgPxOptional
800OrderBookingQtyOptional
70AllocIDOptional
793SecondaryAllocIDOptional
467IndividualAllocIDOptional
60TransactTimeRequired
79AllocAccountOptional
661AllocAcctIDSourceOptional
798AllocAccountTypeOptional
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 Confirmation Request 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.