TradeCaptureReportRequest (MsgType AD)
TradeCaptureReportRequest is the FIX message with MsgType AD, defined in FIX 4.4. It is an application-level message: it carries a business event rather than managing the session. Its body has 38 top-level members once the standard header and trailer are counted.
A real TradeCaptureReportRequest
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 82 | |
| 35 | MsgType | AD | Trade Capture Report Request |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 568 | TradeRequestID | EXAMPLE | |
| 569 | TradeRequestType | 0 | All trades |
| 10 | CheckSum | 003 |
Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.
Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.
Message body
Components are listed by name and link to their own page rather than being expanded inline; repeating groups are expanded, including where they nest.
- —Standard Message HeadercomponentRequired
- 568TradeRequestIDRequired
- 569TradeRequestTypeRequired
- 263SubscriptionRequestTypeOptional
- 571TradeReportIDOptional
- 818SecondaryTradeReportIDOptional
- 17ExecIDOptional
- 150ExecTypeOptional
- 37OrderIDOptional
- 11ClOrdIDOptional
- 573MatchStatusOptional
- 828TrdTypeOptional
- 829TrdSubTypeOptional
- 830TransferReasonOptional
- 855SecondaryTrdTypeOptional
- 820TradeLinkIDOptional
- 880TrdMatchIDOptional
- —PartiescomponentOptional
- —InstrumentcomponentOptional
- —InstrumentExtensioncomponentOptional
- —FinancingDetailscomponentOptional
- —UndInstrmtGrpcomponentOptional
- —InstrmtLegGrpcomponentOptional
- —TrdCapDtGrpcomponentOptional
- 715ClearingBusinessDateOptional
- 336TradingSessionIDOptional
- 625TradingSessionSubIDOptional
- 943TimeBracketOptional
- 54SideOptional
- 442MultiLegReportingTypeOptional
- 578TradeInputSourceOptional
- 579TradeInputDeviceOptional
- 725ResponseTransportTypeOptional
- 726ResponseDestinationOptional
- 58TextOptional
- 354EncodedTextLenConditional
- 355EncodedTextConditional
- —Standard Message TrailercomponentRequired
Handle TradeCaptureReportRequest in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);if (message.msgType === "AD") { message.name; // "TradeCaptureReportRequest" // fields are keyed by tag; repeating groups live on message.groups}// Problems come back as data, never as exceptions:issues; // FixIssue[]fix.validate(message); // dictionary-level problemsDecode this in your own code
The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.
npm i @boarteam/fix @boarteam/fix-dict-fix44