TradeRequestResult (FIX tag 749)

intFIX 4.4

TradeRequestResult (tag 749) is an int field defined in FIX 4.4. It appears in 1 message type and is required in 1 of them. It is an enumerated field with 9 defined values.

At a glance

Tag: 749
Name: TradeRequestResult
Datatype: int
Dialects: FIX 4.4
Messages: 1
Valid values: 9

What the specification says

Result of Trade Request 4000+ Reserved and available for bi-laterally agreed upon user-defined values

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 749

TradeCaptureReportRequestAck · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	94
35	MsgType	AQ	Trade Capture Report Request Ack
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
568	TradeRequestID	EXAMPLE
569	TradeRequestType	0	All trades
749	TradeRequestResult	0	Successful (Default)
750	TradeRequestStatus	0	Accepted
10	CheckSum	047

Edit and decode it yourself

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.

Open in the full decoder →

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.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

Value	Meaning	Symbolic name
0	Successful (Default)	SUCCESSFUL
1	Invalid or unknown instrument	INVALID_OR_UNKNOWN_INSTRUMENT
2	Invalid type of trade requested	INVALID_TYPE_OF_TRADE_REQUESTED
3	Invalid parties	INVALID_PARTIES
4	Invalid Transport Type requested	INVALID_TRANSPORT_TYPE_REQUESTED
5	Invalid Destination requested	INVALID_DESTINATION_REQUESTED
8	TradeRequestType not supported	TRADEREQUESTTYPE_NOT_SUPPORTED
9	Unauthorized for Trade Capture Report Request	UNAUTHORIZED_FOR_TRADE_CAPTURE_REPORT_REQUEST
99	Other	OTHER

Where tag 749 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

Message	MsgType	Requiredness	Where in the message
TradeCaptureReportRequestAck	AQ	Required	directly on the message body

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 749 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const tradeRequestResult = message.fields[749]?.raw;// e.g. "0" — Successful (Default)// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(749)  ?.enumValues?.find((e) => e.value === tradeRequestResult)  ?.description;

Decode 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

Try the decoder Source on GitHub