Skip to main content
Version: Next

Instrument

A financial instrument from any asset class.

Schema

https://fdc3.finos.org/schemas/next/context/instrument.schema.json (github)

Type

fdc3.instrument

Properties

id (required)

type: object

Subproperties:

BBG
CUSIP
FDS_ID
FIGI
ISIN
PERMID
RIC
SEDOL
ticker

type: string

Unstandardized stock tickers

Any combination of instrument identifiers can be used together to resolve ambiguity, or for a better match. Not all applications will use the same instrument identifiers, which is why FDC3 allows for multiple to be specified. In general, the more identifiers an application can provide, the easier it will be to achieve interoperability.

It is valid to include extra properties and metadata as part of the instrument payload, but the minimum requirement is for at least one instrument identifier to be provided.

Try to only use instrument identifiers as intended. E.g. the ticker property is meant for tickers as used by an exchange. If the identifier you want to share is not a ticker or one of the other standardized fields, define a property that makes it clear what the value represents. Doing so will make interpretation easier for the developers of target applications.

market

type: object

Subproperties:

MIC
name

type: string

Human readable market name

COUNTRY_ISOALPHA2
BBG

The market map can be used to further specify the instrument and help achieve interoperability between disparate data sources. This is especially useful when using an id field that is not globally unique.

Example

{
"type": "fdc3.instrument",
"name": "Microsoft",
"id": {
"ticker": "MSFT",
"RIC": "MSFT.OQ",
"ISIN": "US5949181045"
},
"market": {
"MIC": "XNAS"
}
}