Skip to main content
Version: v1
Last Updated: 2025-11-27

​
Base URL

https://api.blockdb.io/v1
Use HTTPS for every request. All endpoints are POST with a JSON body and respond with an envelope containing data, cursor, and count fields for pagination.

​
Authentication

BlockDb.Historic uses OAuth 2.0 with JWT bearer tokens. Request tokens from the internal UserService and send them as an Authorization: Bearer <token> header. Tokens scope access to specific datasets, chains, and rate limits—requests without a valid token return 401.
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, block summaries, transactions, logs, contracts, and deterministic function outputs.

Tokens & Liquidity

Token registries, ERC-721 collections, pools, and normalized reserve snapshots.

Pricing Layers

Catalog discovery plus depth curves, impact grids, OHLC bars, VWAP/LWAP windows.

Lineage & Verification

Trace _tracing_id provenance and recompute receipt roots or logs blooms for integrity checks.

​
Enumerations & Shared Metadata

Most request bodies reference enumerations. Resolve IDs and codes with the dedicated reference pages:

​
Contact & Support

Reach the team at [email protected] for elevated rate limits, dataset activation, or reporting discrepancies between on-chain data and BlockDB exports.