# ENS Name On-Chain Events History

**Use case:** 

Recent on-chain events for ENS names — registrations, renewals, transfers and record updates — with transaction hashes and timestamps, alongside current owner and expiry. For auditors, researchers and DAOs reviewing a name's history before acquiring or relying on it. Replace queries with any .eth names and raise eventsLimit for a longer history.

## Input

```json
{
  "mode": "resolve",
  "queries": [
    "ens.eth",
    "uniswap.eth"
  ],
  "textRecords": [
    "avatar",
    "url",
    "email",
    "com.twitter",
    "com.github",
    "description"
  ],
  "coinTypes": [],
  "includeRegistration": true,
  "includeContenthash": false,
  "verifyReverse": true,
  "includeEvents": true,
  "eventsLimit": 20,
  "expiresWithinDays": 30,
  "lookupOwnedBy": true,
  "lookupResolvedTo": true,
  "onlyActive": true,
  "maxNamesPerQuery": 50,
  "fields": []
}
```

## Output

```json
{
  "query": {
    "label": "Query",
    "format": "string"
  },
  "name": {
    "label": "ENS name",
    "format": "string"
  },
  "address": {
    "label": "Address",
    "format": "string"
  },
  "isPrimaryName": {
    "label": "Is primary name",
    "format": "boolean"
  },
  "avatarUrl": {
    "label": "Avatar URL",
    "format": "string"
  },
  "twitter": {
    "label": "Twitter / X",
    "format": "string"
  },
  "github": {
    "label": "GitHub",
    "format": "string"
  },
  "url": {
    "label": "Website",
    "format": "string"
  },
  "flags": {
    "label": "Flags",
    "format": "array"
  },
  "completeness": {
    "label": "Profile completeness",
    "format": "number"
  }
}
```

## About this Actor

This example demonstrates how to use [ENS Resolver — Name to Address, Reverse Lookup, Avatar](https://apify.com/yadroo/ens-resolver.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/yadroo/ens-resolver.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/yadroo/ens-resolver.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).