eth_getLogs

eth_getLogs returns all event logs emitted on Polygon that match a single filter object. It is the primary event-indexing primitive: ERC-20 Transfers, DEX swaps, mints, bridge events — anything emitted with LOG0–LOG4 on Polygon mainnet (Bor consensus).

You select logs in one of two mutually exclusive ways:

• By block range — set fromBlock and toBlock (tags or hex block numbers). The range is inclusive on both ends.
• By a single block — set blockHash to pin the query to exactly one block. blockHash cannot be combined with fromBlock/toBlock.

Within that window you narrow further by address (one or many contracts) and by topics (the indexed event signature and arguments). The result is a flat, chronologically ordered array of log objects; an empty array means nothing matched (this is not an error).

This is a read method available from the free tier. Polygon's block time is ~2.1 s, so a given wall-clock window covers roughly 6× more blocks than the same window on Ethereum — keep ranges bounded. For high-frequency Polygon event streams (e.g. Uniswap-style swaps can exceed 10,000 events/minute) prefer a WebSocket subscription over polling eth_getLogs (see Notes).

JSON-RPC params is a positional array with a single element: [filter].

Response fields

result is an array of log objects. Each object has:

Errors are returned in the standard JSON-RPC error envelope. See the shared errors reference for the full envelope shape and shared codes.

A malformed filter — e.g. blockHash combined with fromBlock/toBlock, a badly formatted address or topic, or a block range that exceeds the provider's limit — is rejected with the standard -32602 invalid-params error.

JavaScript (fetch)

const res = await fetch("https://api.triport.io/v1/polygon", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.TRIPORT_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    jsonrpc: "2.0",
    id: 1,
    method: "eth_getLogs",
    params: [{
      fromBlock: "0x3658060",
      toBlock: "0x3658070",
      address: "0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174",
      topics: [
        "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
      ],
    }],
  }),
});


const { result } = await res.json();
console.log(`Matched ${result.length} logs`);
for (const log of result) {
  console.log(`${log.blockNumber} ${log.transactionHash} logIndex=${log.logIndex}`);
}

TypeScript SDK (@triport/sdk)

import { Triport } from "@triport/sdk";


const client = new Triport({ apiKey: process.env.TRIPORT_API_KEY });


const TRANSFER =
  "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef";


const logs = await client.polygon.request("eth_getLogs", [{
  fromBlock: "0x3658060",
  toBlock: "0x3658070",
  address: "0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174",
  topics: [TRANSFER],
}]);


console.log(`Matched ${logs.length} logs`);

Python (triport-sdk)

import os
from triport import Triport


client = Triport(api_key=os.environ["TRIPORT_API_KEY"])


TRANSFER = "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"


logs = client.polygon.request("eth_getLogs", [{
    "fromBlock": "0x3658060",
    "toBlock": "0x3658070",
    "address": "0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174",
    "topics": [TRANSFER],
}])


print(f"Matched {len(logs)} logs")

• Block range vs. block hash: supply either fromBlock/toBlock or blockHash, never both. blockHash is the precise way to read all logs from one specific block regardless of reorgs.
• Bound your ranges: a maximum block span per call applies, and very wide windows (or unfiltered address + topics) can return large result sets and are slow. For historic indexing, walk the chain in fixed-size windows (e.g. a couple of thousand blocks per call) and accumulate results. There is no daily quota — pacing is RPS-per-tier with burst.
• Polygon block time: at ~2.1 s per block, ranges grow quickly in wall-clock terms — a one-hour window is roughly 1,700 blocks. Size windows by block count, not by time.
• High-frequency events: for real-time indexing of hot contracts (DEX swaps, bridges) polling eth_getLogs will lag and miss bursts. Use a WebSocket eth_subscribe / logs subscription instead and reserve eth_getLogs for backfill and historic queries.
• Reorgs: logs from recent, non-finalized blocks may later be reorged out; such logs reappear in a subsequent query with removed: true. Query against the finalized tag when you need stability — Bor finality lands a few epochs back.
• Empty result: a filter that matches nothing returns "result": [], which is a success, not an error.
• Related methods: use eth_getBlockReceipts to pull every receipt (and its logs) for a block, eth_getTransactionReceipt for the logs of a single transaction, and eth_blockNumber to discover the current head before paging.