AsyncAPI channel · Starknet · Starknet WebSocket RPC API

starknet_subscribeNewTransactionReceipts

Creates a WebSocket stream that fires notifications for new transaction receipts. The client may filter by `finality_status` (vector, default `[ACCEPTED_ON_L2]`; `ACCEPTED_ON_L1` is excluded) and `sender_address`. Notifications are delivered via `starknet_subscriptionNewTransactionReceipts`.

Open source AsyncAPI → All Starknet channels Starknet provider profile
Provider: Starknet AsyncAPI: v2.6.0 Spec: Starknet WebSocket RPC API Operations: 2 Messages: 5

Channel address

starknet_subscribeNewTransactionReceipts

Operations

publish
subscribeNewTransactionReceipts
Subscribe to new transaction receipts.
onSubscribeNewTransactionReceiptsResponse
Receive subscription id, receipt notifications, or reorg notifications.

Messages

SubscribeNewTransactionReceiptsRequest
JSON-RPC request opening a new-transaction-receipts 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
SubscriptionNewTransactionReceiptsNotification
Server-pushed notification carrying a new transaction receipt with block info.
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.

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

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This channel 
curl "https://apis.io/api/v1/channels/starknet-subscribenewtransactionreceipts"
All event channels 
curl "https://apis.io/api/v1/channels?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.