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?
|390 - BidID ● #||Optional String|
Unique identifier for Bid Response as assigned by sell-side (broker, exchange, ECN). Uniqueness must be guaranteed within a single trading day.
|391 - ClientBidID ● #||Optional String|
Unique identifier for a Bid Request as assigned by institution. Uniqueness must be guaranteed within a single trading day.
|420 - NoBidComponents ● #||Required NumInGroup|
Indicates the number of list entries.
|66 - ListID ● #||Optional String|
Unique identifier for list as assigned by institution, used to associate multiple individual orders. Uniqueness must be guaranteed within a single trading day. Firms which generate multi-day orders should consider embedding a date within the ListID field to assure uniqueness across days.
|421 - Country ● #||Optional Country|
ISO Country Code in field
|54 - Side ● #||Optional char|
Side of order
|44 - Price ● #||Optional Price|
Price per unit of quantity (e.g. per share)
|423 - PriceType ● #||Optional int|
Code to represent the price type
|406 - FairValue ● #||Optional Amt|
Used in EFP trades
|430 - NetGrossInd ● #||Optional int|
Code to represent whether value is net (inclusive of tax) or gross
|63 - SettlType ● #||Optional char|
Indicates order settlement period. If present, SettlDate (64) overrides this field. If both SettlType (63) and SettDate (64) are omitted, the default for SettlType (63) is 0 (Regular).
Regular is defined as the default settlement period for the particular security on the exchange of execution.
In Fixed Income the contents of this field may influence the instrument definition if the SecurityID (48) is ambiguous. In the US an active Treasury offering may be re-opened, and for a time one CUSIP will apply to both the current and "when-issued" securities. Supplying a value of "7" clarifies the instrument description; any other value or the absence of this field should cause the respondent to default to the active issue.
|64 - SettlDate ● #||Optional LocalMktDate|
Specific date of trade settlement (SettlementDate) in YYYYMMDD format. If present, this field overrides SettlType (63). This field is required if the value of SettlType (63) is 6 (Future) or 8 (Sellers Option). This field must be omitted if the value of SettlType (63) is 7 (When and If Issued). (expressed in local time at place of settlement)
|336 - TradingSessionID ● #||Optional String|
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.
|58 - Text ● #||Optional String|
Free format text string. Note: this field does not have a specified maximum length
|354 - EncodedTextLen ● #||Optional Length|
Byte length of encoded (non-ASCII characters) EncodedText (355) field.
|355 - EncodedText ● #||Optional data|
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.
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 firstname.lastname@example.org.
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.