web3_clientVersion

web3_clientVersion returns a free-form string identifying the node's client software and version. On Polygon PoS the execution client is Bor, a Geth fork, so the string typically looks like a Bor/Geth build identifier with version, platform, and Go compiler details. It is useful for knowing exactly which implementation is serving your MATIC requests. Call it against the Polygon mainnet endpoint at https://polygon.therpc.io/YOUR_API_KEY (chain ID 137, 0x89).

Use cases

• Detect the underlying Polygon client type and version (for example a specific Bor release) to enable or disable client-specific behavior in your tooling.
• Log node identity during infrastructure diagnostics so you can correlate Polygon RPC issues with a particular client build across your fleet.

Parameters

هذا الأسلوب لا يأخذ أي معاملات. مرر مصفوفة فارغة [].

Response

Example request

1curl https://polygon.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5    "jsonrpc": "2.0",
6    "method": "web3_clientVersion",
7    "params": [],
8    "id": 1
9  }'

Try it live in the Polygon playground.

Errors & troubleshooting

Common pitfalls

• Managed Polygon RPC providers often return a custom, normalized, or redacted string rather than the exact Bor build, so do not assume it reveals the precise patch version behind the endpoint.
• Do not gate production behavior on parsing this string for feature detection — implementations and formats vary. Instead test whether the specific method you need is available by calling it.

Supported networks

• Mainnet — Chain ID: 137
• Amoy — Chain ID: 80002

See also

• net_version

1curl https://polygon.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H 'Content-Type: application/json' \
4  -d '{"jsonrpc":"2.0","id":1,"method":"web3_clientVersion","params":[]}'