Friday, 20 November 2026 · Free. No paywall. No subscription.
Search The MidPoint News

Search articles, videos and sections. Press / to open, Esc to close.

FIX 4.2Field

TradingSessionID <336>

Tag
336
Type
String
Pedigree
Added FIX 4.2
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

This page shows TradingSessionID <336> as defined in FIX 4.2. For the current standard, see tag 336 TradingSessionID in FIX Latest.

TradingSessionID <336> in plain English

Summary by The MidPoint News, based on the FIX Latest description in the Orchestra file. The FIX 4.2 description is quoted in full below and may differ.

TradingSessionID identifies a trading session. A session can run for an extended period; use is set by the market or the counterparties.

Where it is used

ExecutionReport (35=8), Quote (35=S), SecurityDefinition (35=d), Advertisement (35=7), Allocation (35=J), SettlementInstructions (35=T), QuoteCancel (35=Z), QuoteStatusRequest (35=a) and 14 more. In all, 24 messages in FIX 4.2 can carry it. Full list.

Example message

8=FIX.4.2|9=165|35=D|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|11=ORD-1001|1=ACCT-01|21=1|55=AAPL|54=1|60=20261116-08:30:00.000|38=1000|40=2|44=190.50|59=0|386=1|336=1|10=158

Illustrative example, not real orders or market data. A NewOrderSingle (35=D) in FIX 4.2, shown with BeginString FIX.4.2. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.2 dictionary, but it is not a complete specification of the message.

Description (from the Orchestra file)

Identifier for Trading Session Can be used to represent a specific market trading session (e.g. "PRE-OPEN", "CROSS_2", "AFTER-HOURS", "TOSTNET1", "TOSTNET2", etc). Values should be bi-laterally agreed to between counterparties.

Used in

Messages (14)

Components and repeating groups (8)

NameKindPresence
BidCompReqGrpRepeating groupOptional
BidCompRspGrpRepeating groupOptional
InstrmtMDReqGrpRepeating groupOptional
MDFullGrpRepeating groupOptional
MDIncGrpRepeating groupOptional
QuotEntryGrpRepeating groupOptional
QuotReqGrpRepeating groupOptional
TrdgSesGrpRepeating groupOptional
All 24 messages that can carry TradingSessionID, including through components and groups