eth_subscribe - opBNB

Example code for the eth_subscribe JSON-RPC method. Сomplete guide on how to use eth_subscribe JSON-RPC in GetBlock.io Web3 documentation.

This method creates a real-time subscription over a WebSocket connection. Available subscription types are newHeads (new block headers), logs (matching contract events), and newPendingTransactions (pending transactions).

This method is only available over WebSocket transport — use wss://go.getblock.io/<ACCESS-TOKEN>/.

Parameters

Parameter
Type
Required
Description

subscriptionType

string

Yes

One of "newHeads", "logs", "newPendingTransactions"

filterObject

object

No

For "logs": filter with address and/or topics

Request Example

cURL (wscat)
# This method requires WebSocket connection
wscat -c wss://go.getblock.io/<ACCESS-TOKEN>/

> {"jsonrpc":"2.0","method":"eth_subscribe","params":["newheads"],"id":"getblock.io"}

Response Example

{
    "jsonrpc": "2.0",
    "id": "getblock.io",
    "result": "0x9cef478923ff08bf67fde6c64013158d"
}

Response Parameters

Field
Type
Description

result

string

Subscription ID, used to match incoming eth_subscription notifications and to call eth_unsubscribe

Use Cases

  • Real-time wallet activity notifications

  • Live DEX trade feeds for trading UIs

  • Streaming indexers that react to new blocks instantly

  • Mempool surveillance for MEV bots

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

-32602

Invalid params

Request parameters are missing or malformed

-32601

Method not found

The method is not supported by this node

429

Too Many Requests

Rate limit exceeded for your plan

-32600

Invalid Request

eth_subscribe was called over HTTP; use a WebSocket connection instead

SDK Integration

Last updated

Was this helpful?