Skip to main content

FastNear API

FastNear API is the indexed REST family for builder-facing account views. It is the fastest way to answer questions like "what does this account own?" or "which accounts map to this public key?" without stitching together raw RPC calls.

Base URLs​

FastNear API Mainnet
https://api.fastnear.com
FastNear API Testnet
https://test.api.fastnear.com

Best fit​

  • Wallet balances and asset overviews.
  • NFT and fungible-token account views.
  • Public-key to account lookups.
  • Combined account snapshots for dashboards, explorers, and agents.

When not to use it​

  • Use RPC Reference when you need protocol-native JSON-RPC methods.
  • Use Transactions API when the primary job is transaction or receipt history.
  • Use NEAR Data API when the job is block-family polling and freshness checks.

Auth and network availability​

  • FastNear public REST endpoints often work without an API key.
  • The same FastNear key format still works across API endpoints when you want a consistent authenticated posture or higher limits, and the docs UI can forward it for interactive examples.
  • Add ?network=testnet to move compatible pages to the testnet backend and seeded testnet defaults.

Shareable live examples​

  • Use Copy example URL on any interactive API page to share the selected network and filled request state.
  • Shared example URLs run automatically on load whenever they include operation state.
  • Saved API keys and tokens are never included in those shared docs URLs.

Common starting points​

Need a workflow?​

Use FastNear API Examples for worked examples like account summaries, key-to-account resolution, and asset-specific follow-up.

Troubleshooting​

I only need one low-level value from chain state​

Use raw RPC instead. The indexed surface is optimized for product views, not for mirroring every RPC method.

My page is still on mainnet data​

Check whether the page supports ?network=testnet. Some flows are mainnet-only; the docs call that out when it applies.

I need transactions, not balances​

Move to Transactions API so you do not overload the account-view surface with history queries.