AsyncAPI channel · Arbitrum · Arbitrum Public WebSocket APIs

eth_subscribe/newHeads

`eth_subscribe("newHeads")` on a Nitro JSON-RPC WebSocket. Emits a notification for every new L2 head produced by the Sequencer. Blocks include Arbitrum-specific fields (`l1BlockNumber`, `sendRoot`, `sendCount`, modified `mixHash`, fixed `difficulty` / `gasLimit`).

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

Channel address

eth_subscribe/newHeads

Operations

publish
subscribeNewHeads
Open a `newHeads` subscription.
receiveNewHeads
Receive `eth_subscription` notifications for new heads.

Messages

JsonRpcSubscribeRequestNewHeads
eth_subscribe newHeads request
Content-Type: application/json
EthSubscriptionNewHead
eth_subscription notification — newHeads
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.