Spec

Frammenti di codice

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

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

$ch = curl_init("https://api.oanor.com/linkheader-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/linkheader-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": "Link Header API",
        "notes": "Relations with multiple values are space-separated inside one rel (rel=\"next last\"). Pagination relations are next, prev/previous, first and last. This builds and parses the Link header string — it does not fetch a URL. Nothing is stored.",
        "version": "v1",
        "endpoints": [
            {
                "path": "/v1/parse",
                "params": {
                    "header": "a Link header value (required)"
                },
                "returns": "the parsed links and a rel→uri map"
            },
            {
                "path": "/v1/build",
                "params": {
                    "rel": "single link relation",
                    "uri": "single link URI (alternative to links)",
                    "links": "a JSON array of link objects ({uri, rel, title, …})",
                    "title/type/hreflang…": "optional target attributes for the single link"
                },
                "returns": "the Link header string"
            },
            {
                "path": "/v1/meta",
                "params": [],
                "returns": "this document"
            }
        ],
        "description": "Parse and build RFC 8288 HTTP Link headers (Web Linking). The parse endpoint turns a Link header into a structured list — each link with its URI, rel relation(s) and target attributes (title, type, hreflang, media…) — plus a handy rel→uri map so you can grab next, prev, first and last for pagination in one step. The build endpoint assembles a correct Link header from one or more link objects, quoting values where needed. It correctly handles multiple comma-separated links, quoted parameters, multiple space-separated rel tokens and angle-bracketed URIs. Pure local, no key."
    },
    "meta": {
        "timestamp": "2026-06-03T09:25:03.776Z",
        "request_id": "63fb8b88-575d-45aa-a01a-5d14dab91a6f"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}