AsyncAPI channel · Helius · Helius WebSocket APIs

transactionSubscribe

Helius enhanced subscription. Streams transactions matched by a TransactionSubscribeFilter (vote, failed, signature, accountInclude up to 50,000, accountExclude up to 50,000, accountRequired up to 50,000) and shaped by TransactionSubscribeOptions (commitment, encoding, transactionDetails, showRewards, maxSupportedTransactionVersion). Available on Helius mainnet/devnet WS endpoints (and the legacy

Open source AsyncAPI → All Helius channels Helius provider profile
Provider: Helius AsyncAPI: v2.6.0 Spec: Helius WebSocket APIs Operations: 2 Messages: 4

Channel address

transactionSubscribe

Operations

publish
transactionSubscribe
Open a transactionSubscribe subscription.
transactionNotification
Filtered transaction notifications.

Messages

transactionSubscribe
Helius enhanced subscription opening a filtered transaction stream.
Content-Type: application/json
transactionUnsubscribe
transactionUnsubscribe request
Content-Type: application/json
jsonRpcResponse
Response to a subscribe / unsubscribe request — carries the subscription id (subscribe) or a boolean (unsubscribe).
Content-Type: application/json
transactionNotification
Helius enhanced transactionNotification payload.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.