AsyncAPI channel · Chainstack
· Chainstack RPC WebSocket APIs
arbitrum/eth_subscribe/logs
Subscribe to Arbitrum event logs matching an optional address/topics filter.
Channel address
arbitrum/eth_subscribe/logs
Operations
publish
arbitrumSubscribeLogs
Subscribe to logs on Arbitrum
subscribe
arbitrumLogsNotification
Receive Arbitrum logs notifications
Messages
ethSubscribeLogs
JSON-RPC 2.0 request to subscribe to event logs matching an address/topics filter.
Content-Type:
application/jsonethSubscriptionLog
Push notification carrying an event log.
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.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.