QuoteResponseLevel (FIX tag 301)

intFIX 4.4FIX 4.2

QuoteResponseLevel (tag 301) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 4 message types, always optionally. It is an enumerated field with 3 defined values.

At a glance

Tag
301
Name
QuoteResponseLevel
Datatype
int
Dialects
FIX 4.4 and FIX 4.2
Messages
4
Valid values
3

What the specification says

Level of Response requested from receiver of quote messages.

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

A real message using tag 301

Quote · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength81
35MsgTypeSQuote
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
117QuoteIDEXAMPLE
301QuoteResponseLevel0No Acknowledgement (Default)
10CheckSum182
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.

ValueMeaningSymbolic name
0No Acknowledgement (Default)NO_ACKNOWLEDGEMENT / NoAcknowledgement
1Acknowledge only negative or erroneous quotesACKNOWLEDGE_ONLY_NEGATIVE_OR_ERRONEOUS_QUOTES / AcknowledgeOnlyNegativeOrErroneousQuotes
2Acknowledge each quote messagesACKNOWLEDGE_EACH_QUOTE_MESSAGES / AcknowledgeEachQuoteMessage

Where tag 301 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.

MessageMsgTypeFIX 4.4FIX 4.2Where in the message
MassQuoteiOptionalOptionaldirectly on the message body
MassQuoteAcknowledgementbOptionalOptionaldirectly on the message body
QuoteSOptionalOptionaldirectly on the message body
QuoteCancelZOptionalOptionaldirectly 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 301 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 quoteResponseLevel = message.fields[301]?.raw;// e.g. "0" — No Acknowledgement (Default)// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(301)  ?.enumValues?.find((e) => e.value === quoteResponseLevel)  ?.description;

Other int fields

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