Single WebSocket channel carrying all JSON-RPC traffic. Clients send `eth_subscribe` requests to start subscriptions, receive an id in response, and then receive `eth_subscription` notifications keyed to that id until they call `eth_unsubscribe`.
Send a JSON-RPC 2.0 request over the WebSocket connection.
subscribe
receiveRpcMessage
Receive JSON-RPC 2.0 responses and subscription notifications.
Messages
eth_subscribe_newHeads
Subscribe to notifications for each new block header sealed by Mantle.
Content-Type: application/json
eth_subscribe_logs
Subscribe to logs matching a filter object (address and/or topics). Notifications are emitted for each matching log included in a new canonical block.
Content-Type: application/json
eth_subscribe_newPendingTransactions
Subscribe to notifications for transactions added to the pending state. By default, the server emits transaction hashes; when the optional second boolean parameter is `true`, full transaction objects
Content-Type: application/json
eth_subscribe_syncing
Subscribe to notifications when the node starts or stops syncing with the network.
Content-Type: application/json
eth_unsubscribe
Cancel the subscription identified by the subscription id.
Content-Type: application/json
subscribe_response
JSON-RPC response returning the subscription id for an `eth_subscribe` call.
Content-Type: application/json
unsubscribe_response
JSON-RPC response confirming whether the unsubscribe succeeded.
Content-Type: application/json
newHeads_notification
Emitted for each new block header sealed by the Mantle network.
Content-Type: application/json
logs_notification
Emitted for each log matching the original filter.
Content-Type: application/json
newPendingTransactions_notification
Emitted for each transaction newly accepted into the pending state. The result is a transaction hash by default, or a full transaction object if the subscription was opened with the optional `true` fl
Content-Type: application/json
syncing_notification
Emitted when the node starts or stops syncing with the network.
Content-Type: application/json
jsonrpc_error
Standard JSON-RPC 2.0 error envelope returned on invalid requests.
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.
Discovery needs no key. Ratings and market analysis are Pro.
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.