Polygon REST API

Triport's REST surface for Polygon: the Heimdall consensus-layer proxy for checkpoints, spans, validator sets and chain status over plain HTTP. Everything else on Polygon is served over JSON-RPC and WebSocket.

Endpoint and plans: Polygon RPC endpoint.

Method / Endpoint: GET https://triport.io/rpc/polygon-heimdall/…
Network: Polygon (PoS)
Authentication: x-token header (recommended); see Authentication
Required scope: — (tier-gated per endpoint)
Tier / rate limit: Any tier; see Rate Limits

What this surface is

Unlike JSON-RPC, which proxies the chain's native methods verbatim, the REST layer is built by Triport: indexed, opinionated endpoints that answer product questions in one call.

Endpoint groups

Heimdall — the Heimdall consensus-layer proxy: checkpoints, Bor spans, validator sets and chain status.

Everything else on Polygon goes through the standard interfaces: balances and sending via JSON-RPC (eth_getBalance, eth_sendRawTransaction), tracing via trace_call, live blocks, logs and pending transactions via WebSocket, and wallet history via the cross-chain Wallet Research endpoint.

The full endpoint list is below.

ANY Heimdall consensus RPC proxy

A transparent reverse-proxy that forwards Polygon Heimdall consensus-layer requests (Tendermint RPC, Cosmos LCD, and the consensus Prometheus port) through a single authenticated path on the Triport edge.