Horizon SSE — Stellar Streams

Receive newly ingested Stellar ledgers or transactions as Horizon HAL JSON.

GEThttps://triport.io/rpc/stellar/horizon/ledgers?cursor=now

Network: Stellar mainnet
Scope: stellar:rpc
Auth: x-token: $TRIPORT_API_KEY (or Authorization: Bearer, or ?api-key= query)
Rate limit: stellar_read_rpc_heavy — 15 / 20 / 100 / 250 RPS sustained · short burst 30 / 40 / 200 / 500 (free / basic / pro / business) (plan policy); Burst capacity

Endpoint and plans: Stellar RPC endpoint.

Request

cURLJavaScriptPython

curl -N \
  -H "Accept: text/event-stream" \
  -H "x-token: $TRIPORT_API_KEY" \
  "https://triport.io/rpc/stellar/horizon/ledgers?cursor=now"

const res = await fetch("https://triport.io/rpc/stellar/horizon/ledgers?cursor=now", {
  method: "GET",
  headers: {
    "Accept": "text/event-stream",
    "x-token": process.env.TRIPORT_API_KEY,
  },
});
const data = await res.json();
console.log(data);

import os


import requests


resp = requests.get(
    "https://triport.io/rpc/stellar/horizon/ledgers?cursor=now",
    headers={
        "Accept": "text/event-stream",
        "x-token": os.environ["TRIPORT_API_KEY"],
    },
)
data = resp.json()
print(data)

Response

JSON

Example

data: {"_links":{"self":{"href":"$ledger_url"}},"id":"$ledger_id","paging_token":"$paging_token","sequence":64317187,"closed_at":"2026-09-07T14:01:44Z"}

The mounted SSE surface exposes two channels: newly closed ledgers and newly ingested transactions. Each data: frame contains the original Horizon HAL resource described by the AsyncAPI contract.

Use SSE for live processing without polling a collection. It is not historical replay: both channels require cursor=now and begin after the connection starts.

The mounted Horizon path currently has one measured working operator and is best-effort without an SLA. SSE does not extend the operator's 6,307,191-ledger measured REST retention window.

Parameters

channelstringrequired

Path segment: ledgers or transactions.

cursorstringrequired

Must be the constant now on this published stream surface.

Response

_linksobject

HAL links, including the resource's self link.

idstring

Ledger resource identifier.

paging_tokenstring

Opaque Horizon paging token.

hashstring

Ledger hash when present.

sequenceinteger

Ledger sequence.

closed_atstring

Ledger close timestamp.

Errors

See Stellar errors and the shared error reference.

Status	Meaning	When it happens
`400`	Bad request	`cursor` is missing or is not `now`, or the channel is invalid.
`401`	Unauthorized	The API key is missing or invalid.
`403`	Forbidden	The key lacks the required scope or tier.
`429`	Rate limited	The `stellar_read_rpc_heavy` budget is exceeded.
connection closed	Stream interrupted	The client must reconnect; no delivery SLA is provided.

Examples

Subscribe to newly ingested transactions:

cURL

curl -N \
  -H "Accept: text/event-stream" \
  -H "x-token: $TRIPORT_API_KEY" \
  "https://triport.io/rpc/stellar/horizon/transactions?cursor=now"

Notes

Store any application checkpoint before reconnecting; the published route does not promise replay from an older paging token.
A data: field contains one HAL resource, not a JSON-RPC envelope.
Only the ledger and transaction channels in the AsyncAPI contract are mounted.
This is read-only delivery; no write or transaction-submit channel exists.