BlockReq API

BlockReq provides a REST API on Web (https://blockreq.com/api/...) to manage your account, RPC endpoints, Request Count, usage stats, wallet value, API keys, notifications, and settings. Management calls never go to *-rpc.blockreq.com.

Getting Started

  1. Go to Dashboard → Settings to create an API Key
  2. Use the API Key as a Bearer token in the Authorization header
  3. Refer to the public OpenAPI documentation for all available endpoints

Interactive API Docs — View the deterministic public OpenAPI reference for BlockReq REST API endpoints

Dashboard Settings — Create and manage your API Keys

Authentication

Use a Management API Key (akv1_...) from Dashboard → Settings. It is the same owner as a signed-in dashboard session. RPC Endpoint Keys in {chain}-rpc.blockreq.com/v1/rpc/... URLs only authorize JSON-RPC traffic.

curl -H "Authorization: Bearer akv1_YOUR_MANAGEMENT_API_KEY" \ https://blockreq.com/api/dashboard/credits

Available Resources

ResourceDescription
EndpointsList, create, delete
NetworksSupported chains
UsageStats, analytics, overview
Request Count & walletBalances and Request Pack lots
BillingView payment history and manage payment methods
TeamsManage team members and invitations
API KeysCreate and revoke API keys
PlansView the effective plan and switch self-serve billing modes

For the full list of public endpoints and request/response schemas, visit the Interactive API Docs. Use Dashboard Settings to create or rotate API keys.

Deprecations

These fields keep working until 2027-01-01, when they are removed. Switch to the replacement before then.

DeprecatedReplacement
GET /api/dashboard/chains: chains[].gateway.publicRpcUrl and chains[].gateway.publicWssUrlchains[].publicRpcUrl and chains[].publicWssUrl (same values)
POST /api/dashboard/alert-rules: type: "ru_usage"type: "usage_percent" (rules created with the alias are already stored as usage_percent)