TradingSessionSubID (FIX tag 625)

StringFIX 4.4FIX 5.0 SP2

TradingSessionSubID (tag 625) is a String field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 51 message types, always optionally.

At a glance

Tag
625
Name
TradingSessionSubID
Datatype
String
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
51

What the specification says

FIX 4.4

Optional market assigned sub identifier for a trading session. Usage is determined by market or counterparties. Used by US based futures markets to identify exchange specific execution time bracket codes as required by US market regulations.

FIX 5.0 SP2

Optional market assigned sub identifier for a trading phase within a trading session. Usage is determined by market or counterparties. Used by US based futures markets to identify exchange specific execution time bracket codes as required by US market regulations. Bilaterally agreed values of data type "String" that start with a character can be used for backward compatibility

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

A real message using tag 625

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength165
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
386NoTradingSessions2 entries2repeating group
336TradingSessionIDREGULAR
625TradingSessionSubIDEXAMPLE
336TradingSessionIDREGULAR
625TradingSessionSubIDEXAMPLE
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum176
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 625 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 5.0 SP2Where in the message
Advertisement7OptionalOptionaldirectly on the message body
AllocationInstructionJOptionalOptionaldirectly on the message body
AllocationInstructionAlertBMOptionaldirectly on the message body
AllocationReportASOptionalOptionaldirectly on the message body
BidRequestkOptionalOptionalinside the BidCompReqGrp component
BidResponselOptionalOptionalinside the BidCompRspGrp component
CollateralAssignmentAYOptionalOptionaldirectly on the message body
CollateralInquiryBBOptionalOptionaldirectly on the message body
CollateralInquiryAckBGOptionalOptionaldirectly on the message body
CollateralReportBAOptionalOptionaldirectly on the message body
CollateralRequestAXOptionalOptionaldirectly on the message body
CrossOrderCancelReplaceRequesttOptionalOptionalinside the TrdgSesGrp component
DerivativeSecurityListAAOptionalOptionalinside the RelSymDerivSecGrp component
DerivativeSecurityListRequestzOptionalOptionaldirectly on the message body
DerivativeSecurityListUpdateReportBROptionalinside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp
ExecutionReport8OptionalOptionaldirectly on the message body
MarketDataIncrementalRefreshXOptionalOptionalinside the MDIncGrp component
MarketDataRequestVOptionalOptionalinside the TrdgSesGrp component
MarketDataSnapshotFullRefreshWOptionalOptionalinside the MDFullGrp component
MassQuoteiOptionalOptionalinside QuotSetGrp › QuotEntryGrp
MassQuoteAcknowledgementbOptionalOptionalinside QuotSetAckGrp › QuotEntryAckGrp
MultilegOrderCancelReplaceACOptionalOptionalinside the TrdgSesGrp component
NewOrderCrosssOptionalOptionalinside the TrdgSesGrp component
NewOrderListEOptionalOptionalinside ListOrdGrp › TrdgSesGrp
NewOrderMultilegABOptionalOptionalinside the TrdgSesGrp component
NewOrderSingleDOptionalOptionalinside the TrdgSesGrp component
OrderCancelReplaceRequestGOptionalOptionalinside the TrdgSesGrp component
OrderMassActionReportBZOptionaldirectly on the message body
OrderMassActionRequestCAOptionaldirectly on the message body
OrderMassCancelReportrOptionalOptionaldirectly on the message body
OrderMassCancelRequestqOptionalOptionaldirectly on the message body
OrderMassStatusRequestAFOptionalOptionaldirectly on the message body
PositionMaintenanceReportAMOptionalOptionalinside the TrdgSesGrp component
PositionMaintenanceRequestALOptionalOptionalinside the TrdgSesGrp component
QuoteSOptionalOptionaldirectly on the message body
QuoteCancelZOptionalOptionaldirectly on the message body
QuoteRequestROptionalOptionalinside the QuotReqGrp component
QuoteRequestRejectAGOptionalOptionalinside the QuotReqRjctGrp component
QuoteResponseAJOptionalOptionaldirectly on the message body
QuoteStatusReportAIOptionalOptionaldirectly on the message body
QuoteStatusRequestaOptionalOptionaldirectly on the message body
RFQRequestAHOptionalOptionalinside the RFQReqGrp component
RequestForPositionsANOptionalOptionalinside the TrdgSesGrp component
SecurityDefinitiondOptionalOptionaldirectly on the message body
SecurityDefinitionRequestcOptionalOptionaldirectly on the message body
SecurityDefinitionUpdateReportBPOptionalinside MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp
SecurityListyOptionalOptionalinside the SecListGrp component
SecurityListRequestxOptionalOptionaldirectly on the message body
SecurityListUpdateReportBKOptionalinside SecLstUpdRelSymGrp › SecurityTradingRules › TradingSessionRulesGrp
SecurityStatusfOptionalOptionaldirectly on the message body
SecurityStatusRequesteOptionalOptionaldirectly on the message body
SecurityTypeRequestvOptionalOptionaldirectly on the message body
SecurityTypeswOptionalOptionaldirectly on the message body
TradeCaptureReportAEOptionalOptionalinside the TrdCapRptSideGrp component
TradeCaptureReportAckAROptionalinside the TrdCapRptAckSideGrp component
TradeCaptureReportRequestADOptionalOptionaldirectly on the message body
TradingSessionListBJOptionalinside the TrdSessLstGrp component
TradingSessionListRequestBIOptionaldirectly on the message body
TradingSessionListUpdateReportBSOptionalinside the TrdSessLstGrp component
TradingSessionStatushOptionalOptionaldirectly on the message body
TradingSessionStatusRequestgOptionalOptionaldirectly on the message body

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 625 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[625];field?.name;   // "TradingSessionSubID"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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