Calendar & Booking

Create or update a calendar. Without calendar_id = create (name required), with calendar_id = update.

All calendars of this project.

No input parameters required.

Delete a calendar including its events. Refused while resources are still attached.

Create or update an event. Without event_id = create (calendar_id, title, start_at, end_at required). Datetimes without an offset are read as UTC.

Delete an event.

Events that overlap the window [from, to), optionally per calendar.

Create or update a bookable resource (chair/table/room). Without resource_id = create (calendar_id, type, name required).

All resources of this project, optionally filtered.

Availability rules per resource.

Bookings of this project with filters and pagination.

Change the status of a booking (e.g. confirmed → completed or no_show).

Delete a resource including its availability. Refused while future pending/confirmed bookings exist; past bookings are kept.

Available slots (or nights for rooms) per resource. Give resource_id or type, plus date or from/to (max 31 days). Slots are returned in UTC and in local calendar time. Room nights closed by exceptions (closed:true) or vacations are returned with available:false. With block_on_events on the calendar, busy events are left out as well.

Book a resource. Tables/chairs: start_at + end_at (UTC). Rooms: checkin + checkout (YYYY-MM-DD, night granularity); a stay that includes a night closed by exceptions or vacations is refused. The claim is transactional, so a double booking is impossible. The response contains the cancel_token.

Cancel a booking via cancel_token (visitor) or booking_id (owner only). Idempotent; completed/no_show cannot be cancelled. The linked event is cancelled as well.

Read-only status of one booking by its cancel_token, e.g. to show a visitor whether their booking still stands or was moved or cancelled. Returns status, granularity, resource_name, start_at/end_at (UTC) plus start_local/end_local and timezone (slots) or checkin/checkout (rooms). No personal data. Changes nothing.

Public ICS feed URL of a calendar (the secret is generated on the first call). With rotate=true the secret is replaced and the old URL stops working immediately. Subscribe Apple/Google/Outlook to this URL.

Link an external ICS feed to this calendar (1 per calendar). Imported events get origin=ics and never change internal events or bookings. They only block booking times when the calendar has block_on_events with "ics" (upsert-calendar). url=null to unlink.

Run the ICS import for one calendar (calendar_id) or for all calendars of the project with an import feed. Upserts on UID, removes events that disappeared from the feed, skips RRULE in v1. Also suited to a scheduled task.

Project settings for the calendar (visitor booking caps, booking-email cap per recipient), which ones were changed, and the platform limits.

No input parameters required.

Change project settings; only the keys you send change, null resets a key to the platform default. Values must stay within the platform limits shown by get-config. Owner only, not available to visitors.