nft

Historical Logs

Extracts detailed historical event logs for NFT collections within a specified block range on Ethereum. Designed to support different NFT standards (such as ERC721 and ERC1155), the endpoint returns granular log data—including event topics, parameters (like from, to, and tokenId), block details, and transaction identifiers—allowing developers and auditors to analyze the full history of NFT-related events, track transfers, and perform forensic or compliance analyses.

💡 Compute Unit Value: 100 (Fixed)

get/defi/v1/nft/historicallogs

Request

Base URL
https://svc.blockdaemon.com
URL
https://svc.blockdaemon.com/defi/v1/nft/historicallogs
Auth
API key in header X-API-Key

Query parameters

chainId'1'

The unique ID to direct queries or transactions to the correct blockchain. Find more here.

Example:1

chainSymbolstring

The abbreviated chain name for queries or transactions.

Example:ETH

nftCollectionstring required

The smart contract address of the NFT collection whose balance is to be retrieved.

Example:0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D

nftProtocolIdstring

Specifies the NFT standard to use for the query. Acceptable values are 721 for ERC-721 tokens and 1155 for ERC-1155 tokens. If not provided, the default value is 721

Example:721

startBlockstring

Specifies the starting block number for the event log query. If not provided, the default value is set to 100 blocks prior to the latest finalized block, ensuring a recent historical range is returned.

Example:100000

pagestring

Indicates the page number for paginated results. Defaults to '1' if no value is specified, allowing for easy navigation through large sets of log data.

Example:1

endBlockstring

Specifies the ending block number for the event log query. If omitted, the default is the latest finalized block, capturing all events up to the most recent block.

Example:100010

type'Approval' | 'Transfer' required

Defines the event type to retrieve. For example, for ERC721 collections, valid values include 'Approval' or 'Transfer'. This parameter is required to filter the logs based on the specific event type of interest.

Example:Approval

Response

Successful response

statusinteger

msgstring

dataobject

Example response

{
  "status": 200,
  "msg": "success",
  "data": {
    "logs": [
      {
        "address": "0x08d7c0242953446436f34b4c78fe9da38c73668d",
        "topics": [
          "0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
          "0x00000000000000000000000050d36f27872f637ec9ecb4eedff300df44a608ab",
          "0x000000000000000000000000fcbe7b6da18a08a86ab1beb68c7372a60ab4e331",
          "0x00000000000000000000000000000000000000000000000000000000000003d5"
        ],
        "params": {
          "from": "0x50d36f27872f637ec9ecb4eedff300df44a608ab",
          "to": "0xfcbe7b6da18a08a86ab1beb68c7372a60ab4e331",
          "tokenId": "981"
        },
        "data": "0x",
        "blockNumber": "17147007",
        "blockHash": "0x0af8cae4fce3cabdad9dbcac77ba4761afea961c040817ea835260ea6d56703a",
        "timeStamp": "1682713763",
        "gasPrice": "35684114147",
        "gasUsed": "267808",
        "logIndex": "250",
        "transactionHash": "0x0eb9b987533eee819a1509b5e50691438d0de6f9c43b46973fdd2516eccefd97",
        "transactionIndex": "98"
      }
    ]
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.