Spec

Frammenti di codice

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

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

$ch = curl_init("https://api.oanor.com/lightning-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/lightning-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": "mempool.space public Lightning API (live)",
        "service": "lightning-api",
        "endpoints": {
            "GET /v1/top": "Node league table (by=liquidity|connectivity, limit up to 100).",
            "GET /v1/meta": "This document.",
            "GET /v1/stats": "Network statistics: nodes, channels, total capacity (BTC), fees, clearnet/Tor split.",
            "GET /v1/search": "Find nodes by alias (q=bitfinex): public key, capacity, channels."
        },
        "description": "Live Bitcoin Lightning Network data from mempool.space: network statistics (node and channel counts, total capacity in BTC, average and median channel capacity, average fee rate, clearnet/Tor split); the node league table ranked by liquidity or connectivity; and node search by alias with public key, capacity and channel count. Live, no key, nothing stored. Distinct from on-chain Bitcoin and fee APIs — this is the Lightning Network layer.",
        "upstream_status": "ok"
    },
    "meta": {
        "timestamp": "2026-06-09T11:38:52.050Z",
        "request_id": "f0796a83-d325-43ab-8510-78daff6b2f5f"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}