Crypto Asset & Symbols

Crypto Asset & Symbol Metadata

Access standardized cryptocurrency asset, exchange, and trading symbol metadata through CoinAPI's Market Data API.

CoinAPI helps developers discover available instruments, map exchange-specific trading pairs to standardized identifiers, understand market structure, and configure applications before retrieving trades, quotes, order books, OHLCV, exchange rates, or other crypto market data.

What Is Crypto Asset & Symbol Metadata?

Asset and symbol metadata is descriptive reference data that explains which cryptocurrency assets, exchanges, and trading instruments are available through CoinAPI and how they relate to each other.

Unlike trades, quotes, or order books, which represent individual market events, metadata describes the structure of the market data universe. It tells applications which assets are supported, which exchanges list particular instruments, what type of market each symbol represents, and which standardized identifiers should be used when requesting data.

CoinAPI provides standardized identifiers for assets, exchanges, and trading symbols. These identifiers create a consistent naming layer across exchanges, even when individual venues use different pair names, contract codes, separators, or instrument formats.

For example, one exchange may identify a Bitcoin market as BTCUSDT, another as BTC-USDT, and another through an internal numeric instrument code. CoinAPI maps supported markets into a standardized symbol_id, allowing applications to use a consistent format across venues.

Metadata also explains the relationship between instruments and their underlying assets. Developers can identify the base asset, quote asset, exchange, symbol type, precision settings, available historical range, and recent volume information where provided.

This reduces the need to maintain hardcoded exchange symbol lists or custom mapping tables. Applications can discover supported instruments dynamically, validate identifiers before making requests, and respond more easily when exchanges add, remove, or modify markets.

Asset and symbol metadata is therefore useful for market discovery, search, autocomplete, watchlists, portfolio setup, automated trading configuration, exchange mapping, analytics pipelines, data validation, and multi-exchange market data applications.

What's Included in CoinAPI Asset & Symbol Metadata?

Depending on the endpoint and available source information, CoinAPI returns standardized asset identifiers, exchange identifiers, symbol identifiers, instrument classifications, asset relationships, precision settings, data availability ranges, and volume statistics.

FieldWhat it means
asset_idStandardized CoinAPI identifier for an asset, such as BTC, ETH, or USD
symbol_idUnique CoinAPI identifier for a trading instrument, such as BINANCE_SPOT_BTC_USDT
exchange_idIdentifier of the exchange where the instrument is listed
symbol_typeInstrument classification, such as SPOT, FUTURES, PERPETUAL, OPTION, or INDEX
asset_id_baseBase asset in the trading pair, such as BTC in BTC/USDT
asset_id_quoteQuote asset used to price the base asset, such as USDT in BTC/USDT
price_precisionPrecision or number of decimal places supported for prices
size_precisionPrecision or number of decimal places supported for order and trade sizes
data_startEarliest available market data date or timestamp for the symbol
data_endLatest available market data date or timestamp for the symbol
volume_1hrs_usdEstimated one-hour trading volume in USD where available
volume_1day_usdEstimated one-day trading volume in USD where available
volume_1mth_usdEstimated one-month trading volume in USD where available

Together, these fields allow developers to discover supported markets, resolve valid API identifiers, understand how instruments are structured, compare exchange coverage, and configure downstream market data requests.

Available REST Endpoints

CoinAPI provides REST metadata endpoints for discovering supported assets, exchanges, symbols, and related market reference information.

Assets

Returns cryptocurrency, fiat currency, and other asset identifiers available within CoinAPI.

Response includes
  • standardized asset identifiers
  • asset names and classifications where available
  • metadata useful for resolving assets across CoinAPI datasets

Use the Assets endpoint to discover valid asset_id values before requesting asset-specific data. Asset identifiers are used throughout Exchange Rates, Symbols, OHLCV, Trades, Quotes, Order Books, Indexes, and Market Metrics.

Exchanges

Returns exchanges and market data sources supported by CoinAPI.

Response includes
  • standardized exchange_id
  • exchange name
  • website information where available
  • data availability information
  • volume information where available

The exchange identifier connects symbol metadata to the venue where an instrument is listed. Use it when building exchange selectors, coverage dashboards, venue comparisons, or exchange-specific instrument discovery.

Symbols

Returns standardized trading symbols available across supported exchanges.

Response includes
  • symbol_id
  • exchange_id
  • symbol_type
  • asset_id_base
  • asset_id_quote
  • price and size precision
  • data availability range
  • recent volume information where available

The symbol_id is the primary identifier used when requesting market data for a specific instrument. CoinAPI standardizes it even when exchanges use different native naming conventions, so one application works with many exchanges without a per-venue naming parser.

Exchange-Specific Symbol Discovery

Returns symbols associated with a selected exchange.

Response includes
  • instruments listed on the exchange
  • standardized symbol identifiers
  • base and quote assets
  • instrument classifications
  • precision information
  • data availability information where available

Useful when building exchange-specific market browsers, symbol search tools, trading pair selectors, watchlists, or onboarding workflows — instead of relying on a fixed symbol list that becomes outdated.

Asset-Specific Symbol Discovery

