AsyncAPI channel · Arbitrum · Arbitrum Public WebSocket APIs

eth_subscribe/syncing

`eth_subscribe("syncing")`. Accepted by Nitro for go-ethereum compatibility. Notifications reflect the local node's sync status.

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/syncing

Operations

publish
subscribeSyncing
Open a `syncing` subscription.
receiveSyncing
Receive `syncing` status notifications.

Messages

JsonRpcSubscribeRequestSyncing
eth_subscribe syncing request
Content-Type: application/json
EthSubscriptionSyncing
eth_subscription notification — syncing
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.