Polygon JSON-RPC
The Polygon PoS JSON-RPC surface on
POST https://triport.io/polygon— the Ethereum-compatibleeth_*set plus the Polygon-nativebor_*namespace for validator and sprint introspection.
Choosing an endpoint or a plan rather than a method? See Polygon RPC endpoint. Chain ID, RPC URL and network config: Polygon chain ID & RPC URL.
- Method / Endpoint
POST https://triport.io/polygon- Network
- Polygon (PoS)
- Authentication
x-tokenheader (recommended); see Authentication- Required scope
- — (tier-gated per method)
- Tier / rate limit
- Any tier; see Rate Limits
How to call
Every method takes the same envelope — only method and params change:
curl https://triport.io/polygon \
-H "x-token: $TRIPORT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"bor_getAuthor","params":["latest"]}'Batching (a JSON array of request objects) is supported; each entry is tier-checked and rate-limited individually.
Support semantics
| Status | Meaning |
|---|---|
| Supported | Routed to an upstream node, result returned unchanged — Ethereum-compatible eth_*, net_*, web3_* plus Polygon-native bor_*. |
| Not supported | Methods outside the catalog return -32601 (method_unknown). |
See Errors for the full error envelope.
Method reference
The pages below are grouped by namespace — the Ethereum-compatible set and the
bor_ namespace (bor_getAuthor, bor_getCurrentValidators,
bor_getSnapshot, …). Subscriptions live on the WebSocket channel — see
Polygon WS.