The Event Log API was designed to provide an alternative to the native eth_getLogs.

Below are the list of supported filter parameters:

  • fromBlock, toBlock, address

  • topic0, topic1, topic2, topic3 (32 Bytes per topic)

  • topic0_1_opr (and|or between topic0 & topic1), topic1_2_opr (and|or between topic1 & topic2), topic2_3_opr (and|or between topic2 & topic3), topic0_2_opr (and|or between topic0 & topic2), topic0_3_opr (and|or between topic0 & topic3), topic1_3_opr (and|or between topic1 & topic3)

Some parameters to take note of 📝

  • FromBlock & ToBlock accepts the blocknumber (integer, NOT hex) or 'latest' (earliest & pending is NOT supported yet)

  • Topic Operator (opr) choices are either 'and' or 'or' and are restricted to the above choices only

  • FromBlock & ToBlock parameters are required

  • An address and/or topic(X) parameters are required, when multiple topic(X) parameters are used the topicX_X_opr (and|or operator) is also required

For performance & security considerations, only the first 1000 results are returned. So please narrow down the filter parameters.

Sample Log API Queries

Get Event Logs from block number 13064617 to 'latest' block, where log address = 0xb31f66aa3c1e785363f0875a1b74e27b85fd66c7 and topic[0] = 0x8c5be1e5ebec7d5bd14f71427d1e84f3dd0314c0f7b2291e5b200ac8c7c3b925


Try this endpoint in your browser 🔗

Get Event Logs from block number 13063758 to block 13064758, where log address = 0xa7d7079b0fead91f3e65f86e8915cb59c1a4c664, topic[0] = 0x8c5be1e5ebec7d5bd14f71427d1e84f3dd0314c0f7b2291e5b200ac8c7c3b925 'AND' topic[2] = 0x00000000000000000000000060ae616a2155ee3d9a68541ba4544862310933d4


Try this endpoint in your browser 🔗

Last updated