Reference data catalogs
Use canonical reference data to populate controls, validate input, and map securities to exchanges, markets, sectors, industries, and countries. These resources expose the same values used by v3 ticker and company resources.
Choose a reference resource
Start with the type of filter, mapping, or schedule your application needs.
| Goal | Endpoint | Result |
|---|---|---|
| Resolve exchange codes and MICs | List exchanges | Exchanges, names, MICs, markets, and symbol counts. |
| Group exchanges by trading region | List markets | Market codes, ISO country codes, exchange codes, and symbol counts. |
| Populate company classifications | List sectors and list industries | Exact classification values and symbol counts. |
| Populate company-country filters | List countries | Country names, ISO codes, and symbol counts. |
| Determine an exchange's sessions | Retrieve exchange trading hours | Complete known schedule history in the exchange timezone. |
| Exclude exchange closure dates | Retrieve exchange holidays | One exchange's holiday dates. |
Build filters and market schedules
Catalog routes return complete typed collections in one response and do not use pagination. Each catalog is sorted by its code or name. Use returned values exactly when building ticker filters instead of maintaining a separate static list.
Trading hours and holiday routes take a required exchange code and return one
resource. Trading schedules belong to exchanges rather than markets, so resolve
a market to its member exchanges before requesting session data. These two
schedule routes are paid endpoints.
Company countries describe domicile, while a market's ISO country code describes the listing region. Keep those concepts separate when you build geographic filters.
Common use cases
Use reference data anywhere an application needs valid, current API values.
- Dynamic filter controls. Populate exchange, market, sector, industry, and country selectors with the exact values accepted by ticker and company resources.
- Input validation. Validate user-selected values against canonical catalogs before requesting ticker or company data.
- Exchange mapping. Map an exchange code to its MICs, display names, and trading region so applications can show both stable values and readable labels.
- Market-hours logic. Build exchange-open checks from session history, timezone, and holiday dates instead of assuming one schedule per market.
- Coverage analysis. Compare symbol counts across exchanges, markets, and classifications before defining a screening or research universe.
- Taxonomy synchronization. Refresh application taxonomies from complete catalog responses instead of shipping and maintaining hardcoded value lists.
Caching
Reference catalogs change infrequently and use a private 24-hour cache policy. Cache them in your application and refresh according to the response headers. Exchange trading-hours and holiday resources are retrieved separately for each exchange.
Next steps
Load the catalogs needed by your interface, then use their values in discovery requests.
- List exchanges and capture exchange codes.
- Map markets to exchanges.
- Retrieve trading hours and exchange holidays.
- List or search tickers with canonical reference values.