AsyncAPI channel · Arbitrum
· Arbitrum Public WebSocket APIs
eth_subscribe/logs
`eth_subscribe("logs", {address, topics})` on a Nitro JSON-RPC WebSocket. Emits a notification for each log matching the supplied address/topics filter.
Provider:ArbitrumAsyncAPI: v2.6.0Spec: Arbitrum Public WebSocket APIsOperations: 2Messages: 2
Channel address
eth_subscribe/logs
Operations
publish
subscribeLogs
Open a `logs` subscription with an address/topics filter.
subscribe
receiveLogs
Receive `eth_subscription` notifications for matching logs.
Messages
JsonRpcSubscribeRequestLogs
eth_subscribe logs request
Content-Type: application/json
EthSubscriptionLog
eth_subscription notification — logs
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.