Allows applications to identify trading symbols associated with a selected asset.

Response includes
  • exchanges listing the asset
  • available trading pairs
  • base and quote relationships
  • instrument types
  • standardized symbol_id values

Find every supported market involving an asset such as BTC, ETH, USDT, or USD. Particularly useful for asset profile pages, market comparison tools, liquidity analysis, and exchange coverage dashboards.

Browse Symbols by Exchange

Use CoinAPI symbol metadata to discover the instruments available on each supported exchange before requesting trades, quotes, order books, OHLCV, or other market data.

An exchange-specific symbol browser can help developers:

  • identify valid CoinAPI symbol_id values
  • compare instrument coverage between venues
  • distinguish spot, futures, perpetual, option, and index markets
  • find base and quote asset relationships
  • inspect precision and historical availability
  • avoid requests for unsupported instruments

Applications can use metadata discovery instead of relying on a fixed symbol list that becomes outdated whenever an exchange launches or removes a market.

CoinAPI Asset & Symbol Metadata Dataset Characteristics

  • Available through CoinAPI Market Data API metadata endpoints
  • Provides standardized asset, exchange, and symbol identifiers
  • Supports discovery of available cryptocurrency and fiat assets
  • Maps exchange-native instrument names into consistent CoinAPI symbol_id values
  • Includes base and quote asset relationships
  • Includes instrument classifications such as spot, futures, perpetuals, options, and indexes where available
  • Includes price and size precision information
  • Includes historical data availability ranges for supported symbols
  • Includes recent volume information where available
  • Supports exchange-specific and asset-specific market discovery
  • Helps validate API inputs before requesting market data
  • Reduces dependency on hardcoded symbol lists
  • Provides the reference layer used by Trades, Quotes, Order Books, OHLCV, Exchange Rates, Indexes, and other datasets
  • Can be cached and refreshed separately from high-frequency market data

Why Developers Use Standardized Metadata

Every exchange represents instruments differently. Native exchange symbols may use different separators, abbreviations, contract names, settlement asset codes, expiration formats, or internal identifiers. Even markets representing the same economic pair may be named differently across venues.

CoinAPI provides a standardized metadata layer that separates an application from these venue-specific conventions.

If you need…Use
A list of supported cryptocurrency and fiat assetsAsset metadata
A list of supported trading venuesExchange metadata
Valid identifiers for market data requestsSymbol metadata
Markets listed on a particular exchangeExchange-specific symbol discovery
All markets involving a selected assetAsset-specific symbol discovery
Base and quote asset relationshipsSymbol metadata
Spot, futures, perpetual, or option classificationsymbol_type
Available historical coveragedata_start and data_end
Price and order-size configurationPrecision fields
Markets ranked by recent activityVolume fields where available

Standardized metadata makes applications easier to extend. Adding support for another exchange does not require redesigning the application's internal symbol model — new exchange and symbol records flow through the same discovery workflow already used for existing venues.

Metadata Before Market Data

Metadata is usually one of the first datasets an application should retrieve.

Before requesting trades, quotes, order books, or OHLCV, the application must determine:

  • whether the exchange is supported
  • whether the instrument exists
  • which symbol_id should be used
  • whether the instrument is spot, perpetual, futures, option, or another type
  • which assets form the trading pair
  • whether historical data is available for the requested period

This validation step reduces failed requests, incorrect symbol mappings, duplicate instruments, and inconsistent exchange naming.

Metadata changes less frequently than live market data, so many applications store it locally and refresh it on a schedule. Market data streams can then reference the cached CoinAPI identifiers without repeatedly resolving native exchange symbols.

Standardized Symbols Across Exchanges

A multi-exchange application cannot safely assume that every venue follows the same naming rules.

Differences may include:

  • pair order
  • separators
  • contract suffixes
  • settlement currencies
  • maturity dates
  • perpetual contract naming
  • option strike and expiration formats
  • exchange-specific internal codes

CoinAPI's symbol_id creates a standardized representation that combines the exchange, instrument type, and relevant asset information, giving developers a consistent identifier for requesting and storing market data across many venues.

This format is particularly useful in data warehouses, analytics pipelines, research datasets, trading applications, and AI systems where records from multiple exchanges must be joined or compared.

Crypto Asset & Symbol Metadata Use Cases

  • Discover supported markets
  • Build symbol search and autocomplete
  • Configure trading applications
  • Build watchlists and portfolios
  • Validate data pipelines
  • Compare exchange coverage

Who Uses Crypto Asset & Symbol Metadata?

  • Cryptocurrency trading platforms
  • Quantitative funds
  • Portfolio and wealth applications
  • Market data platforms
  • Researchers and analysts
  • AI and machine learning teams
Crypto Asset & Symbols

Start with Metadata. Build Everything Else.

Trades, quotes, order books, OHLCV, exchange rates, and market metrics all depend on accurate asset and symbol identifiers. CoinAPI's standardized metadata provides the foundation for every other Market Data API dataset, helping developers discover supported markets, validate requests, and integrate hundreds of exchanges through a single, consistent data model.

Build your applications on reliable reference data first, and spend less time maintaining symbol mappings and exchange-specific logic.