Ethereum RPC Endpoint Documentation | ERPC
Ethereum RPC Endpoint Documentation
Use ERPC as your Ethereum RPC endpoint for HTTP JSON-RPC requests and WebSocket subscriptions. Ethereum RPC is part of ERPC's RPC APIs within our Global Edge Blockchain Infrastructure, and the API key can be managed from the ERPC Web Dashboard.
You can use the same RPC key as Solana.
Please add your API key to the 'api-key' parameter.
Endpoints
Send JSON-RPC 2.0 requests as HTTP POST to:
text
https://edge.erpc.global/eth?api-key=<YOUR_API_KEY>https://edge.erpc.global/eth?api-key=<YOUR_API_KEY>For subscriptions, connect over WebSocket to:
text
wss://edge.erpc.global/eth?api-key=<YOUR_API_KEY>wss://edge.erpc.global/eth?api-key=<YOUR_API_KEY>Examples
Here is an HTTP request example.
bash
curl https://edge.erpc.global/eth?api-key=<YOUR_API_KEY> --header 'Content-Type: application/json' --data '{
"jsonrpc":"2.0","id":1,
"method":"eth_blockNumber"
}'curl https://edge.erpc.global/eth?api-key=<YOUR_API_KEY> --header 'Content-Type: application/json' --data '{
"jsonrpc":"2.0","id":1,
"method":"eth_blockNumber"
}'Here is a WebSocket subscription example.
bash
wscat -c "wss://edge.erpc.global/eth?api-key=<YOUR_API_KEY>"
# After connected, send:
{"jsonrpc":"2.0","id":1,"method":"eth_subscribe","params":["newHeads"]}wscat -c "wss://edge.erpc.global/eth?api-key=<YOUR_API_KEY>"
# After connected, send:
{"jsonrpc":"2.0","id":1,"method":"eth_subscribe","params":["newHeads"]}You can obtain and check your API key on the ERPC Web Dashboard: ERPC Web Dashboard
Batch Requests
JSON-RPC batches of up to 256 calls per HTTP request are supported, and JSON-RPC notifications are also accepted. Each call in a batch is metered as its own call.
Usage Metering
Usage is metered in tokens at a flat rate per JSON-RPC call — the same rate for every Ethereum RPC method. Each entry in an HTTP batch and each JSON-RPC call sent over a WebSocket connection is metered separately. You can check the current per-call token rate in the Ethereum RPC API Reference.
Supported Methods
The endpoint covers the standard Ethereum JSON-RPC method families —
eth_*, net_*, txpool_*, and web3_* — including account and block reads (eth_getBalance, eth_getBlockByNumber, eth_getLogs), transaction flow (eth_sendRawTransaction, eth_getTransactionReceipt), fee data (eth_feeHistory, eth_maxPriorityFeePerGas), call simulation (eth_call, eth_callMany, eth_simulateV1), state proofs (eth_getProof), filters (eth_newFilter, eth_getFilterChanges), txpool inspection (txpool_status, txpool_content), and WebSocket subscriptions (eth_subscribe, eth_unsubscribe).For the complete method list with request and response shapes, see the Ethereum RPC API Reference.
Response Status Codes
| HTTP status | Meaning |
|---|---|
| 200 | Upstream JSON-RPC response. |
| 400 | Invalid JSON-RPC request. |
| 401 | Missing or unauthorized API key. |
| 429 | Rate limited by the downstream RPC policy. |
| 502 | Proxy unavailable. |
| 503 | Downstream RPC service unavailable. |
WebSocket connections use
101 (protocol upgrade accepted) and 426 (a WebSocket Upgrade handshake is required) in addition to the codes above.Ethereum RPC Methods and Documentation
For the full list of standard methods, parameters, and subscription specifications, please refer to the official documentation. It covers both HTTP and WebSocket usage.