Home

Polygon (MATIC) API Documentation

Polygon

Polygon (MATIC) is an EVM-compatible proof-of-stake chain whose Heimdall-v2 consensus layer uses CometBFT while Bor provides Ethereum-compatible execution; the Zurich hardfork activated on June 25, 2026. Solidity contracts compile to EVM bytecode against account-based state, while nodes maintain balances, contract storage, blocks, receipts, logs, and validator data across the execution and consensus layers. This EVM execution model preserves Ethereum transaction formats and JSON-RPC conventions while Polygon-specific consensus remains below the application interface.

Polygon API Methods and Endpoints

NOWNodes exposes Polygon's interface, plus a few others, depending on what your integration needs: JSON-RPC for reading chain state and broadcasting transactions, WSS (WebSocket) for real-time subscriptions and events, Blockbook for indexed address, balance, transaction, and block lookups, and Trace/Debug for step-level execution analysis. Archive mode extends any of these to historical states and data beyond standard retention.

Browse the interfaces below for endpoint details, request parameters, response formats, and integration examples. Create an API key, select Mainnet or Testnet, choose the required interface, and start sending requests from your application.

Weighing Polygon RPC providers against each other? Read the comparison guide on our blog — this page stays focused on integration reference.

Quick start

01

Get an API key

Sign up and generate a free key from the dashboard.

Get key →
02

Select environment

Mainnet or Sepolia testnet.

03

Choose an interface

RPC, WSS, Blockbook, or Trace/Debug.

04

Send a request

Call it from your application.

RPCJSON-RPCStandard RPC methods for reading chain state and broadcasting transactions.Node APIs →WSSWebSocketPersistent connections for new blocks, pending transactions, and log events as they happen.WSS API →T/DTrace & DebugStep-level execution traces for inspecting calls and diagnosing transactions.Trace & Debug API →ARCArchive modeFull historical state access beyond standard node retention.Archive nodes →MCPModel Context ProtocolThe Model Context Protocol (MCP) is an open standard that lets AI assistants call external tools through a uniform interface.MCP →

Ready to build on: MATIC

Create a free API key and start sending requests in minutes.