ERPC

NEAR RPC Quickstart | ERPC

NEAR RPC Quickstart

This guide takes you from zero to your first NEAR 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 2.0 request as an HTTP POST, with your API key in the api-key parameter:
bash
curl 'https://edge.erpc.global/near?api-key=<YOUR_API_KEY>' --header 'Content-Type: application/json' --data '{
  "jsonrpc":"2.0","id":1,
  "method":"block",
  "params":{"finality":"final"}
}'
The response returns the latest finalized block in the result field.
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 the node and its chain with status:
bash
curl 'https://edge.erpc.global/near?api-key=<YOUR_API_KEY>' --header 'Content-Type: application/json' --data '{
  "jsonrpc":"2.0","id":1,
  "method":"status",
  "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

Monad RPC Endpoint Documentation | ERPC

Next

NEAR RPC Endpoint Documentation | ERPC