NEAR Data Server by FASTNEAR

For more information, visit GitHub

LIVE LATENCY TEST

Block type: Final Optimistic

Recommended: Rust Crate

The best option to consume Neardata is using the Rust crate: fastnear-neardata-fetcher.
Source code is available at github.com/fastnear/libs/tree/main/neardata-fetcher.

Rate Limits & Authentication

The public access rate limit is 180 requests per minute per IP.

To increase your rate limits, get a subscription at https://fastnear.com/.

To authenticate your requests with a FastNEAR Subscription API key, attach the following query string to the URL: ?apiKey={API_KEY}

Example: /v0/block/98765432?apiKey=YOUR_API_KEY

Invalid API keys may return 401 Unauthorized before the request reaches the neardata application.

Note: Authentication using the Authorization: Bearer header requires you to manually handle redirects, since the redirect URL will not pass the header through and the redirected request will not be authenticated.

API

GET /v0/block

Returns the finalized block by block height.

If the block doesn't exist it returns null.
If the block is not produced yet, but close to the current finalized block, the server will wait for the block to be produced and return it.
Depending on deployment topology, this route may redirect to the host that owns the canonical archive range.
The difference from NEAR Lake data is each block is served as a single JSON object, instead of the block and shards. Another benefit, is we include the tx_hash for every receipt in the receipt_execution_outcomes. The tx_hash is the hash of the transaction that produced the receipt.

Example: /v0/block/100000000

GET /v0/block/:block_height/headers

Logic is similar to the GET /v0/block/ route but returns the top-level block object from the full response, including the block header and chunk summaries.

Example: /v0/block/100000000/headers