Skip to main content

​
DatasetId Enumeration

Defines the canonical dataset identifiers used across Historic API responses (e.g., the dataset field and lineage payloads). Each identifier maps to a documented REST endpoint. The prefix indicates the functional domain:
  • 01xx — base chain primitives (blocks, transactions, logs, traces)
  • 02xx — pool, token, and contract metadata
  • 03xx — liquidity and reserve snapshots
  • 04xx — spot price discovery
  • 05xx — advanced price analytics
  • 06xx — advanced price analytics with fiat quote conversion
ValueDescriptionNotes
0101POST /evm/raw/blocksCanonical block headers and integrity metadata.
—POST /evm/raw/blocks/summaryDerived view over 0101.
0102POST /evm/raw/transactionsExecuted transactions with provenance fields.
0103POST /evm/raw/logsEvent logs emitted by smart contracts.
0104POST /evm/raw/contractsDeployed smart contract metadata keyed by address.
0105POST /evm/raw/function-resultsContract call return values versioned by block.
0201POST /evm/tokens/erc20ERC-20 token metadata snapshots.
0202POST /evm/tokens/erc721ERC-721 collection metadata and mint provenance.
0203POST /evm/poolsAMM and liquidity pool descriptions.
0301POST /evm/reservesPool reserve balances and liquidity metrics.
0401POST /evm/prices/spot/crypto/depthOrderbook-style depth snapshots for spot pairs.
0402POST /evm/prices/spot/crypto/impact-gridPrice impact across notional sizes.
0403POST /evm/prices/spot/crypto/ohlcCandlestick aggregates for spot markets.
0501POST /evm/prices/spot/crypto/vwapVolume-weighted average prices over windows.
0502POST /evm/prices/spot/crypto/lwapLiquidity-weighted average prices across depth bands.
0601POST /evm/prices/spot/fiat/ohlcCandlestick aggregates for spot markets (in USD, EUR etc.).
0602POST /evm/prices/spot/fiat/vwapVolume-weighted average prices over windows (in USD, EUR etc.).
0603POST /evm/prices/spot/fiat/lwapLiquidity-weighted average prices across depth bands (in USD, EUR etc.).

​
Usage Notes

  • Responses and lineage records that expose a dataset field will always use one of the identifiers above.
  • Entries marked with — represent derived views that do not emit a dedicated dataset identifier.
  • New datasets follow the same prefix scheme; clients should tolerate unknown IDs to remain forward compatible.
  • Use this enumeration to drive UI labels and access control lists rather than hardcoding endpoint prefixes.