Understanding your request consumption over HTTP and WebSocket

You can view your node requests metrics on all subscription plans.

A request is a single successful JSON-RPC call to a node through an HTTPS or WebSocket Secure endpoint.

A request is considered successful and consumed in the following cases:

• HTTP: the server returns 200
• WebSocket: the server sends a message

For example, sending an eth_getLogs request over HTTP will return all events specified in the request and count as one request.

Sending an eth_subscribe request over WebSocket will subscribe to events in real time and each event sent will count as one request.

See also:

• Subscribing to smart contract events with web3.js
• Getting logs and events of EVM smart contracts