eth_getLogs

eth_getLogs returns every event log on Polygon PoS (chain ID 137) that matches a filter object built from an address, a set of topics, and a block range (or a single blockHash). It is the primary one-shot method for log queries and backfill indexing: instead of maintaining a stateful filter, you describe exactly what you want and get the full matching set in one response. On Polygon, where MATIC pays for gas and the EVM-equivalent chain emits enormous volumes of Transfer and swap events from USDC, USDT, QuickSwap, and Aave, eth_getLogs against https://polygon.therpc.io/YOUR_API_KEY is how most indexers and analytics pipelines pull historical activity.

Use cases

• Backfill Transfer events for a token over a historical block range — for example tracing USDT on Polygon at 0xc2132D05D31c914a87C6611C10748AEb04B58e8F across a window of blocks.
• Index DeFi protocol events from QuickSwap pools or Aave markets into an analytics dashboard.
• Reconstruct a contract's state by replaying its past events when no convenient on-chain getter exists.
• Verify that a specific event (such as a settlement on Polymarket) was emitted within a given transaction by filtering on its transactionHash-bearing block.

Parameters

Response

Example request

1curl https://polygon.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5    "jsonrpc": "2.0",
6    "method": "eth_getLogs",
7    "params": [{}],
8    "id": 1
9  }'

Try it live in the Polygon playground.

Errors & troubleshooting

Common pitfalls

• Logs from recent, not-yet-checkpointed Polygon blocks can vanish if Bor reorgs before the block is finalized to Ethereum L1 — check the removed field and re-query once the range is finalized.
• Wide block ranges or filters with no address/topics cause timeouts or range-cap errors; given Polygon's ~2-second blocks and high event density, paginate in chunks of roughly 1000–5000 blocks.
• Polling eth_getLogs with fromBlock: "latest" in a tight loop wastes CUs and can miss events — use eth_newFilter + eth_getFilterChanges or eth_subscribe for live streams instead.

Supported networks

• Mainnet — Chain ID: 137
• Amoy — Chain ID: 80002

See also

• eth_newFilter
• eth_getFilterLogs
• eth_subscribe

1curl https://polygon.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H 'Content-Type: application/json' \
4  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getLogs","params":[{}]}'