Spec & calendar links

Fragmentos de código

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

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

$ch = curl_init("https://api.oanor.com/ical-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/ical-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": "Build a valid RFC 5545 iCalendar event from simple parameters, or parse an .ics file back into structured events. /v1/event?title=Standup&start=2026-07-01T10:00:00Z&end=...&location=...&description=...&rrule=FREQ=WEEKLY returns the ready-to-serve .ics text (with proper escaping, 75-octet line folding, an optional VALARM reminder and RRULE recurrence), a base64 data: URI usable directly as a download link, and 'add to calendar' deep-links for Google, Outlook, Office 365 and Yahoo. Pass start/end as ISO 8601 or unix timestamps (UTC), or use duration (minutes) instead of end, or all_day for date-only events. /v1/parse turns raw .ics text (inline or in the body) back into JSON events. Everything is computed locally with no network calls. Ideal for booking and scheduling flows, event pages, email 'add to calendar' buttons, reminders and no-code automations. A calendar-event builder — distinct from date/time math (datetime), public-holiday data (holidays) and the Jewish calendar (hebcal). No key, no cache.",
        "spec": "RFC 5545 (iCalendar)",
        "endpoints": [
            "/v1/event",
            "/v1/parse",
            "/v1/meta"
        ],
        "calendar_links": [
            "google",
            "outlook",
            "office365",
            "yahoo"
        ]
    },
    "meta": {
        "timestamp": "2026-06-01T23:40:48.378Z",
        "request_id": "2579b11a-57a9-4a9e-8e61-00ca5f880bdb"
    },
    "status": "ok",
    "message": "Meta retrieved",
    "success": true
}