Stellar RPC — Soroban & Horizon API

Last updated: September 16, 2026

Get API key Read the documentation

Network details

What works today

simulateTransaction is a read, not a send

It returns the simulated result, the footprint and the resource fee without touching the network — which is exactly what you want before assembling a real transaction, and exactly not what you want if you expected it to submit. Submission is not part of this product: there is no sendTransaction here and no POST /transactions on our Horizon. Sign and broadcast through your own endpoint.

History: a window, and an error at its edge

Soroban history covers about 120,960 ledgers; Horizon's measured retention is far longer, at 6,307,191 ledgers. The part worth designing around is the edge: a request past the Soroban window returns beyond_retention — an error, not an empty list. An empty list would let a client conclude "nothing happened"; an error tells it to reach for its own store instead. Handle it explicitly, and see getEvents.

Two shapes trip up first integrations: getEvents takes a named parameters object rather than a positional array, and getLedgers and getTransactions accept a limit of up to 200 per page.

Horizon and SSE, and what we do not claim

Both are published as limited: Horizon is served through one measured operator, best-effort, no dedicated SLA. POST /transactions is not part of the product. The SSE stream starts at cursor=now and delivers only new records, so there is no arbitrary replay — after a disconnect, close the gap with REST reads and resubscribe. HAL _links and _embedded fields pass through unchanged, and paging uses the usual cursor with a limit of up to 200. See the SSE reference and the Horizon REST reference.

Limits and plans

The heavy budget equals the ordinary read budget on Stellar, so event and ledger history are not rationed separately — the binding constraint is the retention window, not the rate. Plans: Basic $20, Pro $249, Business $499, Enterprise from $999 per month; Free is a 7-day trial with a single key in the EU region. See Stellar rate limits and tiers.

Quickstart

# Soroban: latest ledger
curl https://triport.io/rpc/stellar \
  -H 'x-token: $TRIPORT_API_KEY' -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"getLatestLedger"}'

# Soroban: events take a NAMED params object
curl https://triport.io/rpc/stellar \
  -H 'x-token: $TRIPORT_API_KEY' -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"getEvents","params":{"startLedger":1234567,"pagination":{"limit":200}}}'

# Horizon REST
curl 'https://triport.io/rpc/stellar/horizon/ledgers?limit=200' -H 'x-token: $TRIPORT_API_KEY'

# Horizon SSE (new records only)
curl -N 'https://triport.io/rpc/stellar/horizon/transactions?cursor=now' \
  -H 'Accept: text/event-stream' -H 'x-token: $TRIPORT_API_KEY'

Soroban RPC methods

• getEvents
• getFeeStats
• getHealth
• getLatestLedger
• getLedgerEntries
• getLedgers
• getNetwork
• getTransactions
• getVersionInfo
• simulateTransaction

Horizon routes are documented separately, with one page per endpoint — see the Horizon REST reference.