Spec

Frammenti di codice

curl "https://api.oanor.com/ens-api/v1/meta" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/ens-api/v1/meta", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/ens-api/v1/meta");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/ens-api/v1/meta",
    headers={"x-oanor-key": "oanor_test_..."}
)

Risposta di esempio

Una risposta reale di questo endpoint, acquisita dall'ultimo health check.

{
    "data": {
        "source": "Ethereum Name Service via public resolvers (ensdata.net + ensideas.com, live)",
        "service": "ens-api",
        "endpoints": {
            "GET /v1/meta": "This document.",
            "GET /v1/records": "Just the profile text records for a name (name=vitalik.eth).",
            "GET /v1/resolve": "An ENS name to its address + full profile (name=vitalik.eth).",
            "GET /v1/reverse": "An address to its primary ENS name + profile (address=0x…)."
        },
        "description": "Live Ethereum Name Service resolution: turn a .eth name into its wallet address and back, with the owner's on-chain profile. Resolve returns the address, avatar, content hash, resolver and every text record (Twitter, GitHub, Reddit, Discord, Telegram, email, website, description) plus multi-chain wallets. Reverse returns an address's primary ENS name and profile. Records returns just the profile records. Live, no key, nothing stored. Distinct from raw RPC and token APIs — this is ENS naming and profile data.",
        "upstream_status": "ok"
    },
    "meta": {
        "timestamp": "2026-06-09T11:39:55.224Z",
        "request_id": "d8659e47-866a-4586-ab4c-ba0951cdcf96"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}