POST
/
efb0a5eccd2caa5135eb54eba6f7f300
curl --request POST \
  --url https://optimism-mainnet.core.chainstack.com/efb0a5eccd2caa5135eb54eba6f7f300 \
  --header 'Content-Type: application/json' \
  --data '{
  "jsonrpc": "2.0",
  "method": "eth_getFilterLogs",
  "id": 1,
  "params": [
    "0x5a6b7c"
  ]
}'
{
  "jsonrpc": "<string>",
  "id": 123,
  "result": [
    {
      "removed": true,
      "logIndex": "<string>",
      "transactionIndex": "<string>",
      "transactionHash": "<string>",
      "blockHash": "<string>",
      "blockNumber": "<string>",
      "address": "<string>",
      "data": "<string>",
      "topics": [
        "<string>"
      ]
    }
  ]
}

Optimism API method eth_getFilterLogs retrieves all logs matching a previously created filter. This method is essential for applications that need to fetch historical log data based on specific criteria.

Disclaimer

Note that the default interactive example in this page will not work as the filter will be expired.

To test eth_getFilterLogs in this page, first create a new filter using one of the following:

Then use the fresh filter ID as the parameter for eth_getFilterChanges.

Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • filterId — the ID of the filter for which logs are being fetched. This ID is returned by filter creation methods such as eth_newBlockFilter, or eth_newFilter. For this example, a random value "0x5a6b7c" is used.

​
Response

  • result — an array of log objects. Each log object contains details such as whether the log was removed (due to a chain reorganization), log index, transaction index, transaction hash, block hash, block number, address from which the log originated, data contained in the log, and topics associated with the log.

​
Use case

The eth_getFilterLogs method is essential for:

  • DApps that require access to historical log data for analysis or display purposes.
  • Services that monitor smart contract interactions over time, needing to retrieve all past events that match certain criteria.
  • Analytical tools that process and visualize blockchain data based on logs from specific contracts or transactions.

Body

application/json

Response

200 - application/json

All logs matching the filter

The response is of type object.