Registry Domains
Run in ENSAdmin
Opens the hosted playground with this query pre-filled.
query RegistryDomains(
$registry: AccountIdInput!
) {
registry(by: { contract: $registry }) {
domains {
edges {
node {
label { interpreted }
name
}
}
}
}
} {
"registry": {
"chainId": 99911155111,
"address": "0x31a2bb5d933557cce1b3129993193896d074db92"
}
} {
"data": {
"registry": null
}
} # POST JSON to your ENSNode Omnigraph endpoint (same path enssdk uses).
curl -sS -X POST "https://api.v2-sepolia.ensnode.io/api/omnigraph" \
-H "Content-Type: application/json" \
-d @- <<'EOF'
{
"query": "query RegistryDomains( $registry: AccountIdInput! ) { registry(by: { contract: $registry }) { domains { edges { node { label { interpreted } name } } } } }",
"variables": {
"registry": {
"chainId": 99911155111,
"address": "0x31a2bb5d933557cce1b3129993193896d074db92"
}
}
}
EOF
ENS Omnigraph GraphQL
query RegistryDomains( $registry: AccountIdInput!) { registry(by: { contract: $registry }) { domains { edges { node { label { interpreted } name } } } }}Payload and transport examples
{ "registry": { "chainId": 99911155111, "address": "0x31a2bb5d933557cce1b3129993193896d074db92" }}
Response is an illustrative snapshot; live data depends on your ENSNode instance. The curl tab shows a POST to
https://api.v2-sepolia.ensnode.io/api/omnigraph