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`.
Subscribe to event logs (`eth_subscribe("logs", filter)`).
subscribe
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.