When sending the instrument component block in a FIX client request, you can specify the instrument in any of the following methods:
By Security ID
By Security Alt ID
By Security name
These methods can be used as follows:
You can use the security ID method for all cases.
You can only use the security Alt ID method for contracts for which the exchange populates Tag 455 (SecurityAltID).
You can use the security name method for all contracts on all exchanges with the following exceptions. Note that you cannot use the security name method for ICE contracts that use daily, weekly, variable, and undefined delivery terms.
Tag |
Field Name |
Req’d |
Type |
Comments |
48 |
SecurityID |
Y |
String |
- ID of the instrument
Note
The combination of this tag and tag 22 (IDSource) must uniquely identify an instrument in the QST platform.
|
22 |
IDSource |
Y |
String |
- Source for the value of tag 48 (SecurityID)
-
|
207 |
SecurityExchange |
C |
Exchange |
- Name of the market where the instrument trades.
- QST FIX uses this value to identify the exchange that offers the security. Possible values include:
-
Condition: Required when Tag 100 (ExtDestination) is absent and when tag 22 (IDSource) is 8 (Exchange symbol), 97 (Alias) or 9 (Name).
|
100 |
ExDestination |
C |
Exchange |
- Market Identifier Code (MIC) of the sub-market where the instrument trades.
Execution destination for the order as defined by the institution
Some traders use this tag in place of Tag 207 (SecurityExchange) to identify the exchange.
ISO 10383 defines a comprehensive list of MIC codes.
Condition: Required when Tag 207 (SecurityExchange) is absent and when tag 22 (IDSource) is 8 (Exchange symbol), 97 (Alias) or 9 (Name).
|
55 |
Symbol |
Y |
String |
Exchange-provided product symbol for the tradable product. |
Note
For those exchanges that support alternate security ID (sometimes called aliases), client applications can use Tag 455 (SecurityAltID)
to specify its alternate security ID. As instruments on different exchanges can share the same value for SecurityAltID, including SecurityExchange creates a unique identifier for each instrument.
Tag |
Field Name |
Req’d |
Type |
Comments |
207 |
SecurityExchange |
C |
Exchange |
- Name of the market where the instrument trades.
QST FIX uses this value to identify the exchange that offers the security.
Possible values include:
Condition: Required when Tag 100 (ExtDestination) is absent and when tag 22 (IDSource) is 8 (Exchange symbol), 97 (Alias) or 9 (Name).
|
100 |
ExDestination |
C |
Exchange |
- Market Identifier Code (MIC) of the sub-market where the instrument trades.
Execution destination for the order as defined by the institution
Some traders use this tag in place of Tag 207 (SecurityExchange) to identify the exchange.
ISO 10383 defines a comprehensive list of MIC codes.
Condition: Required when Tag 207 (SecurityExchange) is absent and when tag 22 (IDSource) is 8 (Exchange symbol), 97 (Alias) or 9 (Name).
|
454 |
NoSecurityAltID |
Y |
NumInGroup |
Number of alternate security IDs in this repeating group |
455 |
SecurityAltID |
Y |
String |
Alternate ID for an instrument or security, typically for display purposes. |
456 |
SecurityAltIDSource |
Y |
String |
- Alternate ID for an instrument or security
Possible values include:
8: Exchange security ID
97: Alias
98: Name
99: Other
Note
99 (Other) is the QST internal symbol representation of the instrument.
|
55 |
Symbol |
Y |
String |
Exchange-provided product symbol for the tradable product. |
167 |
SecurityType |
Y |
String |
- Asset class of the instrument.
Possible values include:
FUT: future
MLEG: multi-leg
OPT: option
|
Note
You can also identify instruments by specifying its name and characteristics. You might use this method if your application or business practices do not use security IDs.
Tag |
Field Name |
Req’d |
Type |
Comments |
207 |
SecurityExchange |
C |
Exchange |
- Name of the market where the instrument trades.
QST FIX uses this value to identify the exchange that offers the security.
Possible values include:
Condition: Required when Tag 100 (ExtDestination) is absent and when tag 22 (IDSource) is 8 (Exchange symbol), 97 (Alias) or 9 (Name).
|
100 |
ExDestination |
C |
Exchange |
- Market Identifier Code (MIC) of the sub-market where the instrument trades.
Execution destination for the order as defined by the institution
Some traders use this tag in place of Tag 207 (SecurityExchange) to identify the exchange.
ISO 10383 defines a comprehensive list of MIC codes.
Condition: Required when Tag 207 (SecurityExchange) is absent and when tag 22 (IDSource) is 8 (Exchange symbol), 97 (Alias) or 9 (Name).
|
55 |
Symbol |
Y |
String |
- Exchange-provided product symbol for the tradable product.
Condition: Not used when Tag 167 (SecurityType)=MLEG.
|
167 |
SecurityType |
Y |
String |
- Asset class of the instrument.
Possible values include:
FUT: future
MLEG: multi-leg
OPT: option
|
200 |
MaturityMonthYear |
C |
MonthYear |
- Month and year the instrument reaches maturity in the format YYYYMM.
Condition: Required when Tag 167 (SecurityType) is not MLEG
Note
If included, tag 541 (MaturityDate) will override this tag.
|
541 |
MaturityDate |
C |
LocalMktDate |
- Maturity date in format YYYYMMDD.
Required when Tag 167 (SecurityType) is not MLEG
.. note::
This tag value overrides tag 200 (MaturityMonthYear) and tag 205 (MaturityDay), if they are also specified.
|
205 |
MaturityDay |
C |
DayOfMonth |
- Day of expiration for the instrument.
QST FIX uses this value and Tag 200 (MaturityMonthYear) to specify the maturity date when Tag 167 (SecurityType) is not MLEG.
Required when multiple contracts exist for the same month
Note
If included, tag 541 (MaturityDate) will override this tag.
|
201 |
PutOrCall |
C |
int |
- Whether this is a put or call option
Required when Tag 167 (SecurityType) is OPT
Possible values include:
|
202 |
StrikePrice |
C |
Price |
- Strike price for an option
Required when Tag 167 (SecurityType) is OPT
|