Skip to main content

NEAR RPC

With Quicknode, you get access to our global NEAR network which always routes your API requests to the nearest available location, ensuring low latency and the fastest speeds.

NEAR Overview

NEAR is a Layer 1, proof-of-stake blockchain designed for scalability and developer experience. It utilizes Nightshade, a sharding technology that divides the network into multiple parallel shards to process transactions simultaneously, achieving ~600ms block times with 1.2s finality. NEAR features WebAssembly (WASM) runtime support for smart contracts written in Rust and JavaScript, with human-readable account names and developer-friendly gas fee sharing.

Interacting With NEAR APIs

NEAR exposes JSON-RPC methods that allow developers to interact with the network programmatically. You can query blockchain state, send transactions, call smart contract methods, and access account information. Through this API, you can query account details and access keys, call view methods on smart contracts, submit transactions and track their status, and retrieve block and chunk information.

You can connect by running your own node or by using a hosted provider such as Quicknode, which offers reliable, low-latency access without the need to manage infrastructure.

The Quicknode NEAR documentation is continuously updated, but we recommend cross-referencing with the official NEAR documentation for the latest API details.

Make NEAR API Calls

The quickest way to start building on NEAR is to create a Quicknode endpoint and send your first request. Quicknode provides managed NEAR endpoints, offering:

  • High reliability — globally distributed infrastructure designed to minimize downtime
  • Enhanced performance — optimized latency and request handling for production-grade apps

Visit the QuickStart page to create your endpoint and send your first request.

Supported Networks

Quicknode provides access to the following NEAR networks:

Mainnet
Type:Production
HTTP:
WSS:
Archive:Yes
Pruning:None
Testnet
Type:Testnet
HTTP:
WSS:
Archive:Yes
Pruning:None
Share this doc