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

SecurityReqID <320>

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

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

SecurityReqID <320> in plain English

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

SecurityReqID is the unique ID of a Security Definition Request. The same tag appears on related messages such as SecurityDefinition, SecurityListRequest and SecurityList.

Where it is used

SecurityDefinition (35=d), SecurityDefinitionRequest (35=c) . In all, 2 messages in FIX 4.2 can carry it. Full list.

Example message

8=FIX.4.2|9=92|35=c|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|320=SDR-1|321=0|55=ESZ6|167=FUT|10=128

Illustrative example, not real orders or market data. A SecurityDefinitionRequest (35=c) 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)

Unique ID of a Security Definition Request.

Used in

Messages (2)

MessageMsgTypePresence
SecurityDefinitionRequestcRequired
SecurityDefinitiondRequired