Free Algorand RPC (ALGO)
Explore Algorand blockchain, offering fast transactions via RPC gateway. Access detailed documentation for building scalable dApps and DeFi applications.
Connect to Algorand
Access reliable, enterprise-grade endpoints that power your dApp with ultra-low latency and 99.9% uptime.
Connect to Algorand Gateway
Make your first RPC call on Algorand's Blockchain Gateway.
Testnet
Testnet* Rate limit enabled - perfect for testing and development. For production, we recommend to Upgrade.
Get 200 requests/second, priority support and advanced blockchain features.
Global Load Balancer
Route to nearest node
Batch RPC Calls
Multiple requests at once
Archive Nodes
Historical blockchain data
Debug & Trace
Advanced debugging
Advanced Analytics
Usage & performance
Bring Your Own RPC
Custom RPC gateways
Increase your limit and access all network features in Tatum Development Platform.
Smart Contract Tools on Algorand
Deploy, create, and interact with smart contracts on Algorand.
No signup. No paywalls. Just RPC that works. Great ideas come from everywhere.
With love by Tatum
Algorand methods
Every method the Algorand gateway accepts, grouped by interface. 26 in total, read live from the node rather than kept by hand.
Mainnet is the live Algorand network. Every transaction it
accepts is final, and every ALGO balance it
reports is real money.
Testnet answers the same methods on a network funded with tokens that have no market value. Develop there, then change the URL to Mainnet when the code is stable. Nothing else about your integration has to change.
Everything below is served over REST. Its endpoint differs per network, and all of them are in the gateway list above.
What sits between you and Algorand
A node is a machine running Algorand with a copy of the chain. Your code cannot ask the chain directly, it asks a node. The gateway picks a healthy one for every call, so you point at one URL instead of one machine.
- One URL, nothing to run or keep patched yourself.
- Calls routed to a node that is up and in sync.
- A failing node is skipped rather than returned to you as an error.
REST
26 methodsEvery resource has its own URL, so a request is just an address you can open.
Paste it into a browser, curl it, or bookmark it. There is no body to construct and no method name to look up, and because a read is a plain GET, ordinary HTTP caching applies at the CDN and in your own client. Responses are JSON, and the path itself usually tells you what you are getting.
Where it fits
- Getting oriented on an unfamiliar chain without writing any code first.
- Caching, because a GET can be cached by anything sitting between you and the node.
- Debugging, since the request that failed is a URL you can paste to a colleague.
Trade-offs
- You get exactly what the endpoint returns. There is no way to ask for less, or for more.
- Building a full picture takes several round trips where one batched JSON-RPC call would do.
- Paths carry version prefixes and shift between node releases more readily than method names do.
Enabled and tested methods
Read live from the endpoint, so this is what it actually serves today rather than what the protocol allows in principle. Anything not on this list returns a method-not-found error.
- GET /genesis
- Returns the genesis configuration of the network.
- GET /health
- Reports whether Sidecar and the node behind it are reachable.
- GET /ready
- Reports whether the node has caught up and is ready to serve.
- GET /v2/accounts/{account-id}
- Returns an account, including balances, assets and applications.
- GET /v2/accounts/{account-id}/applications/{application-id}
- Returns the local state an account holds for an application.
- GET /v2/accounts/{account-id}/assets/{asset-id}
- Returns the balance and opt-in status of one asset for an account.
- GET /v2/accounts/{account-id}/transactions/pending
- Lists the pending transactions submitted by an account.
- GET /v2/applications/{application-id}
- Returns an application, including its programs and global state.
- GET /v2/applications/{application-id}/{box-id}
- Returns the contents of one application box.
- GET /v2/applications/{application-id}/boxes
- Lists the box storage keys an application holds.
- GET /v2/assets/{asset-id}
- Returns an asset and its configuration.
- GET /v2/blocks/{round}
- Returns the block for a round.
- GET /v2/blocks/{round}/hash
- Returns the hash of the block for a round.
- GET /v2/blocks/{round}/lightheader/proof
- Returns a proof of the light block header for a round.
- GET /v2/blocks/{round}/transactions/{transaction-id}/proof
- Returns a Merkle proof that a transaction is in a block.
- GET /v2/blocks/{round}/txids
- Lists the transaction IDs in a block.
- GET /v2/deltas/{round}
- Returns the state changes applied by a round.
- GET /v2/ledger/supply
- Returns the total and online stake of the ledger.
- GET /v2/status
- Returns node sync status and the current round.
- GET /v2/status/wait-for-block-after/{round}
- Blocks until a round after the one given is reached, then returns status.
- GET /v2/transactions/params
- Returns the suggested parameters needed to build a transaction.
- GET /v2/transactions/pending
- Lists the transactions waiting in the pool.
- GET /v2/transactions/pending/{transaction-id}
- Returns one pending transaction and its status.
- POST /v2/transactions
- Broadcasts a signed transaction.
- POST /v2/transactions/async
- Broadcasts a signed transaction without waiting for the initial check.
- POST /v2/transactions/simulate
- Runs a transaction without committing it, returning the outcome.
Common REST errors
What you are most likely to hit calling this interface, and what to do about it.
- 400
- Bad request. A path or query parameter is malformed. Check the parameter format, and that path values are URL-encoded.
- 404
- Not found. Either the path is wrong, or the resource genuinely does not exist at that height. Confirm the path against the list above. A valid path can still 404 for pruned history on a non-archive node.
- 429
- Rate limited. You have exceeded the free tier request allowance. Back off and retry. REST responses cache well, so caching on your side removes most repeat traffic.
- 500
- Internal server error. The node failed while handling the request. Retry with backoff.
- 503
- Service unavailable. The node is starting, resyncing, or temporarily out of rotation. Retry with backoff; this is normally short-lived.
Indexed Algorand Data Insights
Complete on-chain data access, no infrastructure to run yourself. Query wallets, tokens, NFTs, and transaction history with lightning-fast APIs.
About Algorand
What it is, and guides for building on it.
The Algorand RPC documentation provides a comprehensive guide for developers to interact with the Algorand network programmatically. It includes APIs for interacting with the core components such as `algod`, responsible for node operations, and the `indexer`, which allows efficient blockchain data searches. Developers can use these endpoints to query blockchain data, submit transactions, and retrieve network statistics. Algorand’s architecture, known for scalability and security, enables the development of efficient decentralized applications across DeFi, payments, and enterprise use cases.
What's new at Tatum on Algorand?
Notifications: Robinhood
Robinhood Chain is now live on Tatum’s Blockchain Notifications, with support for all notification types. Receive onc...
RPC Gateway: WebSockets for Arbitrum and BSC
Stop polling. Start streaming. Tatum WebSocket subscriptions push blockchain updates to your app over a persistent co...
Harmony Networks Removal
Tatum is decommissioning its hosted Harmony Mainnet S0, Harmony Testnet S0, and Harmony Devnet S0 RPC services follow...
Frequently Asked Questions
Everything you need to know about Algorand RPC endpoints
Quick Answer: What is Algorand RPC?
RPC (Remote Procedure Call) is the standard way to interact with the network programmatically - reading on-chain data, submitting transactions, and deploying smart contracts through JSON-RPC calls. The free tier ships 5 requests per minute with no registration required, which covers most learning and testing workflows. Production applications typically move to Tatum Premium for 200 requests per second and enterprise-grade reliability.
What is Algorand RPC?
How do I connect to Algorand using these RPC endpoints?
What are the rate limits for the free RPC tier?
Is Algorand RPC free forever?
What happens if I exceed the free tier rate limit?
Can I use these Algorand RPC endpoints with MetaMask?
Are these RPC endpoints secure?
What's the difference between mainnet and testnet RPC endpoints?
How do I troubleshoot RPC connection errors?
Can I use these endpoints in production?
Explore Other Blockchains
Discover RPC endpoints for other popular blockchain networks