Spec

Fragmentos de código

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

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

$ch = curl_init("https://api.oanor.com/sitemap-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/sitemap-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": {
        "note": "Fetch and parse an XML sitemap. /v1/parse?url=https://example.com/sitemap.xml fetches the sitemap (following redirects and transparently gunzipping .gz sitemaps) and returns its type — a urlset with every URL and its lastmod, changefreq and priority, or a sitemapindex listing the child sitemaps — with offset/limit paging. /v1/urls fetches a sitemap and, when it is an index, fetches its child sitemaps too and flattens every page URL into one list (with a configurable cap on URLs and child sitemaps, and a truncated flag). The request is made server-side; private/internal targets are refused (SSRF-guarded). Ideal for SEO audits, building crawl queues, content inventories and change monitoring. A sitemap fetcher/parser — distinct from generic XML-to-JSON conversion (xml), the robots.txt evaluator (robots) and the on-page SEO audit (seo). No key, no cache.",
        "spec": "sitemaps.org protocol (urlset + sitemapindex)",
        "endpoints": [
            "/v1/parse",
            "/v1/urls",
            "/v1/meta"
        ]
    },
    "meta": {
        "timestamp": "2026-06-01T23:40:40.051Z",
        "request_id": "3c4ed5ac-d7fd-4ed7-a078-ef7179b30c62"
    },
    "status": "ok",
    "message": "Meta retrieved",
    "success": true
}