Polygon RPC & APIs
Everything Triport offers on Polygon PoS behind one key: the Ethereum-compatible
eth_*JSON-RPC surface plus Polygon-nativebor_*methods, a REST product layer (wallets, mempool, bor/heimdall chain intel, tracing), WebSocket pub/sub, and firehose streams.
| Method / Endpoint | POST https://triport.io/polygon (JSON-RPC) · https://triport.io/v1/polygon/… (REST) · wss://triport.io/ws/polygon (streaming) |
| Network | Polygon (PoS) |
| Authentication | x-token header (SDK-preferred); see Authentication for all forms |
| Required scope | — (tier-gated per method/channel) |
| Tier / rate limit | Any tier; RPS-per-tier with burst, no daily quota — see Rate Limits |
Endpoints
| Surface | Endpoint | Reference |
|---|---|---|
| JSON-RPC | POST https://triport.io/polygon | Polygon JSON-RPC — 50 method pages |
| REST product | https://triport.io/v1/polygon/… | Polygon REST — 19 endpoint pages |
| Pub/Sub WebSocket | wss://triport.io/ws/polygon | Polygon WS (mirrors the Ethereum subscription types) |
| Bor firehose WS | see page | Bor firehose |
| Heimdall WS | see page | Heimdall stream |
All surfaces share the same API key, error envelope, and rate-limit model.
Quickstart
curl https://triport.io/polygon \
-H "x-token: $TRIPORT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'{ "jsonrpc": "2.0", "id": 1, "result": "0x4523a1c" }New to Triport? Getting Started takes you from zero to a verified response in under five minutes.
What is Polygon-specific here
bor_*namespace — validator/sprint introspection unique to Polygon:bor_getAuthor,bor_getCurrentValidatorsand the rest of the bor set alongside Ethereum-compatibleeth_*methods.- Chain-layer intel over REST — bor checkpoints, spans, current validators, and a heimdall proxy to the consensus layer.
- Tracing without archive setup — trace call and replay-transaction REST endpoints.
- Mempool & firehose — mempool snapshot / stats, plus raw bor and heimdall firehose WebSocket channels.
Rate limits
Polygon requests are budgeted by sustained RPS per tier and request category, with 2× burst and no daily quota. The per-tier numbers live in Rate Limits & Tiers.
POST Polygon JSON-RPC
The Polygon PoS JSON-RPC surface on POST https://triport.io/polygon — the Ethereum-compatible eth_ set plus the Polygon-native bor_ namespace for validator and sprint introspection.
GET Polygon REST API
Triport's product layer for Polygon under https://triport.io/v1/polygon/… — wallet data, mempool intel, bor/heimdall chain-layer queries, tracing, senders, and firehose WebSocket channels.
GET Platform API
Cross-network Triport endpoints — chain catalog and live metrics, per-key endpoint discovery, a diagnostics runner, and a server-sent events stream of chain status.