AsyncAPI channel · zkSync · zkSync Era WebSocket JSON-RPC PubSub API

/

Single bidirectional WebSocket channel carrying JSON-RPC 2.0 request, response, and notification messages. Clients send `eth_subscribe` requests to open a subscription, then receive `eth_subscription` notifications until they call `eth_unsubscribe`.

Open source AsyncAPI → All zkSync channels zkSync provider profile
Provider: zkSync AsyncAPI: v2.6.0 Spec: zkSync Era WebSocket JSON-RPC PubSub API Operations: 2 Messages: 8

Channel address

/

Operations

publish
sendJsonRpcRequest
Send a JSON-RPC 2.0 request from the client to the zkSync Era node.
receiveJsonRpcMessage
Receive JSON-RPC 2.0 responses and subscription notifications.

Messages

eth_subscribe
Open a new subscription. First parameter is the subscription type name (`newHeads`, `logs`, or `newPendingTransactions`). For `logs` an optional filter object may be supplied as the second parameter.
Content-Type: application/json
eth_unsubscribe
Cancel an existing subscription by ID.
Content-Type: application/json
eth_subscribe_response
JSON-RPC response returning a subscription ID for an eth_subscribe call.
Content-Type: application/json
eth_unsubscribe_response
JSON-RPC response confirming a subscription was cancelled.
Content-Type: application/json
newHeads
Notification delivered when a new block header is produced on zkSync Era.
Content-Type: application/json
logs
Notification delivered when a new log entry matches the filter.
Content-Type: application/json
newPendingTransactions
Notification with the transaction hash of a new pending transaction.
Content-Type: application/json
jsonrpc_error
Error response envelope.
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.