ERPC

Bitcoin RPC Quickstart | ERPC

Bitcoin RPC Quickstart

This guide takes you from zero to your first Bitcoin JSON-RPC response with ERPC.

1. Get Your API Key

You can obtain and check your API key on the ERPC Web Dashboard: ERPC Web Dashboard
Already using ERPC for Solana, Ethereum, or Avalanche? You can use the same RPC key.

2. Make Your First Request

Send a JSON-RPC request as an HTTP POST, with your API key in the api-key parameter:
bash
curl 'https://edge.erpc.global/bitcoin?api-key=<YOUR_API_KEY>' --header 'Content-Type: application/json' --data '{
  "jsonrpc":"1.0","id":1,
  "method":"getblockcount",
  "params":[]
}'
The response returns the current block count in the result field.
Bitcoin accepts jsonrpc set to 1.0 or 2.0, or omitted, and every call needs an id.
On the Free plan, your account can send one request per 10 seconds, and a request to another chain can also count toward this limit. Wait 10 seconds before sending the next request.
You can check which chain the endpoint serves with getblockchaininfo:
bash
curl 'https://edge.erpc.global/bitcoin?api-key=<YOUR_API_KEY>' --header 'Content-Type: application/json' --data '{
  "jsonrpc":"1.0","id":1,
  "method":"getblockchaininfo",
  "params":[]
}'
You can also send your API key as Authorization: Bearer <YOUR_API_KEY>. When both are present, the query parameter is used.

3. Batch Requests

You can send 1 to 100 JSON-RPC calls in a single HTTP request. Every call needs its own id, and id values must not repeat within a batch. Each call in a batch is metered as its own call. On the Free plan, send one call per request: a request with two or more calls is answered with HTTP 429.

Next Steps

Previous

Base RPC Endpoint Documentation | ERPC

Next

Bitcoin RPC Endpoint Documentation | ERPC