signatureSubscribe

signatureSubscribe opens a Solana PubSub subscription that watches a single base-58 transaction signature and pushes exactly one notification the moment that transaction reaches your chosen commitment (processed, confirmed, or finalized). The push tells you whether the transaction — which paid its fee in SOL lamports — succeeded or carries an error, and then the subscription auto-cancels. It is the WebSocket way to await a confirmation instead of polling getSignatureStatuses. The matching JSON-RPC endpoint is https://solana.therpc.io/YOUR_API_KEY, and you can cancel an as-yet-unfired subscription with signatureUnsubscribe.

Use cases

• Get a single push the moment a transaction you sent reaches confirmed or finalized, instead of looping over getSignatureStatuses.
• Build a reliable send-and-await-confirmation flow over WebSocket — submit with sendTransaction, then block on this subscription for the result.
• Receive an early "received" signal as soon as the cluster sees the transaction by setting enableReceivedNotification: true.

Parameters

Response

Example request

1# Open a WebSocket connection (e.g. with wscat) and send the subscribe request:
2wscat -c wss://solana.therpc.io/YOUR_API_KEY
3# then send:
4> {"jsonrpc":"2.0","id":1,"method":"signatureSubscribe","params":["5wHu1qwD4kLwq...",{}]}

Errors & troubleshooting

Common pitfalls

• The subscription fires once and then auto-cancels, so you do not need to clean up after the notification arrives — but call signatureUnsubscribe if you want to drop a subscription that has not fired yet.
• Subscribe before you send, or immediately after, so the transaction does not confirm before your subscription is registered and you miss the only notification.

Supported networks

• Mainnet
• Devnet

See also

• getSignatureStatuses
• sendTransaction
• logsSubscribe