Overview

Start building on Stellar for free

Create an endpoint in under a minute. The Free plan includes 50 million compute units a month, and no credit card is required.

Try free

Network Support

Network	HTTPS	WSS
Pubnet: Horizon (90 day history) & Stellar RPC (60 day history)	✅	❌
Testnet: Horizon (full history since the latest testnet reset) & Stellar RPC (7 day history)	✅	❌
Pubnet Archive: Horizon only (1 year history)	✅	❌
Pubnet RPC v2 (Beta): Stellar RPC only (full history from ledger 2)	✅	❌

History retention: Horizon on Pubnet lets you query the most recent 90 days of history, and the Pubnet Archive endpoint extends this to 1 year (the archive endpoint serves Horizon only; Stellar RPC is not available on it). Stellar RPC (formerly Soroban) serves the most recent 60 days of history on Pubnet and the most recent 7 days on Testnet. Pubnet RPC v2 (Beta) serves Stellar RPC with full Pubnet history, back to ledger 2 in September 2015. Horizon on Testnet serves full history back to the most recent Stellar testnet reset; the Stellar Development Foundation periodically resets testnet, and history restarts from each reset.

Stellar RPC v2 (Beta)

Stellar RPC v2 is the Stellar Development Foundation’s full-history version of Stellar RPC. It serves every Pubnet ledger since ledger 2, so getTransaction, getTransactions, getLedgers and getEvents can read any Pubnet ledger. To use it, create an endpoint and select the Pubnet RPC v2 (Beta) network. Your endpoint URL is https://pubnet.stellar.validationcloud.io/v1/<YOUR_API_KEY_HERE>. A Pubnet RPC v2 key only works on that URL, and a Pubnet key only works on mainnet.stellar.validationcloud.io. Stellar RPC v2 is compatible with existing Stellar RPC clients. No method, parameter or response field was removed. The differences are:

Full history. Requests for old ledgers succeed instead of returning an out-of-range error.
getHealth returns ledgerRetentionWindow: 0 because the node keeps full history. Use oldestLedger to find the oldest ledger served.
getLedgers returns at most 20 ledgers per page, with a default of 5. Stellar RPC on Pubnet and Testnet allows up to 200, with a default of 50. A limit above 20 returns an error.
New method: queryEvents adds newest-first ordering, positional topic filters and stateless cursors.
No Horizon. Pubnet RPC v2 serves Stellar RPC only. For Horizon, use a Pubnet or Pubnet Archive endpoint.

Stellar RPC v2 is in beta. The Stellar Development Foundation’s full list of changes is here.

Stellar SSE Streaming

We recently introduced an updated Compute Unit (CU) model for Server-Sent Events (SSE) streaming on Stellar Horizon API endpoints. SSE allows developers to receive real-time updates without the need for continuous polling. Pricing Model SSE-enabled Stellar endpoints use a two-part pricing structure:

Base cost per request: 20 CUs (same as standard Stellar endpoints)
Data streaming cost: 1 CU per KB of data streamed to the client

This differs from standard Stellar endpoints, which only charge the base request cost and do not include any data-based pricing. Compute Unit Calculation

Total CUs = (20 × number of requests) + (1 × response size in KB)

Total CUs = (cu_amount × requests) + ((response_size_bytes / 1024) × cu_per_kb)

Key Difference

Standard endpoints: Fixed cost per request (no data-based charges)
SSE endpoints: Base request cost plus variable cost based on streamed data volume

Getting Started

Send a request to check that your endpoint works. Replace <YOUR_API_KEY_HERE> with the key from your endpoint in the Validation Cloud app.

curl https://mainnet.stellar.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc": "2.0", "id": 8675309, "method": "getHealth"}'

curl https://testnet.stellar.validationcloud.io/v1/<YOUR_API_KEY_HERE> \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc": "2.0", "id": 8675309, "method": "getHealth"}'

Compute Units

SSE Streaming Endpoints

Certain Stellar Horizon endpoints support Server-Sent Events (SSE), allowing clients to receive real-time updates instead of polling.

Compute Units: When used in streaming mode, these endpoints are charged at 20 CUs per request plus 1 CU per KB of data streamed.

The following endpoints support SSE streaming:

Top-level endpoints

