Skip to main content

Overview

BlockDB authenticates REST and WebSocket traffic with API keys. Send your key in the Authorization header on every request that requires authentication. Keys are tied to your subscription: which datasets and chains you can query, your compute unit allowance, and your rate limit. See the dataset index and Dataset ID for how products map to blockdb_evm tables.
There is no separate token endpoint and no OAuth flow. The key issued to you is the credential you pass as Bearer <key>.

Get an account and API keys

1

Choose a plan

API access is available on a custom plan. Email support@blockdb.io with the datasets, chains, and volume you need.
2

Receive and manage your keys

Your API key is issued when your plan is activated. Email support@blockdb.io to:
  • Request additional keys (up to 5 active keys per account)
  • Label keys (for example production vs staging)
  • Rotate a key when you need a new secret while phasing out an old one
  • Revoke a key that is compromised or no longer needed
Store keys only in environment variables or a secret manager—never commit them to source control.
3

Send the key on each request

Use the HTTP Authorization header with the Bearer scheme:

Code examples: call the API with an API key

Set BLOCKDB_API_KEY in your environment (or substitute your key directly). These examples use the historic REST base URL https://api.blockdb.io/v1.

Official SDKs

The .NET, Python, and JavaScript SDKs accept your API key and attach Authorization: Bearer for you. See each SDK page for the exact constructor and configuration options.

Security practices

  • Rotation: Request a new key from support, deploy it, then ask for the old key to be revoked.
  • Least privilege: Use separate keys for production and non-production when possible (within the five-key limit).
  • Incidents: If a key leaks, email support@blockdb.io immediately to revoke it and issue a replacement.

See Also

Last modified on May 29, 2026