Service metadata

Frammenti di codice

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

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

$ch = curl_init("https://api.oanor.com/litecoinfees-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/litecoinfees-api/v1/meta",
    headers={"x-oanor-key": "oanor_test_..."}
)

Risposta di esempio

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

{
    "data": {
        "sample": {
            "mempool_tx": 820,
            "fastest_fee": 1
        },
        "source": "public Litecoin Space API (litecoinspace.org/api), keyless",
        "service": "litecoinfees-api",
        "endpoints": {
            "GET /v1/fees": "Recommended fee rates (litoshi/vB) and the current mempool size.",
            "GET /v1/meta": "This document.",
            "GET /v1/mining": "Mining-pool distribution over 1 week, with each pool's share and the network hashrate.",
            "GET /v1/difficulty": "Difficulty retarget window: progress, projected change, retarget date, blocks left."
        },
        "description": "Read Litecoin's fee market, difficulty cycle and mining-pool distribution live from the public Litecoin Space API: the recommended fee rates (litoshi/vB) and live mempool size, the difficulty adjustment (progress, projected change, retarget date, blocks remaining) and the mining-pool distribution with each pool's share and the network hashrate. The fee-and-mining layer for Litecoin wallets, miners and fee estimators. Live, short cache only.",
        "upstream_status": "ok"
    },
    "meta": {
        "timestamp": "2026-06-14T17:04:28.918Z",
        "request_id": "40da58a2-6cfa-4b91-b5e0-5edb07edcf6a"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}