Skip to main content
Version: v1
Last Updated: 2026-04-02

​
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, 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_id routing.

​
Enumerations & shared metadata

​
Contact & support

support@blockdb.io
Last modified on April 6, 2026