Calendar and iCal feeds

Not shipped yet. Tracked as API-012. Nothing on this page is callable today. It documents the planned contract so you can plan ahead.

JSON calendar (planned)

GET /v1/resources/{id}/calendar?from&to will return per-day availability status, a price hint, and restrictions — built on the same data as Availability. It will carry a strong ETag and a 60-second Cache-Control; send If-None-Match and expect 304 when nothing changed. Both sk_ and pk_ keys will be able to call it.

iCal feed (planned)

GET /v1/feeds/{token}.ics will export confirmed bookings and external OTA blocks as an iCal feed — busy/free only, no guest names or contact details. The {token} is a signed, per-resource, revocable feed token, not an API key — it’s meant to be pasted into an OTA’s “import a calendar” field and left there long-term. Your operator contact issues and can revoke this token independently of your API keys.

Once it ships

This page gets a real, runnable curl example and a sample .ics output — not a description of what one should look like.