AsyncAPI channel · Alchemy · Alchemy WebSocket Subscription API

/

The single multiplexed JSON-RPC WebSocket channel. Clients publish `eth_subscribe` and `eth_unsubscribe` requests, and the server publishes acknowledgement responses and `eth_subscription` notifications for every active subscription on the same connection.

Open source AsyncAPI → All Alchemy channels Alchemy provider profile
Provider: Alchemy AsyncAPI: v2.6.0 Spec: Alchemy WebSocket Subscription API Operations: 2 Messages: 11

Channel address

/

Operations

publish
sendRpcRequest
Send a JSON-RPC request (subscribe / unsubscribe).
receiveRpcMessage
Receive a JSON-RPC response or subscription notification.

Messages

EthSubscribeRequest
Create a new subscription.
Content-Type: application/json
EthUnsubscribeRequest
Cancel an existing subscription by id.
Content-Type: application/json
SubscribeResponse
Acknowledgement of an eth_subscribe call, returning the subscription id.
Content-Type: application/json
UnsubscribeResponse
Acknowledgement of an eth_unsubscribe call.
Content-Type: application/json
NewHeadsNotification
Emitted when a new block header is added to the chain.
Content-Type: application/json
LogsNotification
Emitted for every log entry matching the filter as new blocks are produced.
Content-Type: application/json
NewPendingTransactionsNotification
Emitted with the hash of each transaction newly added to the Alchemy mempool. Note that only transactions seen by Alchemy nodes are delivered.
Content-Type: application/json
SyncingNotification
Emitted when the node starts or stops synchronizing with the network, with progress details while syncing.
Content-Type: application/json
AlchemyMinedTransactionsNotification
Emitted for every transaction that gets mined matching the configured `addresses` filter. Formerly `alchemy_filteredNewFullPendingTransactions`.
Content-Type: application/json
AlchemyPendingTransactionsNotification
Emitted for every pending transaction matching the `fromAddress` / `toAddress` filter. Formerly `alchemy_filteredFullPendingTransactions`.
Content-Type: application/json
RpcErrorResponse
JSON-RPC 2.0 error envelope returned for malformed or unauthorized requests.
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/untitled"
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.