AsyncAPI channel · Optimism · Optimism (OP Stack) WebSocket JSON-RPC API

eth_subscribe.logs

Subscription that pushes a notification for every log matching a filter. Filter parameters mirror upstream `eth_getLogs` (`address`, `topics`). Log entries include the standard fields plus may be associated with receipts that carry OP Stack L1 fee fields (`l1GasUsed`, `l1GasPrice`, `l1Fee`, `l1FeeScalar`) when fetched via `eth_getTransactionReceipt`.

Open source AsyncAPI → All Optimism channels Optimism provider profile
Provider: Optimism AsyncAPI: v2.6.0 Spec: Optimism (OP Stack) WebSocket JSON-RPC API Operations: 2 Messages: 3

Channel address

eth_subscribe.logs

Operations

publish
subscribeLogs
Subscribe to event logs (`eth_subscribe("logs", filter)`).
onLog
Receive a notification for each matching log entry.

Messages

SubscribeLogsRequest
JSON-RPC request to subscribe to logs matching a filter.
Content-Type: application/json
SubscribeResponse
JSON-RPC response containing the subscription id.
Content-Type: application/json
LogNotification
Notification carrying a single matching log entry.
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.