Exchange Metadata

Discover cryptocurrency exchanges, data coverage, trading symbols, and historical availability through one API.

CoinAPI Exchange Metadata provides standardized information about cryptocurrency exchanges and trading venues available across the CoinAPI platform.

Use exchange metadata to discover supported exchanges, retrieve normalized exchange identifiers, inspect historical data coverage, compare trading activity, check symbol availability, and prepare applications before requesting data. Instead of maintaining separate exchange lists, native identifiers, coverage records, and instrument mappings, developers can access exchange-level information through one consistent API.

Explore the Docs Get Your API Key

What Is Cryptocurrency Exchange Metadata?

Cryptocurrency exchange metadata describes the trading venues available through a market data platform. It provides the information required to identify an exchange, understand its available market data, determine how far its historical coverage extends, and discover which trading instruments belong to that venue.

Unlike market data such as trades, quotes, or order books, exchange metadata changes relatively infrequently. Instead of describing market activity, it acts as reference data that helps applications discover available exchanges, validate identifiers, and configure data requests before retrieving live or historical market data.

A typical workflow begins by discovering exchanges, selecting a venue, retrieving its supported symbols, and then requesting trades, quotes, order books, OHLCV, or market metrics for the relevant instruments.

Exchange metadata is particularly useful for applications that support multiple trading venues. Rather than maintaining hardcoded exchange lists, developers can retrieve standardized metadata dynamically, making it easier to add support for new exchanges, compare venue coverage, build exchange selectors, and keep applications synchronized as markets evolve.

What Is Included in CoinAPI Exchange Metadata?

CoinAPI Exchange Metadata includes identification, historical coverage, symbol availability, trading activity, ranking, and integration information for supported exchanges.

Field	Description
exchange_id	Unique normalized CoinAPI identifier for the exchange, such as BINANCE or KRAKEN
name	Human-readable exchange name
website	Official exchange website
data_quote_start	Earliest available quote data timestamp
data_quote_end	Latest available quote data timestamp
data_orderbook_start	Earliest available order book data timestamp
data_orderbook_end	Latest available order book data timestamp
data_trade_start	Earliest available trade data timestamp
data_trade_end	Latest available trade data timestamp
data_symbols_count	Number of symbols or instruments associated with the exchange
volume_1hrs_usd	Estimated trading volume in USD over the last hour
volume_1day_usd	Estimated trading volume in USD over the last day
volume_1mth_usd	Estimated trading volume in USD over the last month
rank	Exchange ranking indicator
integration_status	Current CoinAPI integration status, such as INTEGRATED

Endpoints

Exchange Metadata Endpoints — Market Data API

Exchange metadata is primarily available through the CoinAPI Market Data API and Indexes API.

Endpoint	Purpose
GET /v1/exchanges	Retrieve metadata for all exchanges available through CoinAPI
GET /v1/exchanges/{exchange_id}	Retrieve metadata for one specific exchange
GET /v1/exchanges/icons/{size}	Retrieve exchange icons in the selected size
GET /v1/symbols	Retrieve normalized symbol and instrument metadata across exchanges
Exchange-scoped symbol metadata endpoint	Retrieve symbols associated with a selected exchange
Exchange metrics endpoints	Retrieve exchange-level metric definitions, current values, and historical values

Endpoints

Exchange Metadata Endpoints — Indexes API

Endpoint	Purpose
GET /api/metadata/exchanges	Retrieve exchange metadata used by the CoinAPI Indexes API
GET /api/metadata/exchanges/{exchange_id}	Retrieve Indexes API metadata for a specific exchange

Exchange metadata in the Indexes API can support benchmark logic, exchange selection, market eligibility analysis, and constituent research.

How Exchange Metadata Works with Symbol Metadata

An exchange identifies the trading venue. A symbol identifies a specific tradable instrument on that venue. For example:

symbol_id

BINANCE_SPOT_BTC_USDT

This normalized CoinAPI symbol identifier describes a Bitcoin and Tether spot market available on Binance. Exchange Metadata helps applications identify the venue and understand its overall coverage. Symbol Metadata provides the instrument-level detail required to request actual market data.

Typical Symbol Metadata Fields

Field	Description
symbol_id	CoinAPI normalized symbol identifier
exchange_id	Exchange where the instrument is traded
symbol_type	Instrument type, such as SPOT, FUTURES, PERPETUAL, or OPTION
asset_id_base	Base asset identifier, such as BTC
asset_id_quote	Quote asset identifier, such as USDT
symbol_id_exchange	Native symbol identifier used by the exchange
price_precision	Supported price precision
size_precision	Supported order or trade size precision
data_start	Earliest available data for the symbol
data_end	Latest available data for the symbol
volume_1day_usd	Recent estimated trading volume in USD
price	Latest or estimated instrument price

