Mainnet
Mainnet Horizon REST API
https://stellar-mainnet.gateway.tatum.io/
Soroban JSON-RPC
https://stellar-mainnet-soroban.gateway.tatum.io/
Free Stellar RPC (XLM)
Explore Stellar, a blockchain designed for cross-border payments and digital assets. Build financial applications using its RPC gateway.
99.9%
4
24/7
FREE
Gateway
Connect to Stellar
Access reliable, enterprise-grade endpoints that power your dApp with ultra-low latency and 99.9% uptime.
Connect to Stellar Gateway
Make your first RPC call on Stellar's Blockchain Gateway.
Testnet
Testnet Horizon REST API
https://stellar-testnet.gateway.tatum.io
Soroban JSON-RPC
https://stellar-testnet-soroban.gateway.tatum.io/
* Rate limit enabled - perfect for testing and development. For production, we recommend to Upgrade.
Ready for production?
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
Get Free API Key
Increase your limit and access all network features in Tatum Development Platform.
Accessible to Everyone
No signup. No paywalls. Just RPC that works. Great ideas come from everywhere.
Our Mission
With love by Tatum
Method reference
Stellar methods
Every method the Stellar gateway accepts, grouped by interface. 47 in total, read live from the node rather than kept by hand.
Mainnet is the live Stellar network. Every transaction it
accepts is final, and every XLM 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.
Stellar answers over 2 interfaces: JSON-RPC and REST. Each is listed once below with every method it accepts. The endpoints differ per network, and all of them are in the gateway list above.
What sits between you and Stellar
A node is a machine running Stellar 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.
Your application
FREE RPC gateway picks a healthy node
Node Node Node
- 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.
JSON-RPC
https://stellar-mainnet-soroban.gateway.tatum.io/
The default. Every wallet, library and framework speaks it, and it is what you want unless you specifically need something else.
One POST carries a method name, its parameters and an id, and the response comes back on the same connection carrying that same id. Requests are independent, so there is no session to keep alive and nothing to reconnect, which is why it runs unchanged behind a load balancer or inside a serverless function. Send an array instead of a single object and the node works through the whole batch in one round trip.
Where it fits
- Anything your library already does for you. ethers, web3.js, viem and their equivalents all target this.
- Batching reads. One array of twenty calls costs one round trip instead of twenty.
- Stateless and serverless deployments, because nothing has to stay connected between calls.
- Historical queries, by passing a block number where you would otherwise pass latest.
Trade-offs
- It cannot push. Finding out that a block landed means polling for it, or moving to WebSocket.
- Wide log queries get refused. Page through in fixed block windows and merge the results yourself.
- Batch responses may come back in any order. Match them on id, never on position.
This endpoint does not publish a machine-readable method list, so there is nothing to enumerate here. Use server reflection against the endpoint above to see what it exposes.
Common JSON-RPC errors
What you are most likely to hit calling this interface, and what to do about it.
- -32700
- Parse error. The request body was not valid JSON. Check that the body is serialised JSON and that Content-Type is application/json.
- -32600
- Invalid request. The JSON parsed, but it is not a well-formed JSON-RPC call. Include jsonrpc, method and id fields. A batch must be a non-empty array.
- -32601
- Method not found. This node does not expose the method you called. Check the spelling and the namespace, and confirm the method is in the list above for this network. Tracing methods in particular are not enabled everywhere.
- -32602
- Invalid params. The method exists but the arguments are wrong. Check argument order and types. Most EVM methods want hex-encoded quantities, and a block parameter such as latest or a hex height.
- -32603
- Internal error. The node failed while handling an otherwise valid request. Retry with backoff. If it persists on one method, it is usually that method rather than the node.
- -32000
- Server error. A catch-all the node uses for execution failures, most often a reverted call or a request over a limit. Read the accompanying message. Execution reverted means your call failed on chain, not in transport. Narrow the block range if you are querying logs.
- HTTP 429
- Rate limited. You have exceeded the free tier request allowance. Back off and retry, batch reads into single calls, or move to a dedicated endpoint for production traffic.
- HTTP 413
- Payload too large. The request body exceeded what the node accepts. Split large batches into smaller ones.
REST
47 methods https://stellar-mainnet.gateway.tatum.io/
Every 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 /
- Returns the Horizon root: version, network passphrase and available endpoints.
- GET /accounts
- Lists accounts, ordered by balance.
- GET /accounts/{account-id}
- Returns an account: balances, signers, thresholds and flags.
- GET /accounts/{account-id}/data/{key}
- Returns one data entry stored on an account.
- GET /accounts/{account-id}/effects
- Lists the effects that changed an account.
- GET /accounts/{account-id}/offers
- Lists the open offers an account has placed.
- GET /accounts/{account-id}/operations
- Lists the operations involving an account.
- GET /accounts/{account-id}/payments
- Lists the payments sent or received by an account.
- GET /accounts/{account-id}/trades
- Lists the trades an account has taken part in.
- GET /accounts/{account-id}/transactions
- Lists the transactions involving an account.
- GET /assets
- Lists the assets issued on the network.
- GET /claimable_balances
- Lists claimable balances, which hold funds until a claimant takes them.
- GET /claimable_balances/{claimable_balance_id}
- Returns one claimable balance.
- GET /claimable_balances/{claimable_balance_id}/operations
- Lists the operations affecting a claimable balance.
- GET /claimable_balances/{claimable_balance_id}/transactions
- Lists the transactions affecting a claimable balance.
- GET /effects
- Lists effects, the fine-grained changes operations produce.
- GET /fee_stats
- Returns recent fee percentiles, for choosing a competitive fee.
- GET /ledgers
- Lists ledgers, the Stellar equivalent of blocks.
- GET /ledgers/{ledger-id}
- Returns one ledger.
- GET /ledgers/{ledger-id}/effects
- Lists the effects produced in a ledger.
- GET /ledgers/{ledger-id}/operations
- Lists the operations contained in a ledger.
- GET /ledgers/{ledger-id}/payments
- Lists the payments contained in a ledger.
- GET /ledgers/{ledger-id}/transactions
- Lists the transactions contained in a ledger.
- GET /liquidity_pools
- Lists the liquidity pools on the network.
- GET /liquidity_pools/{liquidity-pool-id}
- Returns one liquidity pool and its reserves.
- GET /liquidity_pools/{liquidity-pool-id}/effects
- Lists the effects involving a liquidity pool.
- GET /liquidity_pools/{liquidity-pool-id}/operations
- Lists the operations involving a liquidity pool.
- GET /liquidity_pools/{liquidity-pool-id}/trades
- Lists the trades executed against a liquidity pool.
- GET /liquidity_pools/{liquidity-pool-id}/transactions
- Lists the transactions involving a liquidity pool.
- GET /offers
- Lists the open offers on the network.
- GET /offers/{offer-id}
- Returns one open offer.
- GET /offers/{offer-id}/trades
- Lists the trades that filled an offer.
- GET /operations
- Lists operations, the individual actions inside transactions.
- GET /operations/{operation-id}
- Returns one operation.
- GET /operations/{operation-id}/effects
- Lists the effects an operation produced.
- GET /order_book
- Returns the order book for an asset pair.
- GET /paths/strict-receive
- Finds payment paths that deliver an exact amount to the recipient.
- GET /paths/strict-send
- Finds payment paths that spend an exact amount from the sender.
- GET /payments
- Lists payments across the network.
- GET /trade_aggregations
- Returns trade activity summarised into time buckets, for price charts.
- GET /trades
- Lists trades across the network.
- GET /transactions
- Lists transactions, newest first.
- GET /transactions/{transaction-id}
- Returns one transaction.
- GET /transactions/{transaction-id}/effects
- Lists the effects a transaction produced.
- GET /transactions/{transaction-id}/operations
- Lists the operations contained in a transaction.
- GET /transactions/{transaction-id}/payments
- Lists the payments contained in a transaction.
- POST /transactions
- Submits one or more signed transactions.
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.
Blockchain Data
Indexed Stellar Data Insights
Complete on-chain data access, no infrastructure to run yourself. Query wallets, tokens, NFTs, and transaction history with lightning-fast APIs.
Learn more
About Stellar
What it is, and guides for building on it.
The Stellar RPC documentation provides developers with the tools to interact programmatically with the Stellar blockchain. Stellar is designed for cross-border payments and digital asset issuance, using the Stellar Consensus Protocol (SCP) for fast, secure, and low-cost transactions. The documentation includes API endpoints for querying blockchain data, managing transactions, and issuing assets. Developers can build decentralized financial applications, including stablecoins and remittance platforms, using Stellar’s robust RPC gateway and scalable infrastructure.
What's new at Tatum on Stellar?
Oct 8, 2026 Added
Notifications: Robinhood
Robinhood Chain is now live on Tatum’s Blockchain Notifications, with support for all notification types. Receive onc...
Oct 7, 2026 Added
RPC Gateway: WebSockets for Arbitrum and BSC
Stop polling. Start streaming. Tatum WebSocket subscriptions push blockchain updates to your app over a persistent co...
Sep 25, 2026 Deprecated
Harmony Networks Removal
Tatum is decommissioning its hosted Harmony Mainnet S0, Harmony Testnet S0, and Harmony Devnet S0 RPC services follow...
FAQ
Frequently Asked Questions
Everything you need to know about Stellar RPC endpoints
Quick Answer: What is Stellar 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 Stellar RPC?
RPC (Remote Procedure Call) is the interface that lets developers interact with the network: read on-chain data, submit transactions, and deploy smart contracts programmatically over standard JSON-RPC methods, without running your own node.
How do I connect to Stellar using these RPC endpoints?
Simply copy the RPC endpoint URL from above and configure it in your Web3 library (ethers.js, web3.js), wallet (MetaMask, Trust Wallet), or development tool (Hardhat, Truffle). The endpoint works immediately with no registration required for the free tier.
What are the rate limits for the free RPC tier?
Free tier RPC endpoints are limited to 5 requests per minute. This is perfect for testing and development. For production applications, we recommend upgrading to Tatum Premium which offers 200 requests per second with no daily limits.
Is Stellar RPC free forever?
Yes! Our free tier RPC endpoints are free forever with 5 requests per minute. This tier is perfect for learning, testing, and small projects. There are no hidden fees or time limits on the free tier.
What happens if I exceed the free tier rate limit?
If you exceed 5 requests per minute on the free tier, you'll receive an HTTP 429 (Too Many Requests) error. This is a standard rate limiting response. To avoid this, you can upgrade to Tatum Premium which offers 200 requests per second with no daily limits, perfect for production applications.
Can I use these Stellar RPC endpoints with MetaMask?
Yes! You can configure MetaMask to use our RPC endpoints. Simply copy the endpoint URL from above, go to MetaMask Settings > Networks > Add Network (or edit existing), and paste the RPC URL. This works with all EVM-compatible networks, including this one.
Are these RPC endpoints secure?
Yes, all our RPC endpoints use HTTPS encryption and follow enterprise-grade security practices. They're powered by Tatum's infrastructure which maintains 99.9% uptime.
What's the difference between mainnet and testnet RPC endpoints?
Mainnet carries real transactions with real value, so every write is final. Testnet runs on a separate network funded with free test tokens, which makes it the safe place to try new code, retry failed calls, and simulate edge cases. Always validate on testnet before pointing production traffic at mainnet.
How do I troubleshoot RPC connection errors?
If you're experiencing connection errors, check: 1) The RPC endpoint URL is correct, 2) You're not exceeding rate limits (5 req/min for free tier), 3) Your network allows HTTPS connections, 4) The network is currently operational. For persistent issues, check our status page or contact support.
Can I use these endpoints in production?
Free tier endpoints can be used in production for low-traffic applications (under 5 req/min). For production apps with higher traffic, we strongly recommend Tatum Premium for guaranteed uptime, faster rate limits, and enterprise SLA.
Related Blockchains
Explore Other Blockchains
Discover RPC endpoints for other popular blockchain networks
