Root WebSocket channel for the selected Infura network. All
JSON-RPC requests (`eth_subscribe`, `eth_unsubscribe`, plus any
standard Ethereum JSON-RPC method) are sent as text frames on this
single connection, and asynchronous `eth_subscription`
notifications stream back over the same connection.
Server-to-client frames (responses and notifications)
Messages
eth_subscribe
Create a new subscription for a particular event.
Content-Type: application/json
eth_unsubscribe
Cancel an existing subscription by its subscription ID.
Content-Type: application/json
eth_subscribe_response
JSON-RPC response containing the newly created subscription ID.
Content-Type: application/json
eth_unsubscribe_response
Boolean flag indicating whether unsubscription succeeded.
Content-Type: application/json
newHeads
Emitted each time a new header is appended to the chain.
Content-Type: application/json
logs
Emitted when matching event logs are included in new blocks.
Content-Type: application/json
newPendingTransactions
Emitted as new transactions enter the pending pool.
Content-Type: application/json
jsonrpc_error
Standard JSON-RPC 2.0 error envelope.
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.