TriportRPCDashboard

EVM network documentation

Polygon RPC API reference

MainnetChain ID 13750 RPC methods

Polygon mainnet RPC endpoint: https://triport.io/polygon (HTTPS) and wss://triport.io/ws/poly (WebSocket), chain ID 137. Requests need a Triport API key in the x-token header; the Free plan is a 7-day trial. Endpoint, plans and limits: Polygon RPC endpoint.

HTTPS endpointhttps://triport.io/polygon
Polygon RPC endpointPlans, endpoints & pricing for PolygonPolygon chain ID, RPC URL & network configIdentifiers with sources, wallet setupBest Polygon RPC providers comparedPrices, rate limits and features, each with its source
All Polygon reference pages 57

JSON-RPC · polygon bor

JSON-RPC · polygon trace

JSON-RPC · polygon read rpc

JSON-RPC · polygon send tx

JSON-RPC · polygon txpool

REST

Streams

Guides & operations

Contracts

Capabilities

Statuses reflect checks up to 2026-10-10. Rate limits are plan policy, not measured capacity.

One key covers the Ethereum-compatible surface, Polygon-native bor_* methods, trace_* and debug_* tracing, the Heimdall consensus-layer REST proxy, and WebSocket Pub/Sub.

Method / EndpointNetworkChain IDAuthenticationRequired scopeTier / rate limit
POST https://triport.io/polygonPolygon mainnet137x-token: $TRIPORT_API_KEYpolygon:rpcCategory-specific RPS; see Limits

Endpoints

SurfaceEndpointReference
HTTPShttps://triport.io/polygonBackend path /rpc
WSSwss://triport.io/ws/polyRegistry path /ws/poly
RESTProduct routesREST catalog
Stream contractpoly wsAsyncAPI

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":[]}'

What's available

50 JSON-RPC methods in the OpenRPC catalog:

  • polygon_bor: 7
  • polygon_trace: 7
  • polygon_read_rpc: 32
  • polygon_send_tx: 1
  • polygon_txpool: 3

The Polygon surface adds Bor validator and sprint introspection, Heimdall data, tracing, mempool data, and firehose-related REST operations.

Limits

See network limits and Rate Limits & Tiers.

Finite request-rate budgets include a 2× burst buffer at no extra cost. It refills at sustained RPS; there is no quota on the number of bursts. Interval categories use seconds and have no RPS burst. See Burst capacity.

CategoryFreeBasicProBusinessEnterprise
polygon_read_rpc15 RPS sustained · up to 30 burst20 RPS sustained · up to 40 burst100 RPS sustained · up to 200 burst250 RPS sustained · up to 500 burstunlimited
polygon_send_tx3 RPS sustained · up to 6 burst5 RPS sustained · up to 10 burst30 RPS sustained · up to 60 burst80 RPS sustained · up to 160 burstunlimited
polygon_trace——3 RPS sustained · up to 6 burst10 RPS sustained · up to 20 burstunlimited
polygon_txpool——1 RPS sustained · up to 2 burst2 RPS sustained · up to 4 burstunlimited
polygon_txpool_snapshot_min_interval_sec——52unlimited

bor_*, trace, and txpool operations have category-specific tier gates.

Errors

See network-specific errors and the shared error reference.

Methods

polygon bor (7)

polygon trace (7)

polygon read rpc (32)

polygon send tx (1)

polygon txpool (3)

Streams

JavaScript (fetch)

The same request from JavaScript (Node 18+ or the browser):

const res = await fetch("https://triport.io/polygon", {
  method: "POST",
  headers: {
    "x-token": process.env.TRIPORT_API_KEY,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}),
});
const { result } = await res.json();
console.log(result);

Tutorial: stream pending Ethereum and Polygon transactions — Polygon's hash-only stream, and fetching bodies within your plan's read budget.