UnsolicitedIndicator (FIX tag 325)

BooleanFIX 4.4FIX 4.2FIX 5.0 SP2

UnsolicitedIndicator (tag 325) is a Boolean field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 5 message types, always optionally. It is an enumerated field with 2 defined values.

At a glance

Tag
325
Name
UnsolicitedIndicator
Datatype
Boolean (char)
Dialects
FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages
5
Valid values
2

What the specification says

Indicates whether or not message is being sent as a result of a subscription request or not.

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

A real message using tag 325

TradeCaptureReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength171
35MsgTypeAETrade Capture Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
571TradeReportIDEXAMPLE
325UnsolicitedIndicatorNMessage is being sent as a result of a prior request
570PreviouslyReportedNnot reported to counterparty
32LastQty1000000
31LastPx1.09210
75TradeDate20240101
60TransactTime20240101-12:00:00.000
552NoSides1 entry1repeating group
54Side1Buy
37OrderIDORD-10042
10CheckSum210
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
YMessage is being sent unsolicitedYES / MessageIsBeingSentUnsolicited / MESSAGE_IS_BEING_SENT_UNSOLICITED
NMessage is being sent as a result of a prior requestNO / MessageIsBeingSentAsAResultOfAPriorRequest / MESSAGE_IS_BEING_SENT_AS_A_RESULT_OF_A_PRIOR_REQUEST

Where tag 325 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.2FIX 5.0 SP2Where in the message
PositionReportAPOptionalOptionaldirectly on the message body
RequestForPositionsAckAOOptionalOptionaldirectly on the message body
SecurityStatusfOptionalOptionalOptionaldirectly on the message body
TradeCaptureReportAEOptionalOptionaldirectly on the message body
TradingSessionListBJOptionalinside the TrdSessLstGrp component
TradingSessionListUpdateReportBSOptionalinside the TrdSessLstGrp component
TradingSessionStatushOptionalOptionalOptionaldirectly on the message body

Wire format

Y or N. Not 1/0, and not true/false. @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 325 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 unsolicitedIndicator = message.fields[325]?.raw;// e.g. "Y" — Message is being sent unsolicited// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(325)  ?.enumValues?.find((e) => e.value === unsolicitedIndicator)  ?.description;

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