Symbology

The reference datasets support querying by raw_symbol and additionally symbology types listed in the below table (depending on the endpoint).

The raw_symbol symbology type uses a standardized convention for the symbols parameter for requests. This convention is referred to as the "Nasdaq Integrated Platform Suffix" and is used consistently across our datasets, regardless of the suffix originally used by the exchange.

  • Standardization. This approach aligns with our symbology standardization for US equity datasets. For a detailed explanation, see our symbology standards documentation.
  • Local Codes. The local_code field retains the original symbol from the primary exchange. For example, symbols from NYSE-owned feeds such as NYSE Texas use the "CMS Suffix".

For additional context on symbol conventions, including the four most common suffix patterns used for US equities, refer to Nasdaq's guide on ticker symbol conventions.

The symbology related fields included with every data record are as follows:

Field
Description
nasdaq_symbol
Nasdaq Integrated Platform Suffix convention symbol (standardized raw_symbol).
local_code
Local code, typically the original symbol and unique at the listing level (but there are exceptions to this rule). Either an alpha string, or a number.
isin
us_code
bbg_comp_id
Bloomberg composite global ID.
bbg_comp_ticker
Bloomberg composite ticker.
figi
Financial Instrument Global Identifier (FIGI), formerly Bloomberg Global Identifier (BBGID). Listing level identifier.
figi_ticker
Bloomberg exchange-level ticker.
listing_id
Databento-specific identifier that tracks an individual exchange's listing of a security.
issuer_id
Databento-specific identifier shared across all securities issued by the same company.
security_id
Databento-specific identifier at the security level, tracking a security across all of its exchange listings.
Info

Note a symbol may match multiple securities across a time range if the symbol has been recycled.

Tip

When identifying a listing on a specific venue, we suggest using the nasdaq_symbol field, as it aligns with the normalized raw_symbol for instruments. Once you have the ISIN for the security, using the isin symbology type will provide the most accurate results when querying for related records.