As of May 1, 2026, this WebSocket method is billed based on metered data usage: 0.1 MB = 15 API credits. Learn more about WebSocket billing.

Parameters

filter

object

(Optional) A filter object to specify which transactions to receive notifications for:

vote

boolean

If true, include voting transactions; if false, exclude them

failed

boolean

If true, include failed transactions; if false, exclude them

signature

string

Filter notifications to a specific transaction signature

accounts

object

Account-based filtering with the following fields:

include

array

A list of account addresses (base-58 encoded strings) — notify when any of these appear in a transaction

exclude

array

A list of account addresses (base-58 encoded strings) — suppress notifications when any of these appear in a transaction

required

array

A list of account addresses (base-58 encoded strings) that must all be present in a transaction to trigger a notification

config

object

(Optional) A configuration object with the following fields:

commitment

string

The level of commitment required for the query. The options include:

processed

string

The node will query its most recent block. Note that the block may not be complete

confirmed

string

The node will query the most recent block that has been voted on by the supermajority of the cluster

finalized

string

The node will query the most recent block confirmed by the supermajority of the cluster as having reached maximum lockout

encoding

string

The encoding format for transaction data. It can be one of base58 (slow), base64, base64+zstd, or jsonParsed

transactionDetails

string

The level of transaction detail to return, either 'full', 'accounts', 'signatures', or 'none'

showRewards

boolean

Whether to include block rewards in the response

maxSupportedTransactionVersion

integer

The maximum transaction version to return, as a JSON integer. Set it to 1 to receive legacy, version 0, and version 1 transactions

Returns

result

integer

The subscription id (needed to unsubscribe)

transactionNotification

object

The notification object with the following fields:

context

object

API version and slot information

value

object

Transaction data with the following fields:

signature

string

The transaction signature

slot

integer

The slot in which the transaction was processed

transaction

object

The transaction data and metadata, including compute units consumed, fees, log messages, pre/post account balances, token balances, and inner instructions. On version 1 transactions the message carries a transactionConfig object with the compute and fee settings

version

string|integer

The transaction version, one of "legacy", 0, or 1

error

object|null

Error information if the transaction failed, otherwise null

Request

1
wscat -c  \
2
# wait for connection
3
{"id":1,"jsonrpc":"2.0","method":"transactionSubscribe","params":[{"vote":false,"failed":false,"accounts":{"include":["5qRKrGPYaQmazdtMnia1iC3gFbpgW4CT7KPrHq9nJGm5"]}},{"commitment":"confirmed","encoding":"base64","transactionDetails":"full","showRewards":false,"maxSupportedTransactionVersion":1}]}

1
wscat -c  \
2
# wait for connection
3
{"id":1,"jsonrpc":"2.0","method":"transactionSubscribe","params":[{"vote":false,"failed":false,"accounts":{"include":["5qRKrGPYaQmazdtMnia1iC3gFbpgW4CT7KPrHq9nJGm5"]}},{"commitment":"confirmed","encoding":"base64","transactionDetails":"full","showRewards":false,"maxSupportedTransactionVersion":1}]}

Response

1
{
2
  "jsonrpc": "2.0",
3
  "result": 0,
4
  "id": 1
5
}

1
{
2
  "jsonrpc": "2.0",
3
  "result": 0,
4
  "id": 1
5
}

Don't have an account yet?

Create your Quicknode endpoint in seconds and start building

Get started for free