Documentation

/openapi.json post /EXPERIMENTALprotocolconfig A configuration that defines the protocol-level parameters such as gas/storage costs, limits, feature flags, other settings

/openapi.json post /EXPERIMENTALreceipt Fetches a receipt by its ID (as is, without a status or execution outcome)

/openapi.json post /EXPERIMENTALreceipttotx Resolves a receipt ID back to the originating transaction hash and sender account

/openapi.json post /EXPERIMENTALsplitstorageinfo Contains the split storage information. More info on split storage here

/openapi.json post /EXPERIMENTALtxstatus [Deprecated] Queries status of a transaction by hash, returning the final transaction result and details of all receipts. Consider using txstatus instead.

/openapi.json post /EXPERIMENTALvalidatorsordered Returns the current epoch validators ordered in the block producer order with repetition. This endpoint is solely used for bridge currently and is not

/openapi.json post /EXPERIMENTALviewaccesskey Returns information about a single access key for given account.

/openapi.json post /EXPERIMENTALviewaccesskeylist Returns all access keys for a given account.

/openapi.json post /EXPERIMENTALviewaccount Returns information about an account for given accountid.

/openapi.json post /EXPERIMENTALviewcode Returns the contract code (Wasm binary) deployed to the account.

/openapi.json post /EXPERIMENTALviewstate Returns the state (key-value pairs) of a contract based on the key prefix.

/openapi.json post /gasprice Returns gas price for a specific blockheight or blockhash. Using [null] will return the most recent block's gas price.

/openapi.json post /genesisconfig Get initial state and parameters for the genesis block

/openapi.json post /health Returns the current health status of the RPC node the client connects to.

/openapi.json post /lightclientproof Returns the proofs for a transaction execution.

/openapi.json post /maintenancewindows Returns the future windows for maintenance in current epoch for the specified account. In the maintenance windows, the node will not be block producer or chunk p

/openapi.json post /networkinfo Queries the current state of node network connections. This includes information about active peers, transmitted data, known producers, etc.

/openapi.json post /nextlightclientblock Returns the next light client block.

/openapi.json post /query This module allows you to make generic requests to the network. The RpcQueryRequest struct takes in a BlockReference and a QueryRequest. The BlockReference enum allows you to

/openapi.json post /sendtx Sends transaction. Returns the guaranteed execution status and the results the blockchain can provide at the moment.

/openapi.json post /status Requests the status of the connected RPC node. This includes information about sync status, nearcore node version, protocol version, the current set of validators, etc.

/openapi.json post /tx Queries status of a transaction by hash and returns the final transaction result.

/openapi.json post /txstatus Queries status of a transaction by hash, returning the final transaction result and details of all receipts.

/openapi.json post /validators Queries active validators on the network. Returns details and the state of validation on the blockchain.

Remember to make your callbacks private In NEAR, your contract can call a function from another contract, and then schedule a callback to handle its result. The callback function needs to be "public"

Enable users to login with their social accounts (Google, GitHub, etc.) Privy is a third-party service that allows users to login using their email or social accounts (Google, Facebook, Twitter, etc).

Reduce contract size and create reproducible builds that users can verify against the deployed code. In this page, we will explore strategies for reducing the size of smart contracts on NEAR. This is

Learn how to retrieve the genesis and current protocol configurations using the NEAR RPC API. The RPC API enables you to retrieve the current genesis and protocol configuration. Quick Reference | Meth

Overview of tools and methods for interacting with the NEAR Protocol. NEAR Protocol provides multiple ways to interact with the network — from low-level JSON-RPC calls to visual explorers and wallets.

Avoid predictable randomness vulnerabilities When writing smart contracts in NEAR you have access to a random seed that enables you to create random numbers/strings within your contract. This random s