From Venue Discovery to Market Data

Together, exchange and symbol metadata allow applications to move from venue discovery to instrument discovery and then to market data retrieval. A common sequence is:

Retrieve the available exchanges.
Select an exchange_id.
Retrieve symbols associated with that exchange.
Filter by instrument type, asset, or trading pair.
Request historical or real-time market data for the selected symbol_id.

This removes the need to maintain separate symbol mappings and native exchange naming conventions inside the application.

Check Market Data Coverage Before Making a Request

Historical cryptocurrency data coverage varies by exchange, instrument, and data type. One exchange may provide trades dating back several years while its quote or order book history begins later. Another may support thousands of active symbols but only a smaller subset of historical instruments.

Exchange metadata helps applications verify coverage before requesting large historical datasets. This is especially important for backtesting, quantitative research, market reconstruction, and bulk historical data workflows.

Developers can inspect:

Trade data start and end dates
Quote data start and end dates
Order book data start and end dates
Number of available symbols
Current integration status
Recent estimated exchange volume
Exchange ranking

Instead of discovering missing coverage after submitting a query, applications can evaluate exchange-level availability first and build more reliable data collection logic.

Across the Platform

Use Exchange Metadata Across CoinAPI Products

Exchange Metadata supports several products and delivery methods across the CoinAPI platform.

Market Data API

Exchange Metadata is a foundational dataset within the Market Data API.

Use it before accessing:

Trades
Quotes and Level 1 market data
Level 2 and Level 3 order books
OHLCV candles
Symbols and instruments
Historical REST data
Real-time WebSocket streams
Exchange-level market metrics

WebSocket Market Data

Real-time applications can retrieve exchanges and symbols first, then subscribe to selected instruments through the CoinAPI WebSocket API.

This allows a system to validate exchange and symbol identifiers before opening large real-time subscriptions.

Flat Files

Exchange Metadata is not itself a Flat Files market dataset, but its normalized identifiers and coverage information help users select the correct historical files.

Relevant identifiers include:

exchange_id
symbol_id
Symbol mappings
Exchange coverage dates

These fields support bulk data downloads, historical research, backtesting, and long-term storage workflows.

Indexes API

The CoinAPI Indexes API uses exchange metadata in workflows where index construction, benchmark methodology, eligible trading venues, and constituent selection depend on exchange-level information.

Example

Example Exchange Metadata Response

The following example shows the structure of an exchange metadata response for Binance.

Applications can use this response to confirm the normalized exchange identifier, inspect historical coverage, estimate venue activity, and determine how many instruments are available before retrieving symbol-level data.

exchange-metadata.json

[
  {
    "exchange_id": "BINANCE",
    "website": "https://www.binance.com/",
    "name": "Binance",
    "data_quote_start": "2017-12-18T00:00:00.0000000Z",
    "data_quote_end": "2025-08-21T00:00:00.0000000Z",
    "data_orderbook_start": "2017-12-18T00:00:00.0000000Z",
    "data_orderbook_end": "2025-08-21T00:00:00.0000000Z",
    "data_trade_start": "2017-07-14T00:00:00.0000000Z",
    "data_trade_end": "2025-08-21T00:00:00.0000000Z",
    "data_symbols_count": 3240,
    "volume_1hrs_usd": 157482489.63,
    "volume_1day_usd": 5358147539.83,
    "volume_1mth_usd": 733858370166.07,
    "rank": 2,
    "integration_status": "INTEGRATED"
  }
]

Coverage dates, volumes, rankings, and symbol counts change over time and should be retrieved directly from the API when making production decisions.

Crypto Exchange Metadata Use Cases

Discover supported cryptocurrency exchanges
Validate historical data availability
Build exchange selection interfaces
Map native exchanges to normalized IDs
Filter symbols by exchange
Compare cryptocurrency exchanges
Prepare real-time subscriptions

Who Uses Crypto Exchange Metadata?

Trading platforms
Quantitative trading firms
Hedge funds and asset managers
Brokers and fintech platforms
Data and analytics providers
Academic researchers
AI and machine learning teams

Exchange Metadata

Explore CoinAPI Exchange Metadata

Start with Exchange Metadata to discover supported cryptocurrency exchanges, inspect available historical coverage, retrieve normalized exchange identifiers, and connect each venue to its available trading symbols.

From there, use the same CoinAPI platform to access trades, quotes, order books, OHLCV, market metrics, real-time WebSocket streams, and bulk historical datasets.