Ethereum

Ethereum

eth_getLogs

eth_getLogs is the workhorse for reading Ethereum events. Every emit in a Solidity contract — an ERC-20 Transfer, a Uniswap Swap, an Aave borrow — leaves a log on Ethereum mainnet (chain ID 1, the EVM network where gas is paid in ETH), and this method pulls back all the logs that match a filter object you describe. You filter by address (one contract or several), by indexed topics, and by a block range with fromBlock/toBlock, or pin a single block with blockHash. Unlike the stateful filter API, it's a one-shot query: no eth_newFilter registration, no polling cursor. That makes it the standard tool for backfilling and indexing event history. Send the request to https://ethereum.therpc.io/YOUR_API_KEY.

Use cases

• Backfill an ERC-20's Transfer history by setting address to the token and topics[0] to the Transfer(address,address,uint256) signature hash, walking the range in chunks.
• Feed an analytics dashboard: pull Swap, Mint, and Burn events from Uniswap pools or borrow events from Aave to reconstruct volumes and TVL over time.
• Rebuild contract state from its event trail when there's no view function for what you need — replaying ordered logs is often the only way to recover historical positions.
• Confirm a specific event fired inside one transaction by pinning the query with blockHash and matching on the contract address and topic.

Parameters

Response

Example request

1curl https://ethereum.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 Ethereum playground.

Errors & troubleshooting

Common pitfalls

• Logs from blocks that aren't yet finalized can vanish in a head reorg. Watch the removed field, and for anything that moves value, re-query once the block reaches finalized (roughly 12.8 minutes, two epochs, after it was proposed).
• A wide range with no address or topics makes the node scan far too much and you'll hit a block-range cap or the 10,000-result ceiling — both surface as -32005. Paginate in chunks of about 1,000 to 5,000 blocks and always narrow by address or topic.
• Looping eth_getLogs with fromBlock: "latest" to fake a live feed is wasteful and races the chain head. For streaming, use eth_newFilter + eth_getFilterChanges, or subscribe to logs over WebSocket with eth_subscribe.

Supported networks

• Mainnet — Chain ID: 1
• Sepolia — Chain ID: 11155111

See also

• eth_newFilter
• eth_getFilterLogs
• eth_subscribe

1curl https://ethereum.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":[{}]}'