FastNear Transactions API

Retrieve NEAR blockchain transaction, account, block, and receipt data via JSON POST requests.

3|2|Updated May 27, 2024
One-click install
npx skills add https://github.com/fastnear/explorer-api --skill fastnear-transactions-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: FastNear Transactions API
Source: https://github.com/fastnear/explorer-api/tree/main/static
Command: npx skills add https://github.com/fastnear/explorer-api --skill fastnear-transactions-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It helps you retrieve raw NEAR blockchain transaction, account history, block, and receipt data through simple JSON-based POST requests without manually querying or decoding on-chain data.

Core Features & Use Cases

  • Fetch raw transactions by hash: Retrieve up to 20 transactions per request for debugging, auditing, and data enrichment.
  • Get account transaction history: Use cursor-based pagination and multiple signer/receiver/action filters to power wallets, explorers, and analytics dashboards.
  • Retrieve blocks and receipts: Look up a block by height or hash (optionally including transactions/receipts) and fetch a receipt with its associated transaction for deep investigation.

Quick Start

Send a POST request to the transactions endpoint with a JSON body containing a tx_hashes array to get the raw transaction payloads for those hashes.

Frequently Asked Questions about FastNear Transactions API

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve NEAR blockchain transactions using a transaction hash?

Fetch NEAR account transaction history by sending a POST request with account_id filters and a resume_token cursor, enabling filtered, paginated data retrieval for analytics dashboards.

What is the best way to look up a NEAR block by height or hash?

The best way to look up a NEAR block is via a POST request using a block_id identifier, optionally including associated transactions and receipts for deep blockchain investigation.

Can I fetch NEAR receipt data and its associated transaction together?

Query NEAR blockchain transaction, account, block, and receipt data via JSON POST API calls under the /v0 base path to retrieve raw on-chain data without manual decoding.

How do I paginate NEAR account transaction history for a wallet application?

Yes, you can filter NEAR account history by applying multiple signer, receiver, and action filters within your POST request to retrieve targeted transaction subsets for explorers.

Are there limits on how many NEAR transactions I can fetch per API request?

Limitations include a maximum of 20 transactions per hash lookup request and the strict requirement to shape POST request fields properly under the /v0 base path for successful retrieval.