net_listening — Ethereum JSON-RPC

Status: Available

Returns whether the Ethereum node is actively listening for network connections.

POSThttps://triport.io/eth

Network: Ethereum
Auth: x-token: $TRIPORT_API_KEY (or Authorization: Bearer)
Rate limit: free — 10 RPS sustained · up to 20 burst · basic 20 RPS sustained · up to 40 burst · pro 100 RPS sustained · up to 200 burst · business 250 RPS sustained · up to 500 burst; Burst capacity

Endpoint and plans: Ethereum RPC endpoint.

Request

cURLJavaScriptPython

curl https://triport.io/eth \
  -H "Authorization: Bearer $TRIPORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "net_listening",
    "params": []
  }'

const res = await fetch("https://triport.io/eth", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.TRIPORT_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "jsonrpc": "2.0",
    "id": 1,
    "method": "net_listening",
    "params": []
  }),
});
const data = await res.json();
console.log(data);

import os


import requests


resp = requests.post(
    "https://triport.io/eth",
    headers={
        "Authorization": f"Bearer {os.environ['TRIPORT_API_KEY']}",
        "Content-Type": "application/json",
    },
    json={
        "jsonrpc": "2.0",
        "id": 1,
        "method": "net_listening",
        "params": [],
    },
)
data = resp.json()
print(data)

Response

JSON

Example

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": true
}

net_listening reports whether the underlying Ethereum node is currently listening for inbound peer-to-peer network connections. It returns a single boolean: true when the node is accepting connections, false otherwise.

Use it as a lightweight health/liveness probe before issuing heavier calls, or as part of a monitoring loop. It takes no parameters and is available on the Free trial, so it is a cheap way to confirm the endpoint is reachable and your API key is valid.

This is a read-only method in the net namespace. It does not reflect peer count — use net_peerCount for that.

Parameters

This method takes no parameters. Pass an empty array for params.

——optional

No parameters.

Response

Response fields

Field	Type	Description
`jsonrpc`	string	JSON-RPC version, always `"2.0"`.
`id`	number	Echoes the request `id`.
`result`	boolean	`true` if the node is listening for network connections, otherwise `false`.

Errors

Code	Meaning	When it happens
`401`	`trial_expired`	The API key's trial period has ended; upgrade the plan to continue.
`429`	`rate_limited`	Requests exceeded the per-tier RPS limit (10 RPS sustained · up to 20 burst on free). Back off and retry.

Errors are returned in the standard JSON-RPC error envelope. See the shared Errors page for the full envelope and handling guidance.

Examples

JavaScript (fetch)

JavaScript

const res = await fetch("https://triport.io/eth", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.TRIPORT_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    jsonrpc: "2.0",
    id: 1,
    method: "net_listening",
    params: [],
  }),
});


const { result } = await res.json();
console.log("listening:", result); // true

Notes

The result is almost always true for a healthy synced node; a false value indicates the node has disabled inbound networking.
For richer connectivity diagnostics, pair this with net_peerCount (number of connected peers) and net_version (network ID).
No parameters and no daily quota — rate limiting is purely RPS-per-tier with burst allowance.