AsyncAPI channel · QuickNode · QuickNode WebSocket Subscription API

ethereum/logs

Subscribe to event logs matching filter criteria (addresses, topics) via `eth_subscribe` with the `logs` subscription type.

Provider: QuickNode AsyncAPI: v2.6.0 Spec: QuickNode WebSocket Subscription API Operations: 2 Messages: 5

Channel address

ethereum/logs

Operations

publish
subscribeEthLogs
Send eth_subscribe / eth_unsubscribe for logs
receiveEthLogs
Receive subscription id and log notifications

Messages

EthSubscribeLogsRequest
Subscribe to logs matching an optional address/topics filter
Content-Type: application/json
EthUnsubscribeRequest
Cancel an active eth_subscribe subscription
Content-Type: application/json
EthSubscribeResponse
Returned subscription id (hex string)
Content-Type: application/json
EthUnsubscribeResponse
eth_unsubscribe response
Content-Type: application/json
EthLogsNotification
eth_subscription logs notification
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.