AsyncAPI channel · Starknet
· Starknet WebSocket RPC API
starknet_subscribeNewTransactions
Creates a WebSocket stream that fires notifications for new transactions.
The client may filter by `finality_status` vector (default
`[ACCEPTED_ON_L2]`; `ACCEPTED_ON_L1` is excluded), `sender_address`, and
optional `tags` (e.g. `INCLUDE_PROOF_FACTS`). Notifications are delivered
via `starknet_subscriptionNewTransaction`.
Receive subscription id, transaction notifications, or reorg notifications.
Messages
SubscribeNewTransactionsRequest
JSON-RPC request opening a new-transactions subscription.
Content-Type: application/json
SubscriptionIdResponse
Returned by the server in response to any successful
`starknet_subscribe*` request; the `result` is the assigned
`subscription_id` which is echoed in every subsequent notification.
Content-Type: application/json
SubscriptionNewTransactionNotification
Server-pushed notification carrying a new transaction with hash and finality status.
Content-Type: application/json
SubscriptionReorgNotification
Server-pushed notification that the chain has reorganized. Can be
emitted on subscriptions of type newHeads, Events, TransactionStatus,
NewTransactionReceipts, and NewTransactions.
Content-Type: application/json
JsonRpcErrorResponse
Returned when a `starknet_subscribe*` or `starknet_unsubscribe` request
fails. Error codes defined by the WebSocket spec include
INVALID_SUBSCRIPTION_ID (66), TOO_MANY_ADDRESSES_IN_FILTER (67), and
TO
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.