Account Resolver Permissions
Resolver contracts where an account has been granted resolver ACLs.
Run in ENSAdmin
Open an interactive playground to execute this query on our sepolia-v2
ENSNode instance.
query AccountResolverPermissions($address: Address!) {
account(by: { address: $address }) {
resolverPermissions {
edges {
node {
resolver {
contract {
address
}
}
}
}
}
}
} {
"address": "0x205d2686da3bf33f64c17f21462c51b5ead462cf"
} {
"data": {
"account": {
"resolverPermissions": {
"edges": [
{
"node": {
"resolver": {
"contract": {
"address": "0x5f35454af804f1131d6c1261c55b77308be5a11c"
}
}
}
}
]
}
}
}
} # 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 AccountResolverPermissions($address: Address!) { account(by: { address: $address }) { resolverPermissions { edges { node { resolver { contract { address } } } } } } }",
"variables": {
"address": "0x205d2686da3bf33f64c17f21462c51b5ead462cf"
}
}
EOF
ENS Omnigraph GraphQL
query AccountResolverPermissions($address: Address!) { account(by: { address: $address }) { resolverPermissions { edges { node { resolver { contract { address } } } } } }}Payload and transport examples
{ "address": "0x205d2686da3bf33f64c17f21462c51b5ead462cf"}
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