Are ENS Names supported by the qn_fetchNFTsByCollection endpoint?

Hello! I’m new to qucknode coming from alchemy. the main reason being that their nft endpoints didnt support ENS names properly (not a complaint… ENS is a weird NFT). My question is whether the endpoint qn_fetchNFTsByCollection handles ENS, contract address 0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85
using this code:

import requests
import json

url = "<api-key>/"

payload = json.dumps({
  "id": 67,
  "jsonrpc": "2.0",
  "method": "qn_fetchNFTsByCollection",
  "params": [{
    "collection": "0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85",
    "omitFields": [
    "page": 1,
    "perPage": 10
headers = {
  'Content-Type': 'application/json'

response = requests.request("POST", url, headers=headers, data=payload)

data = response.json()

print(json.dumps(data, indent=2))

i get these objects as responses:

        "collectionName": "ENS: Ethereum Name Service",
        "collectionAddress": "0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85",
        "collectionTokenId": "373693751495179816022478081374443916959044675629285851815308898302858417637",
        "description": "",
        "name": "dccclxxv.eth",
        "imageUrl": "",
        "traits": [],
        "chain": "ETH",
        "network": "MAINNET"

The question/issue is that I would expect the expiration date to be in the traits array. Anyone from quicknode know whether there is a way to get those traits populated, or if ENS is supported on this endpoint?



Hey Mark :wave: ,

As of now we have some limited support for ENS domains, but we don’t currently have the expiration date.


Thanks! Ill keep looking around then.

Take care,


1 Like