Get Contract Logs

List contract logs from a contract on the network.

This method will use 120 Compute Units.

---

List contracts logs across many contracts on the network

Search the logs across many contracts with multiple contract calls. Chained logs are not included but can be found by calling /api/v1/contracts/{contractId}/results/{timestamp} or /api/v1/contracts/results/{transactionId}. When searching by topic a timestamp parameter must be supplied and span a time range of at most seven days.

Ordering

The order is governed by the combination of timestamp and index values. If the index param is omitted, the order is determined by the timestamp only.

Note: The default order for this API is currently DESC

Filtering

When filtering there are some restrictions enforced to ensure correctness and scalability.

The table below defines the restrictions and support for the endpoint

Query Param	Comparison Operator	Support	Description	Example
index	eq	Y	Single occurrence only. Requires the presence of timestamp	?index=X
	ne	N
	lt(e)	Y	Single occurrence only. Requires the presence of timestamp	?index=lte:X
	gt(e)	Y	Single occurrence only. Requires the presence of timestamp	?index=gte:X
timestamp	eq	Y	Single occurrence only.	?timestamp=Y
	ne	N
	lt(e)	Y	Single occurrence only. Optional second timestamp gt(e)	?timestamp=lte:Y
	gt(e)	Y	Single occurrence only. Optional second timestamp lt(e)	?timestamp=gte:Y

Both filters must be a single occurrence of gt(e) or lt(e) which provide a lower and or upper boundary for search.

get

/api/v1/contracts/results/logs

Query parameters

indexstring

Contract log index

Example: {"summary":"--","value":""}

Pattern: ^((eq|gt|gte|lt|lte):)?\d{1,10}$

limitinteger · int32 · min: 1 · max: 100 · default: 25

The maximum number of items to return

Example: 2

orderundefined · enum · default: desc

The order in which items are listed

Example: asc

Options: asc, desc

timestampstring[]

The consensus timestamp in seconds.nanoseconds format with an optional comparison operator

Example: {"summary":"--","value":""}

topic0string[]

The first topic associated with a contract log. Requires a timestamp range also be populated.

topic1string[]

The second topic associated with a contract log. Requires a timestamp range also be populated.

topic2string[]

The third topic associated with a contract log. Requires a timestamp range also be populated.

topic3string[]

The fourth topic associated with a contract log. Requires a timestamp range also be populated.

Responses

application/json

application/json

cURL

JavaScript

Python

HTTP

cURL

curl -L \
  --url 'https://mainnet.hedera.validationcloud.io/v1/YOUR_API_KEY/api/v1/contracts/results/logs'

200

400

200

{
  "logs": [
    {
      "address": "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
      "contract_id": "0.1.2",
      "data": "0x00000000000000000000000000000000000000000000000000000000000000fa",
      "index": 0,
      "topics": [
        "0xf4757a49b326036464bec6fe419a4ae38c8a02ce3e68bf0809674f6aab8ad300"
      ],
      "bloom": null,
      "block_hash": "0x553f9311833391c0a3b2f9ed64540a89f2190a511986cd94889f1c0cf7fa63e898b1c6730f14a61755d1fb4ca05fb073",
      "block_number": 10,
      "timestamp": "1586567700.453054000",
      "transaction_hash": "0x397022d1e5baeb89d0ab66e6bf602640610e6fb7e55d78638db861e2c6339aa9",
      "transaction_index": 1,
      "root_contract_id": null
    }
  ]
}

OK