Skip to main content

​
Description

Enumerations provide canonical reference data used across BlockDB API requests and responses. These identifiers ensure consistent data classification and enable filtering across datasets. All enumeration values are stable and versioned independently from dataset schemas.

​
Enumeration Reference

EnumerationDescriptionUse Cases
ChainSupported EVM chain IDs compatible with ChainListFilter datasets by network, specify chain_id in all requests
Digital ExchangeDEX protocol identifiers for pools and price feedsFilter reserves and pricing data by exchange type
Dataset IDCanonical dataset identifiers mapping to API endpointsReference datasets in lineage and catalog queries
Pool TypeAMM pool archetype classificationsFilter pools and reserves by liquidity model
Asset ClassAsset type identifiers (ERC-20, NFT, fiat, native)Construct price request descriptors
Fiat CurrencyISO 4217 fiat currency codesSpecify quote currencies in pricing endpoints
Market KindMarket classification (spot, derivative, etc.)Scope pricing queries to specific market surfaces

​
Parameter Conventions

  • Enumeration values are case-sensitive and must match exactly as documented
  • Use numeric IDs for chain, exchange, and pool type enumerations
  • Use string codes for asset class, fiat currency, and market kind
  • All enumeration values are immutable within a major version

​
Usage Guidance

  • Cache enumerations client-side — values change infrequently and can be cached for extended periods
  • Validate before requests — check that enumeration values exist before constructing API requests to avoid 400 Bad Request errors
  • Reference in filters — use enumeration IDs in request body filters (e.g., exchange_ids, pool_type_ids) rather than hardcoding values
  • Monitor updates — subscribe to Release Notes for new enumeration values or deprecations

​
See Also