MDReqRejReason (FIX tag 281)

charFIX 4.4FIX 4.2

MDReqRejReason (tag 281) is a char field defined in FIX 4.4 and FIX 4.2. It appears in 1 message type, always optionally. It is an enumerated field with 13 defined values.

At a glance

Tag: 281
Name: MDReqRejReason
Datatype: char
Dialects: FIX 4.4 and FIX 4.2
Messages: 1
Valid values: 13

What the specification says

FIX 4.4

Reason for the rejection of a Market Data request

FIX 4.2

Reason for the rejection of a Market Data request.

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

A real message using tag 281

MarketDataRequestReject · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	79
35	MsgType	Y	Market Data Request Reject
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
262	MDReqID	REQ-1
281	MDReqRejReason	0	Unknown symbol
10	CheckSum	005

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	Dialects
0	Unknown symbol	UNKNOWN_SYMBOL / UnknownSymbol	FIX 4.4, FIX 4.2
1	Duplicate MDReqID	DUPLICATE_MDREQID / DuplicateMDReqID	FIX 4.4, FIX 4.2
2	Insufficient Bandwidth	INSUFFICIENT_BANDWIDTH / InsufficientBandwidth	FIX 4.4, FIX 4.2
3	Insufficient Permissions	INSUFFICIENT_PERMISSIONS / InsufficientPermissions	FIX 4.4, FIX 4.2
4	Unsupported SubscriptionRequestType	UNSUPPORTED_SUBSCRIPTIONREQUESTTYPE / UnsupportedSubscriptionRequestType	FIX 4.4, FIX 4.2
5	Unsupported MarketDepth	UNSUPPORTED_MARKETDEPTH / UnsupportedMarketDepth	FIX 4.4, FIX 4.2
6	Unsupported MDUpdateType	UNSUPPORTED_MDUPDATETYPE / UnsupportedMDUpdateType	FIX 4.4, FIX 4.2
7	Unsupported AggregatedBook	UNSUPPORTED_AGGREGATEDBOOK / UnsupportedAggregatedBook	FIX 4.4, FIX 4.2
8	Unsupported MDEntryType	UNSUPPORTED_MDENTRYTYPE / UnsupportedMDEntryType	FIX 4.4, FIX 4.2
9	Unsupported TradingSessionID	UNSUPPORTED_TRADINGSESSIONID	FIX 4.4
A	Unsupported Scope	UNSUPPORTED_SCOPE	FIX 4.4
B	Unsupported OpenCloseSettleFlag	UNSUPPORTED_OPENCLOSESETTLEFLAG	FIX 4.4
C	Unsupported MDImplicitDelete	UNSUPPORTED_MDIMPLICITDELETE	FIX 4.4

Where tag 281 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	FIX 4.4	FIX 4.2	Where in the message
MarketDataRequestReject	Y	Optional	Optional	directly on the message body

Wire format

A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 281 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 mDReqRejReason = message.fields[281]?.raw;// e.g. "0" — Unknown symbol// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(281)  ?.enumValues?.find((e) => e.value === mDReqRejReason)  ?.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