Service metadata & live sample

Frammenti di codice

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

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

$ch = curl_init("https://api.oanor.com/nearview-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/nearview-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": {
            "symbol": "USDt",
            "decimals": 6
        },
        "source": "public NEAR JSON-RPC (query / call_function), keyless",
        "service": "nearview-api",
        "endpoints": {
            "GET /v1/meta": "This document.",
            "GET /v1/view": "Call any contract view method (contract=..., method=ft_metadata, args={...}).",
            "GET /v1/token": "NEP-141 token metadata + total supply (contract=usdt.tether-token.near).",
            "GET /v1/balance": "An account's NEP-141 token balance (contract, account)."
        },
        "description": "Execute read-only contract view methods on NEAR via public NEAR RPC — NEAR's equivalent of eth_call. Call any contract's view method with JSON args, or use the convenience endpoints for NEP-141 token metadata + total supply and an account's token balance. The on-chain read layer for NEAR wallets, dashboards and bots. Live, short cache only.",
        "upstream_status": "ok"
    },
    "meta": {
        "timestamp": "2026-06-14T08:04:00.269Z",
        "request_id": "2e097026-fa05-43fa-83f3-567818974bb3"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}