v1Last Updated:
2026-05-12
Base URL
POST with a JSON body and typically return an envelope with data, cursor, and count for pagination. Account endpoints such as GET /usage and GET /health use GET with no body.
Authentication
Authentication uses API keys issued by the BlockDB team when your plan is activated (up to five active keys per account). Send the key on every request asAuthorization: Bearer <API_KEY>. Entitlements (datasets and chains) are tied to your account; monthly compute units and RPS are account-wide and shared across all keys—you cannot assign separate usage or rate limits to individual keys. Requests without a valid key return 401. See Authorization and Rate limiting.
The API never accepts query parameters for filters. Always place filters in the JSON body (for example,
chain_id, block ranges, or address lists).Endpoint families
Ledger & execution
Blocks, transactions, logs, internal traces, contracts, and function results.
Tokens & liquidity
ERC-20/721/1155 registries, pools, fee terms, reserves, transfers, and swap fees.
Pricing & TVL
Swap prints, OHLC, per-pool and cross-pool VWAP, token-to-USD VWAP, yields, and TVL.
Flash loans & arbitrage
Flash loan prints, arb paths, path status, and opportunities.
Lineage, verification, and JSON-RPC
- Lineage — Resolve records, genesis artifacts, and parent graphs from
_tracing_id. - Verification — Recompute receipt trie roots and log blooms for integrity checks.
- JSON-RPC — Proxied Ethereum JSON-RPC methods with
chain_idrouting.
Enumerations & shared metadata
- Dataset index — All EVM dataset IDs,
blockdb_evmtable names, and catalog links - Chain
- Digital Exchange
- Dataset ID
- Pool Type
- Asset Class
- Fiat Currency
- Market Kind