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 Latest · EP313Field

TradSesReqID <335>

Tag
335
Type
String
FIXML name
ReqID
Pedigree
Added FIX 4.2
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

TradSesReqID <335> in plain English

Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).

TradSesReqID is described in the Orchestra file as the unique ID of a Trading Session Status message. It appears on TradingSessionStatusRequest, TradingSessionStatus and the trading session list messages.

Where it is used

TradingSessionStatusRequest (35=g), TradingSessionStatus (35=h), TradingSessionList (35=BJ), TradingSessionListRequest (35=BI), TradingSessionListUpdateReport (35=BS) . In all, 5 messages in FIX Latest can carry it. Full list.

Example message

8=FIXT.1.1|9=76|35=g|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|335=TSR-1|263=0|10=086

Illustrative example, not real orders or market data. A TradingSessionStatusRequest (35=g) in FIX Latest, shown with BeginString FIXT.1.1. 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 Latest dictionary, but it is not a complete specification of the message.

Description (from the Orchestra file)

Unique ID of a Trading Session Status message.

Used in

Messages (5)