Transactions API
Transactions API is the history surface. Use it when you want indexed transaction or receipt views without repeatedly polling raw RPC methods and joining the results yourself.
Base URLs
Transactions API Mainnet
https://tx.main.fastnear.comTransactions API Testnet
https://tx.test.fastnear.comBest fit
- Account activity feeds.
- Debugging and support tooling.
- Transaction and receipt lookups by hash.
- Block and block-range history queries.
When not to use it
- Use FastNear API when you need balances, NFTs, staking, or public-key lookups.
- Use RPC Reference when you need canonical node behavior or transaction submission.
Auth and availability
- Public history reads often work without a key.
- If your integration standardizes on one FastNear API key across FastNear surfaces, reuse the same header or query-param shape here too.
- Testnet uses
https://tx.test.fastnear.com, and receipt lookup is available there as well. - The service is built for indexed history access rather than transaction submission.
Common starting points
- Transactions by hash when you already know the transaction ID.
- Account history for activity feeds and account debugging.
- Receipt lookup for execution-flow investigation.
- Block range when you want a bounded history scan.
Need a workflow?
Use Transactions API Examples for worked examples like transaction lookups, receipt investigation, account activity, and block-window history.
Troubleshooting
I expected to submit a transaction here
This family is for indexed history queries, not for sending signed transactions. Use raw RPC for submission.
I need pagination guidance
/v0/account uses an opaque resume_token, while /v0/blocks is range and limit based. Reuse opaque tokens exactly as returned.
Need one canonical transaction status result?
Use raw RPC instead of the indexed history family.