RPC / API Reference
Choosing the FastNear API or reference.
Use RPC for canonical JSON-RPC state reads, contract calls, and transaction submission. Use indexed APIs for balances, holdings, activity history, and recent block-family data.
FastNear API keys work across the RPC and APIs.
Indexed account, asset, staking, and public-key endpoints for account-centric application reads.
Canonical JSON-RPC methods for blocks, contract calls, validators, and transaction submission.
Account activity, receipts, transaction lookups, and block-scoped history from indexed execution data.
Recent optimistic and finalized blocks, headers, and redirect helpers for polling and lightweight monitoring.
These are the main FastNear entry points.
Start with the API or reference section that matches the data you need, then move into the detailed reference for the specific endpoint.
Use indexed REST endpoints for balances, NFTs, staking positions, and public-key lookups without raw JSON-RPC request and response envelopes.
Use protocol-native methods for direct state reads, transaction submission, contract calls, and chain inspection.
Use indexed endpoints for account activity, receipts, transaction lookups, and block-scoped execution history.
Use NEAR Data for recent optimistic and finalized blocks, block headers, and latest-block helper routes when you need near-realtime reads or lightweight monitoring.
What teams ask before going live.
Keep these close when you are moving from exploration to production.
Sign in, create keys, and move to higher-limit usage patterns when you need them.
Check incidents or degraded service before you start debugging application behavior.
Stand up RPC or archival infrastructure faster without replaying the chain from scratch.
Building with AI agents or background workers?
Use the agent docs for credential posture, routing logic, and prompt-friendly markdown exports.