Exchange & Symbol Metadata

Discover Supported Stock Exchanges and Trading Symbols

Exchange & Symbol Metadata provides the foundation for working with the FinFeedAPI Stock Historical API. Retrieve standardized information about supported exchanges, listed stock symbols, trading history availability, and market identifiers before requesting OHLCV data or Native IEX datasets.

The metadata endpoints help developers discover available markets, validate requests, build symbol search functionality, synchronize reference databases, and understand historical data coverage across supported exchanges.

Explore Documentation Get Your API Key

What Is Exchange & Symbol Metadata?

Exchange and Symbol Metadata provide the reference information needed to work with the Stock Historical API.

Exchange Metadata identifies supported trading venues and their standardized identifiers, while Symbol Metadata identifies the securities available on those exchanges. Together, they help applications discover supported markets, validate identifiers, and determine which exchange and symbol combinations can be used when requesting historical data.

Unlike historical market datasets, metadata does not contain trades, quotes, order books, or OHLCV records. It provides the reference layer applications use before requesting that data.

What's Included?

Exchange Metadata includes standardized information about each supported venue, such as its FinFeedAPI exchange identifier, MIC codes, market name, category, country, city, and website.

Symbol Metadata provides information about individual securities, including the symbol identifier, associated exchange, security category, issuer name, and metadata date. CSV datasets may also include additional fields such as asset class and whether the security is currently enabled.

These fields make it easier to map exchanges and securities consistently across historical data requests.

Exchange Metadata

Field	What it means
exchange_id	Unique FinFeedAPI identifier for the exchange (e.g., IEXG, XNAS).
mic	ISO 10383 Market Identifier Code for the exchange.
operating_mic	Operating Market Identifier Code.
oprt_sgmt	Operating segment code (OPRT for operational segments).
legal_entity_name	Full legal registered name of the exchange entity.
market_name_institution_description	Official institution description or market name.
market_category_code	Classification code for the market category (e.g., NSPD, RMKT, MLTF).
acronym	Standard shorthand acronym for the market (e.g., IEX, NASDAQ).
iso_country_code	Two-letter ISO country code where the venue is located (e.g., US, PL).
city	City where the exchange is headquartered.
website	Official website web address for the exchange.

Symbol Metadata

Field	What it means
symbol_id	Standardized ticker symbol identifier (e.g., AAPL, TSLA, NVDA).
exchange_id	Identifier of the exchange where the symbol is listed (e.g., IEXG).
security_category	Instrument classification (e.g., Common Stock, ETF, Bond).
name	Full legal or corporate name of the security issuer.
date	ISO 8601 UTC date associated with the symbol metadata record (YYYY-MM-DD).
asset_class (CSV only)	Asset class classification for internal security master mapping.
is_enabled (CSV only)	Boolean flag indicating whether the security is active for data requests.

Available REST Endpoints

FinFeedAPI provides dedicated REST endpoints for discovering supported exchanges and listed symbols.

List Exchanges

Returns every exchange supported by the Stock Historical API together with reference information and historical data availability.

Response includes

exchange identifiers
exchange names
country
website
historical data availability
supported dataset types

List Symbols

Returns all supported stock symbols for a selected exchange.

Response includes

exchange symbol identifiers
stock ticker symbols
company names

MCP & JSON-RPC Support

Exchange and Symbol Metadata are available through every interface supported by the Stock Historical API.

MCP Server

The hosted Stock Historical MCP Server exposes dedicated discovery tools for exchanges and symbols, allowing AI applications to explore available markets before requesting historical datasets.

Rather than hardcoding exchange or symbol identifiers, AI agents can discover supported exchanges first, retrieve the corresponding symbol catalog, and then use those identifiers when requesting OHLCV data or Native IEX datasets. This discovery-first workflow reduces invalid requests and allows applications to automatically adapt as reference data evolves.

JSON-RPC

Exchange and Symbol Metadata are also available through the JSON-RPC endpoint.

The JSON-RPC gateway exposes the same metadata operations as the REST API while using the JSON-RPC request format. Regardless of transport protocol, developers receive the same standardized metadata structure, making it straightforward to switch between REST and JSON-RPC without changing application logic.

Dataset Characteristics

Standardized exchange reference data
Standardized stock symbol metadata
Exchange discovery endpoint
Exchange-specific symbol discovery endpoint
Available through REST API, JSON-RPC, and hosted MCP Server
Consistent identifiers used throughout the Stock Historical API
Historical data availability information
API key authentication required
Supports application discovery, validation, and synchronization workflows

Why Developers Use Exchange & Symbol Metadata

Metadata endpoints provide the reference information needed before requesting historical market data.

If you need...	Use...
Discover supported exchanges	Exchange Metadata
Retrieve symbols listed on an exchange	Symbol Metadata
Validate exchange identifiers	Exchange Metadata
Build stock symbol search	Symbol Metadata
Synchronize reference databases	Exchange & Symbol Metadata
Retrieve historical candles	OHLCV Historical Data
Retrieve historical trade executions	Native IEX Trades

Most production systems periodically synchronize metadata so applications always operate with the latest supported exchanges and symbols before requesting historical datasets.

Common Use Cases

Build exchange and symbol search interfaces
Synchronize internal security master databases
Validate API requests before retrieving market data
Discover supported exchanges automatically
Populate trading application dropdowns
Keep market reference data up to date

Who Uses This Dataset?

Market Data Platforms
Trading Application Developers
Financial Data Engineers
Quantitative Research Teams
Enterprise Integration Teams

Exchange & Symbol Metadata

Explore Exchange & Symbol Metadata

Exchange & Symbol Metadata provides the reference layer for the FinFeedAPI Stock Historical API.

By discovering supported exchanges, listed securities, and standardized identifiers before requesting historical datasets, developers can build more reliable integrations while simplifying access to OHLCV data, Native IEX datasets, and the rest of the Stock Historical ecosystem.