EncodedSecurityDesc (FIX tag 351)

dataFIX 4.4FIX 4.2FIX 5.0 SP2

EncodedSecurityDesc (tag 351) is a data field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 59 message types, always optionally. It is length-prefixed — tag 350 carries the byte count, so the value may contain the SOH separator without breaking the message.

At a glance

Tag
351
Name
EncodedSecurityDesc
Datatype
data
Dialects
FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages
59
Length field
tag 350

What the specification says

FIX 4.4

Encoded (non-ASCII characters) representation of the SecurityDesc (07) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the SecurityDesc field.

FIX 4.2

Encoded (non-ASCII characters) representation of the SecurityDesc field in the encoded format specified via the MessageEncoding field. If used, the ASCII (English) representation should also be specified in the SecurityDesc field.

FIX 5.0 SP2

Encoded (non-ASCII characters) representation of the SecurityDesc (107) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the SecurityDesc field.

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

A real message using tag 351

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength129
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
350EncodedSecurityDescLen7
351EncodedSecurityDescEXAMPLE
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum233
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.

Where tag 351 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
AdjustedPositionReportBL——Optionalinside InstrmtGrp › Instrument
Advertisement7ConditionalOptionalOptionalinside the Instrument component
AllocationInstructionJConditionalOptionalOptionalinside the Instrument component
AllocationInstructionAlertBM——Optionalinside the Instrument component
AllocationReportASConditional—Optionalinside the Instrument component
AssignmentReportAWConditional—Optionalinside the Instrument component
CollateralAssignmentAYConditional—Optionalinside the Instrument component
CollateralInquiryBBConditional—Optionalinside the Instrument component
CollateralInquiryAckBGConditional—Optionalinside the Instrument component
CollateralReportBAConditional—Optionalinside the Instrument component
CollateralRequestAXConditional—Optionalinside the Instrument component
CollateralResponseAZConditional—Optionalinside the Instrument component
ConfirmationAKConditional—Optionalinside the Instrument component
ContraryIntentionReportBO——Optionalinside the Instrument component
CrossOrderCancelReplaceRequesttConditional—Optionalinside the Instrument component
CrossOrderCancelRequestuConditional—Optionalinside the Instrument component
DerivativeSecurityListAAConditional—Optionalinside RelSymDerivSecGrp › Instrument
DerivativeSecurityListUpdateReportBR——Optionalinside RelSymDerivSecUpdGrp › Instrument
DontKnowTradeQConditionalOptionalOptionalinside the Instrument component
EmailCConditionalOptionalOptionalinside InstrmtGrp › Instrument
ExecutionAcknowledgementBN——Optionalinside the Instrument component
ExecutionReport8ConditionalOptionalOptionalinside the Instrument component
IOI6ConditionalOptionalOptionalinside the Instrument component
ListStrikePricemConditionalOptionalOptionalinside InstrmtStrkPxGrp › Instrument
MarketDataIncrementalRefreshXConditionalOptionalOptionalinside MDIncGrp › Instrument
MarketDataRequestVConditionalOptionalOptionalinside InstrmtMDReqGrp › Instrument
MarketDataSnapshotFullRefreshWConditionalOptionalOptionalinside the Instrument component
MassQuoteiConditionalOptionalOptionalinside QuotSetGrp › QuotEntryGrp › Instrument
MassQuoteAcknowledgementbConditionalOptionalOptionalinside QuotSetAckGrp › QuotEntryAckGrp › Instrument
MultilegOrderCancelReplaceACConditional—Optionalinside the Instrument component
NewOrderCrosssConditional—Optionalinside the Instrument component
NewOrderListEConditionalOptionalOptionalinside ListOrdGrp › Instrument
NewOrderMultilegABConditional—Optionalinside the Instrument component
NewOrderSingleDConditionalOptionalOptionalinside the Instrument component
NewsBConditionalOptionalOptionalinside InstrmtGrp › Instrument
OrderCancelReplaceRequestGConditionalOptionalOptionalinside the Instrument component
OrderCancelRequestFConditionalOptionalOptionalinside the Instrument component
OrderMassActionReportBZ——Optionalinside the Instrument component
OrderMassActionRequestCA——Optionalinside the Instrument component
OrderMassCancelReportrConditional—Optionalinside the Instrument component
OrderMassCancelRequestqConditional—Optionalinside the Instrument component
OrderMassStatusRequestAFConditional—Optionalinside the Instrument component
OrderStatusRequestHConditionalOptionalOptionalinside the Instrument component
PositionMaintenanceReportAMConditional—Optionalinside the Instrument component
PositionMaintenanceRequestALConditional—Optionalinside the Instrument component
PositionReportAPConditional—Optionalinside the Instrument component
QuoteSConditionalOptionalOptionalinside the Instrument component
QuoteCancelZConditionalOptionalOptionalinside QuotCxlEntriesGrp › Instrument
QuoteRequestRConditionalOptionalOptionalinside QuotReqGrp › Instrument
QuoteRequestRejectAGConditional—Optionalinside QuotReqRjctGrp › Instrument
QuoteResponseAJConditional—Optionalinside the Instrument component
QuoteStatusReportAIConditional—Optionalinside the Instrument component
QuoteStatusRequestaConditionalOptionalOptionalinside the Instrument component
RFQRequestAHConditional—Optionalinside RFQReqGrp › Instrument
RequestForPositionsANConditional—Optionalinside the Instrument component
RequestForPositionsAckAOConditional—Optionalinside the Instrument component
SecurityDefinitiondConditionalOptionalOptionalinside the Instrument component
SecurityDefinitionRequestcConditionalOptionalOptionalinside the Instrument component
SecurityDefinitionUpdateReportBP——Optionalinside the Instrument component
SecurityListyConditional—Optionalinside SecListGrp › Instrument
SecurityListRequestxConditional—Optionalinside the Instrument component
SecurityListUpdateReportBK——Optionalinside SecLstUpdRelSymGrp › Instrument
SecurityStatusfConditionalOptionalOptionalinside the Instrument component
SecurityStatusRequesteConditionalOptionalOptionalinside the Instrument component
SettlementObligationReportBQ——Optionalinside SettlObligationInstructions › Instrument
StreamAssignmentReportCD——Optionalinside StrmAsgnRptGrp › StrmAsgnRptInstrmtGrp › Instrument
StreamAssignmentRequestCC——Optionalinside StrmAsgnReqGrp › StrmAsgnReqInstrmtGrp › Instrument
TradeCaptureReportAEConditional—Optionalinside the Instrument component
TradeCaptureReportAckARConditional—Optionalinside the Instrument component
TradeCaptureReportRequestADConditional—Optionalinside the Instrument component
TradeCaptureReportRequestAckAQConditional—Optionalinside the Instrument component
TradingSessionStatush——Optionalinside the Instrument component

Wire format

Raw bytes, length-prefixed by a partner field. The value may legally contain the SOH separator, which is why the length matters. @boarteam/fix reads the partner length field first and takes exactly that many bytes, so an embedded separator does not truncate the value.

Read tag 351 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);​// Length-prefixed: tag 350 carries the byte count, so the// value may contain the SOH separator without breaking the message.const length = message.fields[350]?.value;const encodedSecurityDesc = message.fields[351]?.raw;

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