| ID | 295 |
The Instrument holds basic background information, such as instrument id, type and (optionally) primary market for an instrument. Since an instrument can be traded in different currencies and visibility (normal, dark etc), the instrument has a set of child objects called TradableInstrument in which the actual trading takes place. An Instrument may reference another Instrument using the ""parentInternalId"" attribute. The parentInternalId is typically used by warrants or options to reference the underlying instrument.
Field | Name | Type | Req'd | Comments | Pedigree |
|---|---|---|---|---|---|
300 | Is used to identify the parent object (is set to null if this is the root object). This field is set by RTC, only set on outgoing messages on the reference data flow. | ||||
61 | Is used to identify the reference data cache. This field is set by RTC, only set on outgoing messages on the reference data flow. | ||||
13 | Identify the reason for the cache action (CACHE_ACTION), i.e. if it is an addition of a new reference data object, an update of an existing object or a removal of an object from the reference data cache. This field is set by RTC, only set on outgoing messages on the reference data flow. | ||||
509 | A sequence number that is incremented with each reference data update, i.e. a version number for the cache contents. The sequence number series is common for all caches. This means that for a specific cache instance, the sequence number is not necessarily consecutive (but constantly increasing). This field is set by RTC, only set on outgoing messages on the reference data flow. | ||||
604 | The id is unique among all objects and may be used to retrieve a specific instance. Do not however, try to interpret the contents. This field is set by RTC, only set on outgoing messages on the reference data flow. | ||||
544 | The date and time of the latest modification for this reference data object. Format: yyyy-mm-ddTHH.MM.SS.sss. May be null if the object never has been updated. This field is set by RTC, only set on outgoing messages on the reference data flow. | ||||
272 | A unique instrument identifier. May be an ISIN, CUSIP or symbol name. The InternalID is created using the InstrumentID and InstrumentIdType fields. Example: SE0000108656_ISIN | ||||
384 | This is a reference to the parent instrument, if any. A parent instrument is typically an underlying instrument when trading derivatives. Shall be set to null if this instrument is a "root" instrument. | ||||
288 | The state of this item. | ||||
156 | Not used in this configuration of RTC. | ||||
255 | Y | The global identity of the instrument. The type of identifier (ISIN, CUSIP etc) is defined by the instrumentIdType attribute. | |||
256 | Y | The type of the InstrumentId (ISIN, CUSIP etc) | |||
416 | Not used in this configuration of RTC. | ||||
417 | Not used in this configuration of RTC. | ||||
600 | Y | The type of instrument (equity, warrant, future etc). | |||
499 | Y | The short display name for the instrument, ERICB for example. | |||
353 | Y | The complete instrument name, Ericsson B for example. | |||
295 | The issuer of the instrument | ||||
470 | The financial sector to which the instrument belong | ||||
429 | A unique id that defines market/market that is to be considered primary for the instrument, XLON, XSSE for example.) | ||||
19 | Not used in this configuration of RTC. This field is a fixed point number with a scaling factor equal to 1/DIVISOR.PRICE. | ||||
20 | Not used in this configuration of RTC. | ||||
610 | Y | The first date the instrument is valid. The format is yyyy-MM-dd. | |||
611 | The last date the instrument is valid. The format is yyyy-MM-dd. | ||||
312 | A list of other markets'/exchanges' ID of this instrument in the format: market1:id1,market2:id2,... | ||||
397 | The instrument partition for the Position Manager server. | ||||
466 | The RTC internal ID for the underlying product. |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy