Geyser · Solana Streaming

Geyser Documentation

TheRPC Geyser exposes the standard Yellowstone gRPC interface — a bidirectional stream of Solana state changes (slots, accounts, transactions, full blocks) at the commitment level you choose. Your TheRPC API key is the x-token gRPC metadata header. Drop-in Yellowstone gRPC compatible.

Quickstart

Connect in one file — TypeScript, Rust, Python.

Code examples

TS / Rust / Python drop-in samples.

Geyser product page

Pricing, use-cases, comparisons.

Endpoint

geyser.therpc.io:443

TLS on port 443. Pass your API key as the x-token gRPC metadata header (handled automatically by the Yellowstone client).

Subscription types

All four subscription types travel over a single gRPC session. Mix them freely in one SubscribeRequest.

SubscribeRequestFilterSlots

Slot status updates — processed, confirmed, finalized. Low-bandwidth heartbeat of chain progress.

SubscribeRequestFilterAccounts

Account changes filtered by owner pubkey, specific accounts, or data-size/memcmp predicates.

SubscribeRequestFilterTransactions

Transactions filtered by included/excluded accounts, program ID, vote flag, failed flag, or signature.

SubscribeRequestFilterBlocks

Full block data including all transactions and account updates. High-bandwidth — filter narrowly.

Authentication

Pass your TheRPC API key as the x-token gRPC metadata header. The Yellowstone gRPC client accepts it as the second constructor argument.

TypeScript

1// TypeScript
2const client = new Client(
3  "https://geyser.therpc.io:443",
4  "<YOUR_API_KEY>", // x-token header
5  undefined
6);

Reconnect & durability

The Yellowstone client reconnects automatically on disconnect. Missed events are not replayed — the stream is live-only. To handle gaps:

·Track the last slot you received and skip updates older than that on reconnect.
·Backfill gaps using getSignaturesForAddress on your TheRPC Solana JSON-RPC endpoint (same API key).
·Use CommitmentLevel.FINALIZED if you need a hard guarantee that slots don't roll back.