Skip to main content
Start a subscription to Preconfirmations — transactions delivered at the scheduled-transaction stage, before they are collected into entries and converted into shreds. This is the lowest-latency transaction signal Helius offers.

Endpoints

preconfSubscribe is served from the Helius Gatekeeper endpoint:
  • wss://beta.helius-rpc.com/?api-key=<API_KEY>
The beta hostname refers to the Gatekeeper rollout, not the maturity of Preconfirmations — it will become the standard endpoint as traffic migrates to Gatekeeper.
The stream is not continuous. Coverage scales with the share of network stake forwarding to Helius, so expect slots with no messages — handle these gaps gracefully. See Coverage.

Authorizations

string
required
Your Helius API key, passed as the api-key query parameter. Requires a Professional plan or higher.

Body

array
Optional. Omit params to receive every scheduled transaction. To narrow the stream, pass a filter object as the first element — filtering happens server-side, so you only pay for and receive the transactions you care about.
An invalid account value or unrecognized region code returns JSON-RPC error -32602 (invalid params). Account filters match more than the transaction’s static account keys — Helius resolves v0 address lookup tables server-side, so accountInclude, accountExclude, and accountRequired also match accounts a transaction loads through an ALT.

Region codes

Response

integer
Subscription id (needed to unsubscribe)

Notifications

After the JSON acknowledgement, notifications are delivered as binary WebSocket frames (not JSON). Each frame is a packed byte layout carrying a single scheduled transaction: Read the fields in order, then bincode-deserialize the remaining bytes into a VersionedTransaction to read instructions, accounts, and the signature.
Always read and check the version byte first. It is currently 1. If Helius needs to update the payload format, the version will increment — branch on it so your decoder keeps working across schema changes.
A preconfirmation is an early signal, not a guarantee. The transaction has not yet landed onchain and could still fail or be dropped. Confirm landing through standard commitment checks before treating it as final.

Pricing

Preconfirmations require a Professional plan or higher and cost 10 credits per message — one message per streamed transaction. See Credits for details.

Preconfirmations Overview

What Preconfirmations are and where they sit in the validator pipeline.

preconfUnsubscribe

Stop a subscription by its id.