UnderlyingPx (FIX tag 810)

PriceFIX 4.4

UnderlyingPx (tag 810) is a Price field defined in FIX 4.4. It appears in 59 message types, always optionally.

At a glance

Tag
810
Name
UnderlyingPx
Datatype
Price (float)
Dialects
FIX 4.4
Messages
59

What the specification says

Underlying price associate with a derivative instrument.

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

A real message using tag 810

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength165
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
711NoUnderlyings2 entries2repeating group
311UnderlyingSymbolEXAMPLE
810UnderlyingPx1.09210
311UnderlyingSymbolEXAMPLE
810UnderlyingPx1.09210
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum036
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 810 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.

MessageMsgTypeRequirednessWhere in the message
Advertisement7Optionalinside UndInstrmtGrp › UnderlyingInstrument
AllocationInstructionJOptionalinside UndInstrmtGrp › UnderlyingInstrument
AllocationReportASOptionalinside UndInstrmtGrp › UnderlyingInstrument
AssignmentReportAWOptionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralAssignmentAYOptionalinside UndInstrmtCollGrp › UnderlyingInstrument
CollateralInquiryBBOptionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralInquiryAckBGOptionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralReportBAOptionalinside UndInstrmtGrp › UnderlyingInstrument
CollateralRequestAXOptionalinside UndInstrmtCollGrp › UnderlyingInstrument
CollateralResponseAZOptionalinside UndInstrmtCollGrp › UnderlyingInstrument
ConfirmationAKOptionalinside UndInstrmtGrp › UnderlyingInstrument
CrossOrderCancelReplaceRequesttOptionalinside UndInstrmtGrp › UnderlyingInstrument
CrossOrderCancelRequestuOptionalinside UndInstrmtGrp › UnderlyingInstrument
DerivativeSecurityListAAOptionalinside the UnderlyingInstrument component
DerivativeSecurityListRequestzOptionalinside the UnderlyingInstrument component
DontKnowTradeQOptionalinside UndInstrmtGrp › UnderlyingInstrument
EmailCOptionalinside UndInstrmtGrp › UnderlyingInstrument
ExecutionReport8Optionalinside UndInstrmtGrp › UnderlyingInstrument
IOI6Optionalinside UndInstrmtGrp › UnderlyingInstrument
ListStrikePricemOptionalinside UndInstrmtStrkPxGrp › UnderlyingInstrument
MarketDataIncrementalRefreshXOptionalinside MDIncGrp › UndInstrmtGrp › UnderlyingInstrument
MarketDataRequestVOptionalinside InstrmtMDReqGrp › UndInstrmtGrp › UnderlyingInstrument
MarketDataSnapshotFullRefreshWOptionalinside UndInstrmtGrp › UnderlyingInstrument
MassQuoteiOptionalinside QuotSetGrp › UnderlyingInstrument
MassQuoteAcknowledgementbOptionalinside QuotSetAckGrp › UnderlyingInstrument
MultilegOrderCancelReplaceACOptionalinside UndInstrmtGrp › UnderlyingInstrument
NewOrderCrosssOptionalinside UndInstrmtGrp › UnderlyingInstrument
NewOrderListEOptionalinside ListOrdGrp › UndInstrmtGrp › UnderlyingInstrument
NewOrderMultilegABOptionalinside UndInstrmtGrp › UnderlyingInstrument
NewOrderSingleDOptionalinside UndInstrmtGrp › UnderlyingInstrument
NewsBOptionalinside UndInstrmtGrp › UnderlyingInstrument
OrderCancelReplaceRequestGOptionalinside UndInstrmtGrp › UnderlyingInstrument
OrderCancelRequestFOptionalinside UndInstrmtGrp › UnderlyingInstrument
OrderMassCancelReportrOptionalinside the UnderlyingInstrument component
OrderMassCancelRequestqOptionalinside the UnderlyingInstrument component
OrderMassStatusRequestAFOptionalinside the UnderlyingInstrument component
OrderStatusRequestHOptionalinside UndInstrmtGrp › UnderlyingInstrument
PositionMaintenanceReportAMOptionalinside UndInstrmtGrp › UnderlyingInstrument
PositionMaintenanceRequestALOptionalinside UndInstrmtGrp › UnderlyingInstrument
PositionReportAPOptionalinside PosUndInstrmtGrp › UnderlyingInstrument
QuoteSOptionalinside UndInstrmtGrp › UnderlyingInstrument
QuoteCancelZOptionalinside QuotCxlEntriesGrp › UndInstrmtGrp › UnderlyingInstrument
QuoteRequestROptionalinside QuotReqGrp › UndInstrmtGrp › UnderlyingInstrument
QuoteRequestRejectAGOptionalinside QuotReqRjctGrp › UndInstrmtGrp › UnderlyingInstrument
QuoteResponseAJOptionalinside UndInstrmtGrp › UnderlyingInstrument
QuoteStatusReportAIOptionalinside UndInstrmtGrp › UnderlyingInstrument
QuoteStatusRequestaOptionalinside UndInstrmtGrp › UnderlyingInstrument
RFQRequestAHOptionalinside RFQReqGrp › UndInstrmtGrp › UnderlyingInstrument
RequestForPositionsANOptionalinside UndInstrmtGrp › UnderlyingInstrument
RequestForPositionsAckAOOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityDefinitiondOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityDefinitionRequestcOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityListyOptionalinside SecListGrp › UndInstrmtGrp › UnderlyingInstrument
SecurityListRequestxOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityStatusfOptionalinside UndInstrmtGrp › UnderlyingInstrument
SecurityStatusRequesteOptionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportAEOptionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportRequestADOptionalinside UndInstrmtGrp › UnderlyingInstrument
TradeCaptureReportRequestAckAQOptionalinside UndInstrmtGrp › UnderlyingInstrument

Wire format

A decimal price. Precision is a venue convention, not a protocol rule, so compare the raw string when exactness matters. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.

Read tag 810 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 field = message.fields[810];field?.name;   // "UnderlyingPx"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

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