Spec

Frammenti di codice

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

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

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

Risposta di esempio

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

{
    "data": {
        "name": "CBOR API",
        "notes": "Encode emits definite-length items and float64 for non-integers; decode also accepts indefinite-length strings/arrays/maps and half/single floats. 64-bit integers beyond 2^53 decode to a decimal string. CBOR map keys that aren't text strings are stringified in the JSON output. Nothing is stored.",
        "version": "v1",
        "endpoints": [
            {
                "path": "/v1/encode",
                "params": {
                    "json": "a JSON value to encode (string)"
                },
                "returns": "the CBOR bytes as hex and base64, with byte length"
            },
            {
                "path": "/v1/decode",
                "params": {
                    "hex": "the CBOR bytes as hex",
                    "base64": "or as base64"
                },
                "returns": "the decoded JSON value"
            },
            {
                "path": "/v1/meta",
                "params": [],
                "returns": "this document"
            }
        ],
        "description": "Encode and decode CBOR (RFC 8949, Concise Binary Object Representation) — the IETF-standard binary data format behind COSE, WebAuthn/FIDO2, the EU Digital COVID Certificate, and many IoT and constrained-device protocols. The encode endpoint turns a JSON value into compact, definite-length CBOR, choosing the smallest head for each integer, string, array and map; the decode endpoint parses CBOR back into a JSON value. It implements the spec across all major types — unsigned and negative integers of every width, byte and text strings (including indefinite-length chunks), arrays, maps, tags, the simple values false/true/null, and half/single/double floats — and rejects trailing or truncated data. Byte strings and non-UTF-8 text come back losslessly as {\"_bytes_hex\":\"…\"}, tags as {\"_tag\":{\"tag\":N,\"value\":…}}, and other simple values as {\"_simple\":N}, so encode and decode round-trip exactly. Bytes are exchanged as hex and base64. Everything is computed locally and deterministically. Ideal for debugging CBOR/COSE/WebAuthn payloads, bridging JSON and CBOR systems, IoT pipelines, and teaching the format. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is CBOR specifically; for MessagePack use the MessagePack API, for BitTorrent's Bencode use the Bencode API, for JSON/YAML/TOML/XML use those format APIs, and for base64/hex/URL encoding use a general encoding API."
    },
    "meta": {
        "timestamp": "2026-06-03T17:42:17.368Z",
        "request_id": "60155e8e-ba2c-4053-8502-a2600ef84bbf"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}