Skip to main content
1

Request access and credentials

Contact support@blockdb.io to provision your account and delivery method (API, WebSocket, or archive).
You will receive an API key. Store it securely — use an environment variable or secret manager and never commit it to version control.
2

Set up authentication

All API requests require a Bearer token in the Authorization header. Set your key as an environment variable:
export BLOCKDB_API_KEY="your-api-key-here"
See Authorization for full token details and Rate Limiting for quota management.
3

Make your first API call

Query the latest Ethereum block to confirm connectivity:
curl -X POST https://api.blockdb.io/v1/evm/raw/blocks \
  -H "Authorization: Bearer $BLOCKDB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "chain_id": 1,
    "from_block": 21000000,
    "to_block": 21000001,
    "limit": 1
  }'
A successful response returns { "data": [...], "cursor": null, "count": 1 }. If you get a 401, check that your Authorization header is set correctly.
You received a JSON response with a data array containing block records.
4

Explore the data catalog

Use the Dataset Index and EVM Overview to find the tables and schemas relevant to your use case. Each dataset page documents available fields, lineage keys, and example queries.
5

Choose a delivery path

Pick the method that fits your workload:
  • REST API — on-demand queries, low-latency lookups, CU-based billing
  • WebSocket (WSS) — real-time streaming with Protobuf support, flat-rate plan
  • Bulk delivery — SFTP, S3, Azure, Snowflake and more; cheaper than API for large historical backfills
See Pricing for plan details.
6

Verify and monitor

Use Data Lineage and Data Verification to audit row provenance via _tracing_id. Track uptime and incidents at status.blockdb.io.
For bulk workloads, start with an archive backfill, then switch to API/WebSocket for deltas.