Service metadata & endpoints

Fragmentos de código

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

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

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

Respuesta de ejemplo

Una respuesta real de este endpoint, capturada en la última comprobación de estado.

{
    "data": {
        "source": "public Solana RPC (getTransaction jsonParsed / getSignatureStatuses), keyless",
        "service": "solanatx-api",
        "endpoints": {
            "GET /v1/tx": "Full decoded transaction: status, fee, instructions, logs, balance changes (signature=...).",
            "GET /v1/meta": "This document.",
            "GET /v1/status": "Fast confirmation status of a signature (signature=...).",
            "GET /v1/transfers": "Just the value moved: SOL + SPL-token balance changes (signature=...)."
        },
        "description": "Decode any Solana transaction by signature, live from public Solana RPC: fee, fee payer, success/error, slot, block time, compute units, parsed instructions, program log, and the decoded SOL and SPL-token balance changes. A transfers endpoint extracts just the money movements; a status endpoint gives a fast confirmation check. The transaction-decoding layer for Solana wallets, explorers and payment processors. Live, short cache only."
    },
    "meta": {
        "timestamp": "2026-06-14T08:04:08.087Z",
        "request_id": "f7a763ff-2663-474f-a674-19c27d1bcd70"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}