JSON-RPC

Overview

All requests are counted in Compute Units (CU) and rate-limited per key.

• Endpoint: POST /v1/{chain}/{api_key} (key in the path) or POST /v1/{chain} (key in a header). For Robinhood Chain, {chain} is robinhood_mainnet: https://api.blockvectra.com/v1/robinhood_mainnet. The same API key works on every supported chain
• Protocol: HTTP POST, single call or batch
• Metering: A request's total CU cost counts against your key's burst capacity as soon as it arrives. Every accepted call that gets a response is charged at the method's published CU weight; the Errors reference lists the cases that are not billed. Billing is settled hourly (rounded down to whole units, remainder carries over, executed ~15 minutes after the period ends)
• Ethereum: its own method list and a state window determined by state_window_blocks — see Supported Chains → Ethereum.

For complete parameter schemas, method signatures, and interactive request testing across all methods, see the Full Reference. For path versioning, backward compatibility rules, and SDK recommendations, see API versioning and compatibility.

To get an API key and send a first request, see the Quickstart; it also covers key passing and batch requests.

Common calls

Worked examples for common calls.

Query logs (eth_getLogs)

Filter a contract's logs over a recent block range — here, the ERC-20 Transfer event (topic 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef). See the CU Metering Rules table below for eth_getLogs's current CU weight; a range wider than the chain's max_logs_block_range (from GET /v1/chains) is rejected with -32602.

export BLOCKVECTRA_API_KEY=rgw_your_api_key

curl -X POST "https://api.blockvectra.com/v1/robinhood_mainnet" \
  -H 'Content-Type: application/json' \
  -H "x-api-key: $BLOCKVECTRA_API_KEY" \
  -d '{
    "jsonrpc": "2.0",
    "method": "eth_getLogs",
    "params": [{
      "fromBlock": "0x45a2409",
      "toBlock": "0x45a2609",
      "address": "0x1111111111111111111111111111111111111111",
      "topics": ["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"]
    }],
    "id": 1
  }'

Trace a transaction (debug_traceTransaction)

Trace a transaction's internal calls with the callTracer. See the CU Metering Rules table below for debug_traceTransaction's current CU weight. Like the other state-reading methods, it's rejected once the target block falls outside that chain's recent-state window (-32011). The window size is the chain's state_window_blocks (from GET /v1/chains). On chains that provide traces, use the Data API for historical traces.

export BLOCKVECTRA_API_KEY=rgw_your_api_key

curl -X POST "https://api.blockvectra.com/v1/robinhood_mainnet" \
  -H 'Content-Type: application/json' \
  -H "x-api-key: $BLOCKVECTRA_API_KEY" \
  -d '{
    "jsonrpc": "2.0",
    "method": "debug_traceTransaction",
    "params": ["0xYOUR_TRANSACTION_HASH", {"tracer": "callTracer"}],
    "id": 1
  }'

CU metering rules

Method policy

Available methods vary by chain; each chain's list is shown below, and Supported Chains covers the rest. Only methods matching an allowed name or pattern are reachable; any other method returns -32601 method not available.

Limits:

• Batch: max 100 calls per request; also limited by the key's CU burst, see below.
• Request body: max 2 MiB (see “10. Limits at a glance” in the full OpenAPI reference)
• CU burst: each API key has a CU bucket (cu_per_sec refill, burst_cu capacity — defaults are 100 CU/s and burst 400 CU; after a paid top-up each key is at least 2,000 CU/s and burst 10,000 CU, and higher custom limits are kept; shown per key in the console Keys table). A single request — including a whole JSON-RPC batch — whose total CU exceeds the key's burst capacity is rejected with -32022 request_exceeds_burst (request cost <N> CU exceeds burst capacity <M> CU); split it into smaller batches.

Error codes

See the Errors reference for every error code, whether it is billed, and what to do.

Full OpenAPI reference

See the Full OpenAPI reference for the complete machine-readable specification with all method signatures, request and response schemas, and parameter details rendered interactively.