ZagTrader

FIX Protocol Message 35=BX: Application Message Request Ack

Application Message Request Ack (35=BX) is a FIX application message defined in FIX 5.0 SP1 to 5.0 SP2. In the FIX 5.0 SP1 definition it has 1 required body field and 13 optional fields listed below.

MsgType (tag 35)
BX
FIX name
ApplicationMessageRequestAck
Category
Application
FIX versions
FIX 5.0 SP1 to 5.0 SP2

Application Message Request Ack in each FIX version

The full field layout as defined in a specific version.

Required fields

Body fields that every Application Message Request Ack message must carry in FIX 5.0 SP1, in addition to the standard header and trailer.

Field layout

All body fields in the order of the FIX 5.0 SP1 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
1353ApplResponseIDRequired
1346ApplReqIDOptional
1347ApplReqTypeOptional
1348ApplResponseTypeOptional
1349ApplTotalMessageCountOptional
Component ApplIDRequestAckGrpOptional
1351NoApplIDs (repeating group)Optional
1355RefApplIDOptional
1182ApplBegSeqNumOptional
1183ApplEndSeqNumOptional
1357RefApplLastSeqNumOptional
1354ApplResponseErrorOptional
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 Application Message Request Ack 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.