GET /ledgers
GET /transactions
GET /operations
GET /payments
GET /effects
GET /trades

Account-specific endpoints

GET /accounts/{account_id}/transactions
GET /accounts/{account_id}/operations
GET /accounts/{account_id}/payments
GET /accounts/{account_id}/effects
GET /accounts/{account_id}/trades
GET /accounts/{account_id}/offers

Ledger-specific endpoints

GET /ledgers/{ledger_sequence}/transactions
GET /ledgers/{ledger_sequence}/operations
GET /ledgers/{ledger_sequence}/payments
GET /ledgers/{ledger_sequence}/effects

Liquidity pool endpoints

GET /liquidity_pools/{liquidity_pool_id}/effects
GET /liquidity_pools/{liquidity_pool_id}/trades
GET /liquidity_pools/{liquidity_pool_id}/transactions
GET /liquidity_pools/{liquidity_pool_id}/operations

Transaction & operation endpoints

GET /operations/{operation_id}/effects
GET /transactions/{transaction_id}/operations
GET /transactions/{transaction_id}/effects

Offer endpoints

GET /offers/{offer_id}/trades

Claimable balance endpoints

GET /claimable_balances/{claimable_balance_id}/transactions
GET /claimable_balances/{claimable_balance_id}/operations

Stellar RPC (formerly known as Soroban)

Method	Compute units
getEvents	10
getFeeStats	10
getHealth	10
getLatestLedger	10
getLedgerEntries	10
getLedgers	10
getNetwork	10
getTransaction	10
getTransactions	10
getVersionInfo	10
queryEvents (Pubnet RPC v2 only)	10
sendTransaction	10
simulateTransaction	10

Horizon

Method	Compute units
GET /	10
GET /accounts	20
GET /accounts/:account_id	20
GET /accounts/:account_id/transactions	20
GET /accounts/:account_id/operations	20
GET /accounts/:account_id/payments	20
GET /accounts/:account_id/effects	20
GET /accounts/:account_id/offers	20
GET /accounts/:account_id/trades	20
GET /accounts/:account_id/data/:key	20
GET /assets	20
GET /claimable_balances	20
GET /claimable_balances/:claimable_balance_id	20
GET /claimable_balances/:claimable_balance_id/transactions	20
GET /claimable_balances/:claimable_balance_id/operations	20
GET /effects	20
GET /fee_stats	10
GET /ledgers/:sequence	20
GET /ledgers/:sequence/transactions	20
GET /ledgers/:sequence/payments	20
GET /ledgers/:sequence/operations	20
GET /ledgers/:sequence/effects	20
GET /ledgers	20
GET /liquidity_pools	20
GET /liquidity_pools/:liquidity_pool_id	20
GET /liquidity_pools/:liquidity_pool_id/effects	20
GET /liquidity_pools/:liquidity_pool_id/trades	20
GET /liquidity_pools/:liquidity_pool_id/transactions	20
GET /liquidity_pools/:liquidity_pool_id/operations	20
GET /offers	20
GET /offers/:offer_id	20
GET /offers/:offer_id/trades	20
GET /operations/:id	20
GET /operations/:id/effects	20
GET /operations	20
GET /order_book	10
GET /paths/strict-receive	10
GET /paths/strict-send	10
GET /payments	20
GET /transactions/:transaction_hash/payments	10
GET /trades	20
GET /trade_aggregations	40
GET /transactions/:transaction_hash	20
GET /transactions/:transaction_hash/operations	20
GET /transactions/:transaction_hash/effects	20
GET /transactions	20
POST /transactions	20

Node API

Account

Endpoints

Admin API

Resources

Chains

Network Support

Stellar RPC v2 (Beta)

Stellar SSE Streaming

Getting Started

Compute Units

SSE Streaming Endpoints

Stellar RPC (formerly known as Soroban)

Horizon

​Network Support

​Stellar RPC v2 (Beta)

​Stellar SSE Streaming

​Getting Started

​Compute Units

​SSE Streaming Endpoints

​Stellar RPC (formerly known as Soroban)

​Horizon

Network Support

Stellar RPC v2 (Beta)

Stellar SSE Streaming

Getting Started

Compute Units

SSE Streaming Endpoints

Stellar RPC (formerly known as Soroban)

Horizon