Message
TradeCaptureReportRequestAck (AQ)
| ID | 76 |
| Abbr Name | TrdCaptRptReqAck |
| Pedigree | Added FIX.4.4, Updated EP192 |
The Trade Capture Request Ack message is used to:
- Provide an acknowledgement to a Trade Capture Report Request in the case where the Trade Capture Report Request is used to specify a subscription or delivery of reports via an out-of-band ResponseTransmissionMethod.
- Provide an acknowledgement to a Trade Capture Report Request in the case when the return of the Trade Capture Reports matching that request will be delayed or delivered asynchronously. This is useful in distributed trading system environments.
- Indicate that no trades were found that matched the selection criteria specified on the Trade Capture Report Request or the Trade Capture Request was invalid for some business reason, such as request is not authorized, invalid or unknown instrument, party, trading session, etc.
- Provide an acknowledgement to a Trade Capture Report Request in the case where the Trade Capture Report Request is used to specify a subscription or delivery of reports via an out-of-band ResponseTransmissionMethod.
- Provide an acknowledgement to a Trade Capture Report Request in the case when the return of the Trade Capture Reports matching that request will be delayed or delivered asynchronously. This is useful in distributed trading system environments.
- Indicate that no trades were found that matched the selection criteria specified on the Trade Capture Report Request or the Trade Capture Request was invalid for some business reason, such as request is not authorized, invalid or unknown instrument, party, trading session, etc.
Field | Name | Type | Req'd | Comments | Pedigree |
|---|---|---|---|---|---|
StandardHeader | Y | MsgType = AQ | Added FIX.4.4 | ||
568 | Y | Identifier for the trade request | Added FIX.4.4 | ||
1003 | Added EP-1 | ||||
1040 | Added EP-1 | ||||
1041 | Added EP-1 | ||||
1042 | Added EP-1 | ||||
569 | Y | Added FIX.4.4 | |||
263 | Used to subscribe / unsubscribe for trade capture reports If the field is absent, the value 0 will be the default | Added FIX.4.4 | |||
748 | Number of trade reports returned | Added FIX.4.4 | |||
749 | Y | Result of Trade Request | Added FIX.4.4 | ||
750 | Y | Status of Trade Request | Added FIX.4.4 | ||
Instrument | Insert here the set of "Instrument" (symbology) fields defined in "Common Components of Application Messages" | Added FIX.4.4 Updated EP95 | |||
InstrumentExtension | Added EP192 | ||||
UndInstrmtGrp | Added FIX.4.4 | ||||
InstrmtLegGrp | Number of legs NoLegs > 0 identifies a Multi-leg Execution | Added FIX.4.4 | |||
442 | Specify type of multileg reporting to be returned. | Added FIX.4.4 | |||
725 | Ability to specify whether the response to the request should be delivered inband or via pre-arranged out-of-band transport. | Added FIX.4.4 | |||
726 | URI destination name. Used if ResponseTransportType is out-of-band. | Added FIX.4.4 | |||
58 | May be used by the executing market to record any execution Details that are particular to that market | Added FIX.4.4 | |||
354 | Must be set if EncodedText field is specified and must immediately precede it. | Added FIX.4.4 | |||
355 | Encoded (non-ASCII characters) representation of the Text field in the encoded format specified via the MessageEncoding field. | Added FIX.4.4 | |||
1011 | Used to identify the event or source which gave rise to a message | Added EP-1 | |||
StandardTrailer | Y | Added FIX.4.4 |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy