AsyncAPI channel · Optimism
· Optimism (OP Stack) WebSocket JSON-RPC API
eth_subscribe.syncing
Subscription that emits when the node enters or exits sync. The notification is either `false` (synced) or a `SyncStatus` object describing progress. Behaviour matches upstream go-ethereum / op-geth.
Channel address
eth_subscribe.syncing
Operations
publish
subscribeSyncing
Subscribe to sync-status changes (`eth_subscribe("syncing")`).
subscribe
onSyncing
Receive sync-status change notifications.
Messages
SubscribeSyncingRequest
JSON-RPC request to subscribe to sync status changes.
Content-Type:
application/jsonSubscribeResponse
JSON-RPC response containing the subscription id.
Content-Type:
application/jsonSyncingNotification
Notification carrying the current sync status.
Content-Type:
application/jsonAbout 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.