Skip to main content
In order to use the RPC API you will need to setup the correct RPC endpoints.

​
RPC Endpoint Setup

  • POST for all methods
  • JSON RPC 2.0
  • id: "dontcare"
  • endpoint URL varies by network:
    • mainnet https://rpc.mainnet.near.org
    • testnet https://rpc.testnet.near.org
    • betanet https://rpc.betanet.near.org (may be unstable)
    • localnet http://localhost:3030

​
Limits

  • Maximum number of requests per IP for mainnet: 30 req/min, 75 req per 10 mins
  • Maximum number of requests per IP for testnet: 30 req/min, 75 req per 10 mins

​
Querying Historical Data

Querying historical data (older than 5 epochs or ~2.5 days), you may get responses that the data is not available anymore. In that case, archival RPC nodes will come to your rescue:
  • mainnet https://archival-rpc.mainnet.near.org
  • testnet https://archival-rpc.testnet.near.org
You can see this interface defined in nearcore here.

​
Limits

  • Maximum number of requests per IP for mainnet: 4 req/min, 10 req per 10 mins
  • Maximum number of requests per IP for testnet: 20 req/min, 50 req per 10 mins
The endpoints https://*.near.org are officially deprecated and heavily rate-limited. Please use any of the available RPC providers in production. See this announcement for more info.

​
Postman Setup

An easy way to test the queries in this documentation page is to use an API request tool such as Postman. You only need to configure two things:
  1. Make sure you add a header with a key of Content-Type and value of application/json.
  2. Then select the Body tab and choose the raw radio button and ensure JSON is the selected format.
After that is set up, just copy/paste the JSON object example snippets below into the body of your request, on Postman, and click send.

​
JavaScript Setup

All of the queries listed in this documentation page can be called using near-api-js.

​
HTTPie Setup

If you prefer to use a command line interface, we have provided RPC examples you can use with HTTPie. Please note that params take either an object or array passed as a string. 
http post https://rpc.testnet.near.org jsonrpc=2.0 id=dontcare method=network_info params:='[]'

​
Using block_id param

The block_id param can take either the block number (e.g. 27912554) or the block hash (e.g. '3Xz2wM9rigMXzA2c5vgCP8wTgFBaePucgUmVYPkMqhRL') as an argument.
The block IDs of transactions shown in NearBlocks Explorer are not necessarily the block ID of the executed transaction. Transactions may execute a block or two after its recorded, and in some cases, can take place over several blocks. Due to this, it is important to check subsequent blocks to be sure all results related to the queried transaction are discovered.

​
Using finality param

The finality param has three options: optimistic, near-final and final:
  1. optimistic - the transaction is in a block that - though unlikely - might be skipped (~1s after submission)
  2. near-final - the transaction is in a block that is irreversible, unless at least one block producer is slashed (~2s after submission)
  3. final - the block is final and irreversible (~3s after submission)
The near-final finality has enough guarantees for any normal operations, and thus should be preferred for most applications. You can learn more about it in this official blog post.

Build docs developers (and LLMs) love

Get started for freeTalk to us