To get the full experience of our online specs, you really need to use something a little bigger. Do you mind firing up your tablet or computer please?
|320 - SecurityReqID ● #||Required String|
Unique ID of a Security Definition Request.
|322 - SecurityResponseID ● #||Required String|
Identifier for the security response message Unique ID of a Security Definition message.
|323 - SecurityResponseType ● #||Required int|
The result of the security request identified by SecurityReqID Type of Security Definition message response
|557 - TotNoSecurityTypes ● #||Optional int|
Indicates total number of security types in the event that multiple Security Type messages are used to return results Indicates total number of security types in the event that multiple Security Type messages are used to return results
|893 - LastFragment ● #||Optional Boolean|
Indicates whether this is the last fragment in a sequence of message fragments. Only required where message has been fragmented. Indicates whether this message is the last in a sequence of messages for those messages that support fragmentation, such as Allocation Instruction, Mass Quote, Security List, Derivative Security List
|558 - NoSecurityTypes ● #||Optional NumInGroup|
Number of Security Type repeating group instances.
|167 - SecurityType ● #||Optional String|
Indicates type of security. See also the Product (460) and CFICode (46) fields. It is recommended that CFICode be used instead of SecurityType for non-Fixed Income instruments. NOTE: Additional values may be used by mutual agreement of the counterparties)
|762 - SecuritySubType ● #||Optional String|
Sub-type qualification/identification of the SecurityType for example:
|460 - Product ● #||Optional int|
Indicates the type of product the security is associated with. See also the CFICode (46) and SecurityType (67) fields.
|461 - CFICode ● #||Optional String|
Indicates the type of security using ISO 10962 standard, Classification of Financial Instruments (CFI code) values. ISO 10962 is maintained by ANNA (Association of National Numbering Agencies) acting as Registration Authority. See the Product (460) and SecurityType (167) fields. It is recommended that CFICode be used instead of SecurityType (167) for non-Fixed Income instruments.
|58 - Text ● #||Optional String|
Comment, instructions, or other identifying information. Free format text string. Note: this field does not have a specified maximum length
|354 - EncodedTextLen ● #||Optional Length|
Must be set if EncodedText field is specified and must immediately precede it. Byte length of encoded (non-ASCII characters) EncodedText (355) field.
|355 - EncodedText ● #||Optional data|
Encoded (non-ASCII characters) representation of the Text field in the encoded format specified via the MessageEncoding field. Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text field.
|336 - TradingSessionID ● #||Optional String|
Optional Trading Session Identifier to specify a particular trading session for which you want to obtain a list of securities that are tradeable. 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. Firms may register Trading Session values on the FIX website (presently a document maintained within "ECN and Exchanges" working group section).
|625 - TradingSessionSubID ● #||Optional String|
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.
|263 - SubscriptionRequestType ● #||Optional char|
Subscribe or unsubscribe for security status to security specified in request. Subscription Request Type
Seems this is the only instance of this field in this spec unfortunately.
The field also appears in the following technical messages:
The field also appears in the following functional views:
Want a head start on a new FIX spec using a FIXatdl file?
Import the XML and we'll create a skeleton spec based on the content.
FixSpec.com is FREE website helping the financial services community to connect faster and easier. Registered users get access to an awesome range of developer tools and an ever-expanding specification repository.
Cool! Check your inbox for a password reset link. If you don't receive it, then your email may not be in our records so try registering it instead.
We are so glad you decided to sign up.
We aim to make this website as simple and enjoyable as possible, but if you get stuck at any point or have any suggestions then please get in touch.
Use the "Help" tab on the right, or email us at email@example.com.
To help you find your way around, we've built a short interactive tour of the site.Start the whirlwind tour! (2-3 mins) No thanks, I'll just look around myself.