HTTP API

eth_getLogs

Return logs for a filter object within the allowed request shape. The hosted route enforces a maximum explicit fromBlock/toBlock span of 10000 blocks.

Methodeth_getLogs

Route familyEVM

StageGeneral availability

Available under EVM HTTP API. Use the chain-family pages for route switching and the method pages for exact request and response shapes.

Access patterns

Pattern	Value	Notes
Compatibility URL (Recommended)	`POST /v1/{EVM_CHAIN}/{API_KEY}`	Public RPC onboarding uses one URL that already carries the API key. This fits mainstream wallets, RPC clients, and infrastructure tooling that expect one endpoint string.
Internal raw route	`POST /rpc/{EVM_CHAIN}`	The gateway rewrites compatibility URLs to internal raw RPC routes. This internal route is implementation detail, not the preferred public onboarding form.

Examples

Compatibility URL example


curl -X POST "{RPC_HTTP_BASE_URL}/v1/ethereum/<api_key>" \  -H "Content-Type: application/json" \  -d '{  "jsonrpc": "2.0",  "id": 1,  "method": "eth_getLogs",  "params": [  {    "fromBlock": "0x1",    "toBlock": "0x2710",    "address": "0x0000000000000000000000000000000000000001"  }]}'

Internal raw route example


curl -X POST "{RPC_HTTP_BASE_URL}/rpc/ethereum" \  -H "Authorization: Bearer <api_key>" \  -H "Content-Type: application/json" \  -d '{  "jsonrpc": "2.0",  "id": 1,  "method": "eth_getLogs",  "params": [  {    "fromBlock": "0x1",    "toBlock": "0x2710",    "address": "0x0000000000000000000000000000000000000001"  }]}'

This internal raw route example is secondary. Prefer the compatibility URL form for public integrations.

Response example


{  "jsonrpc": "2.0",  "id": 1,  "result": []}

Try send

Try eth_getLogs

Send one direct browser request to the current hosted gateway base URL so the real network request is visible in devtools. The API key is only stored locally when you provide one.

API key (used in endpoint URL)Request pathPOSTJSON body

Request fields

JSON-RPC request body

Field	Type	Required	Notes
`jsonrpc`	`string`	Required	JSON-RPC version. Use `2.0`.
`id`	`number \| string \| null`	Required	Client-supplied request identifier echoed back in the response.
`method`	`string`	Required	Method name. Use `eth_getLogs`.
`params[0].fromBlock / params[0].toBlock`	`hex quantity`	Required	When both are explicit block numbers, the current hosted route allows a maximum span of `10000` blocks.
`params[0].address`	`string \| string[]`	Required	Optional contract address filter.

Response fields

JSON-RPC response body

Field	Type	Notes
`jsonrpc`	`string`	JSON-RPC version.
`id`	`number \| string \| null`	Request identifier echoed from the request.
`result`	`array`	Returned log entries when the request succeeds.
`error`	`object`	Standard JSON-RPC error object. Oversized ranges return code `-32012` with message `eth_getLogs query exceeds max block range 10000`. Request correlation stays on HTTP headers such as `X-Trace-ID` and `X-Request-ID`.

EVM overview: Return to the chain-family landing page.
EVM HTTP API: Open the HTTP API tree for this chain family.
Use RPC: Return to the task-oriented raw RPC guide.
Canonical method path: Keep a direct link to this exact method page.