QuoteCondition (FIX tag 276)

MultipleValueStringFIX 4.4FIX 4.2

QuoteCondition (tag 276) is a MultipleValueString field defined in FIX 4.4 and FIX 4.2. It appears in 2 message types, always optionally. It is an enumerated field with 9 defined values.

At a glance

Tag
276
Name
QuoteCondition
Datatype
MultipleValueString (String)
Dialects
FIX 4.4 and FIX 4.2
Messages
2
Valid values
9

What the specification says

FIX 4.4

Space-delimited list of conditions describing a quote

FIX 4.2

Space-delimited list of conditions describing a quote.

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

A real message using tag 276

MarketDataSnapshotFullRefresh · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength93
35MsgTypeWMarket Data-Snapshot/Full Refresh
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
268NoMDEntries2 entries2repeating group
269MDEntryType0Bid
276QuoteConditionAOpen / Active
269MDEntryType0Bid
276QuoteConditionAOpen / Active
10CheckSum066
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
AOpen / ActiveOPEN / Open
BClosed / InactiveCLOSED / Closed
CExchange BestEXCHANGE_BEST / ExchangeBest
DConsolidated BestCONSOLIDATED_BEST / ConsolidatedBest
ELockedLOCKED / Locked
FCrossedCROSSED / Crossed
GDepthDEPTH / Depth
HFast TradingFAST_TRADING / FastTrading
INon-FirmNON_FIRM / NonFirm

Where tag 276 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
MarketDataIncrementalRefreshXOptionalOptionalinside the MDIncGrp component
MarketDataSnapshotFullRefreshWOptionalOptionalinside the MDFullGrp component

Wire format

Several values in one field, separated by spaces. Decoders return an array. @boarteam/fix splits the value on its delimiter and returns an array of strings.

Read tag 276 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 quoteCondition = message.fields[276]?.raw;// e.g. "A" — Open / Active// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(276)  ?.enumValues?.find((e) => e.value === quoteCondition)  ?.description;

Other MultipleValueString 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