web3_clientVersion
https://triport.io/rpc/bscReturn the selected node client version.
web3_clientVersion returns the software version string reported by the selected BNB Smart Chain node.
Use it for diagnostics, compatibility investigation, or support data. Requests may be routed among eligible upstream nodes, so applications must not assume that the returned string is stable across calls.
This method identifies client software only. Use eth_chainId to verify the chain and eth_syncing to inspect synchronization state.
Parameters
JSON-RPC params must be an empty array: [].
Response
The response below is the checked fixture for this method; it is reproduced without changing its fields or values.
resultstringErrors
Errors use the standard JSON-RPC error envelope. See BSC errors for network-specific classification and the linked shared reference.
| Code | Meaning | When it happens |
|---|---|---|
-32602 | Invalid params | A required positional parameter is missing or a value does not match the OpenRPC schema. |
401 | Unauthorized | The x-token API key is missing or invalid. |
429 | Rate limited | The request exceeds the configured category RPS for the caller's tier. |
Examples
JavaScript (fetch)
const response = await fetch("https://triport.io/rpc/bsc", {
method: "POST",
headers: {
"x-token": process.env.TRIPORT_API_KEY,
"Content-Type": "application/json",
},
body: JSON.stringify({
"jsonrpc": "2.0",
"id": 1,
"method": "web3_clientVersion",
"params": []
}),
});
const payload = await response.json();
console.log(payload.result);Notes
- The BSC categories use configured defaults of 15 / 20 / 100 / 250 RPS; they are marked unmeasured in the tier matrix.
- Related methods:
eth_chainId,eth_syncing,net_version.