Blockchain Data API reference

Overview

Use this Blockchain Data API reference to construct REST requests for indexed blocks, transactions, addresses, tokens, NFTs, DEX activity, tokenized stocks and dataset freshness. To choose a dataset and check chain availability, start with the datasets directory; for wallet token balances and transfer history, follow the wallet assets guide.

• Base URL: https://api.blockvectra.com/v1/data — every route except /chains is prefixed with a chain identifier (e.g. https://api.blockvectra.com/v1/data/{chain}/…)
• Protocol: HTTP GET (plus POST for batch token lookups at /{chain}/tokens:batch), JSON responses
• Authentication: API key required — pass your key in the x-api-key request header. Requests are metered and billed in Compute Units (CU); only 2xx successful responses are billed
• Ethereum: data coverage is determined by coverage.from_block in GET /v1/data/chains, and covers a smaller set of datasets — see Supported Chains → Ethereum
• TypeScript SDK (GitHub) · Daily DEX price example · npm · WETH/USDG · robinhood_mainnet · 2026-10-01 UTC · JSON

npm install @blockvectra/data-api

Need cursor-based history? The checkpointed ERC-20 transfers example saves one page and its original meta per run, then resumes from the same opaque cursor when you rerun it with the same fixed query and state file. Pagination exhaustion alone does not prove a complete history — check coverage separately. ERC-20 only. Install the prebuilt package to run it directly; no local schema generation or source build.

Data API CU weights are listed on the Pricing page and returned by GET /v1/plans. See Quickstart → Call the Data API for example requests and response shapes. For path versioning, backward compatibility rules, and SDK recommendations, see API versioning and compatibility.

Chains

The Data API serves indexed data scoped to each chain: https://api.blockvectra.com/v1/data/{chain}/….

Available datasets and features vary by chain; see Supported Chains for the full capability matrix. GET https://api.blockvectra.com/v1/data/chains reports each chain's features, coverage, finality and limits. Requests outside a dataset's coverage return HTTP 422 no_coverage (not billed); an unknown or not-public chain returns HTTP 404 with error.code not_found (not billed; chain names must be exact lowercase slugs).

Errors

Every error response is {"error":{"code","message"}}; only 409 not_indexed_yet may add indexed_through (the highest indexed block on that chain), and it is absent when the chain has no indexed data yet. Codes customers hit most often:

Endpoint index