Contract creation and deployer

Get the creation record of a contract: deployer address, creation transaction, block and timestamp.

GEThttps://triport.io/v1/intelligence/eth/0xdac17f958d2ee523a2206206994597c13d831ec7/creation

Network: Ethereum
Scope: intelligence:read
Auth: x-token: $TRIPORT_API_KEY header (or Authorization: Bearer)
Rate limit: Business — 30 rps (intelligence, burst ×2); Enterprise — 150 rps

Request

cURLJavaScriptPython

curl "https://triport.io/v1/intelligence/eth/0xdac17f958d2ee523a2206206994597c13d831ec7/creation" \
  -H "x-token: $TRIPORT_API_KEY"

const res = await fetch("https://triport.io/v1/intelligence/eth/0xdac17f958d2ee523a2206206994597c13d831ec7/creation", {
  method: "GET",
  headers: {
    "x-token": process.env.TRIPORT_API_KEY,
  },
});
const data = await res.json();
console.log(data);

import os


import requests


resp = requests.get(
    "https://triport.io/v1/intelligence/eth/0xdac17f958d2ee523a2206206994597c13d831ec7/creation",
    headers={
        "x-token": os.environ["TRIPORT_API_KEY"],
    },
)
data = resp.json()
print(data)

Response

JSON

Example

{
  "state": "ok",
  "meta": {
    "observedAt": "2026-11-06T09:20:56.695726381Z",
    "expiresAt": "2026-11-07T09:20:56.695726381Z",
    "cached": true,
    "complete": false
  },
  "data": {
    "chain": "eth",
    "address": "0xdac17f958d2ee523a2206206994597c13d831ec7",
    "creation": {
      "kind": "deployment_or_first_appearance",
      "blockNumber": "4634748",
      "timestamp": {
        "value": "1511829681000",
        "unit": "milliseconds"
      },
      "index": "64",
      "txHash": "0x2f1c5c2b44f771e942a8506148e256f94f1a464babc938ae0690c6e34cd79190",
      "from": "0x36928500bc1dcd7af6a2b4008875cc336b927d57"
    }
  }
}

Get the creation record of a contract: deployer address, creation transaction, block and timestamp.

Block number, index and timestamp are strings; the timestamp is in milliseconds. creation.kind qualifies the record (the example shows deployment_or_first_appearance): it is not always a contract deployment, and it is not the same as a full deployer scan.

Released on Ethereum. Any other chain value answers 422 with state unsupported. More chains are coming; see the changelog.

Every answer is an envelope with state, meta, optional data and optional error. Read state first: ok, empty, partial, stale, unsupported or unavailable (see response states). meta.cached tells you whether the answer came from cache.

Parameters

chainstringrequired

Path segment. Chain id, see Network above (eth, and for labels also solana and avalanche). Aliases: ethereum → eth, sol → solana, avax → avalanche.

addressstringrequired

Path segment. Address to look up: 0x + 40 hex characters, any letter case.

fresh0 or 1optional

Query parameter. 1 skips the cache and asks for a new lookup.

Response

Response recorded on 2026-11-06 through https://triport.io (long lists shortened). Values change over time.

Errors

HTTP	`error.code`	When
400	`invalid_request`	Malformed address, unknown field, `null` value or invalid JSON.
401	`unauthorized`	Missing or invalid API key.
403	`scope_missing` / `tier_insufficient`	The key lacks `intelligence:read`, or the plan is below Business.
405	`method_not_allowed`	Wrong HTTP method; the `Allow` header names `GET`.
422	`unsupported`	The chain (or the contract) is not supported by this method.
429	`rate_limited`	Over the `intelligence` per-second limit; wait `Retry-After` seconds.
503	`unavailable`	The lookup could not be completed right now; retry later.
504	`timeout`	The lookup took too long; retry, or retry later with the same input.

See errors, limits and states for the full rules and the code examples.