Docs / Inbox, calendar and Drive

Booking pages

A booking page lets people outside the workspace pick a free time with you, without an account: /book/{handle} lists your event types, each event type shows open times in the visitor's time zone, and a booking becomes an event in your calendar with the visitor as a guest. Both of you get an email. It is part of the calendar, so it is available wherever the inbox is.

In the dashboard and the Mac app: Calendar → Booking page.

Your page

MethodPathPurpose
GET, PUT/v1/booking/profile{ "handle": "olive", "displayName": "Olive Host", "intro": "…", "timeZone": "Europe/Berlin", "enabled": true }.
GET, POST/v1/booking/event-typesList, add (at most 50).
GET, PATCH, DELETE/v1/booking/event-types/{id}Read, change, delete (bookings already made stay in your calendar).
GET/v1/booking/event-types/{id}/slots?from=…&to=…&duration=…The open slots as visitors see them (at most 62 days).
GET/v1/booking/bookings?status=confirmed&from=…&to=…Your bookings (confirmed, canceled, all).
POST/v1/booking/bookings/{id}/cancel{ "reason": "…" }: frees the time, removes the event, and sends the visitor a cancellation.

The handle is the page's address: 3 to 40 lowercase letters, digits and single hyphens, unique on the server (409 handle_taken; some words such as admin or manage are reserved). A page belongs to one member; it stops taking bookings when they leave the workspace.

An event type:

FieldMeaning
name, slug, description/book/{handle}/{slug}.
durationsLengths a visitor can choose, in minutes (multiples of 5, up to 12 hours, at most 6).
location{ "kind": "video", "value": "https://meet.example/olive" }; kinds in_person, phone, video, custom. A video link becomes the event's link.
availability{ "timeZone": "Europe/Berlin", "weekly": { "mon": [["09:00", "12:00"], ["13:00", "17:00"]], … }, "overrides": [{ "date": "2026-12-24", "hours": [] }] }. Weekly hours are wall-clock hours in the zone (default: the page's), so they stay put across daylight saving changes; an override replaces a date's hours (empty: closed).
bufferBefore, bufferAfterMinutes kept free around each booking (at most 240).
minNoticeMinutes from now before the first bookable start (default 120).
maxDaysAheadDays ahead that can be booked (1 to 730).
dailyLimitMost bookings of this type a day (in the availability's zone). Held like the slots: each booking takes one of the day's dailyLimit rows in booking_locks, so bookings made at the same moment cannot pass it.
slotIntervalMinutes between slot starts (default: the duration).
questionsUp to 10 { "id", "label", "required", "multiline" }. Name and email are always asked.
busyCalendarIdsCalendars whose busy events block slots (default: your personal calendar). Only calendars you can read; free and canceled events, and invitations you declined, do not count.
targetCalendarIdThe calendar bookings go into (default: your personal calendar). It always counts as busy.

The public pages

PathPurpose
GET /book/{handle}The page: your event types.
GET /book/{handle}/{slug}?tz=…&from=YYYY-MM-DD&d=…A week of open times in the visitor's zone (tz; a small script fills it in from the browser, and there is a time zone menu), for duration d.
GET /book/{handle}/{slug}?slot=…The form for one time.
POST /book/{handle}/{slug}Book (the HTML form).
GET /book/{handle}/{slug}/slots?from=…&to=…&tz=…&d=…JSON: { "slots": ["2026-11-18T08:00:00.000Z", …], "timeZone", "duration" }.
POST /book/{handle}/{slug}/bookJSON: { "start", "duration", "name", "email", "answers": { "topic": "…" }, "timeZone" } → { "ok": true, "status": "confirmed", "start", "end" }; 409 slot_taken, 400 invalid_booking (details.field), 429 rate_limited or too_many_bookings.
GET /book/manage/{token}, POST /book/manage/{token}/cancelReschedule or cancel from the link in the confirmation.

The pages follow the signup forms' rules (The hosted page): server-rendered and usable without JavaScript (one inline script, allowed by its hash, only fills in the time zone), a strict content security policy (default-src 'none', forms post only to this server, never framed), X-Robots-Tag: noindex, Cache-Control: no-store, Referrer-Policy: no-referrer, every value escaped, light and dark.

Only open times are shown: never what makes a time busy (titles, places or that an event exists). An unknown handle, a page that is turned off, an unknown or disabled event type, a host who left the workspace, and a workspace being deleted or suspended all show the same 404 page, so handles cannot be probed.

What a booking does

  1. Checked again. The time must still be open for its day: busy calendars, other bookings with their buffers, notice, days ahead, the daily limit. Otherwise 409 slot_taken. Reading the host's calendars is bounded (repeating events: see Repeating events).
  2. No double booking. The booking first inserts the 5-minute slots it covers, buffers included, into booking_locks, whose primary key is host + slot: two bookings that overlap anywhere, made at the same moment on any number of servers, cannot both get their slots. Its row also has a unique active_key (host + start). If either insert fails, what it inserted is removed and the visitor gets 409 slot_taken. Canceling frees the slots.
  3. The event. An event in the target calendar (source: booking, bookingId) titled with the event type and both names, with the visitor as a guest who accepted, the answers in its notes, and the location.
  4. The emails. The visitor gets the invitation (invite.ics, METHOD:REQUEST) from your address (as for any invitation) with a link to reschedule or cancel; without an address to send from, a plain confirmation from the workspace's system address. You get a notice. The visitor's mail carries nothing they typed (see Abuse protection).

Reschedule and cancel links carry a signed token (purpose booking_manage, the booking and workspace) valid until a day after the booking's start (at most 400 days). Rescheduling picks a new time on the same event type and keeps the booking's name and address (the form does not ask for them; a name or email sent anyway is ignored); the new booking takes over the slots the old one held that it still needs, then the old one is canceled, so moving by 15 minutes works. Canceling tells you by email and sends the visitor a cancellation.

Abuse protection

No third-party CAPTCHA (OneSend has no CAPTCHA integration to hook into). Instead:

  • Honeypot. A hidden website field; a booking that fills it gets the normal confirmation and books nothing.
  • Time to submit. The form carries a signed render time (booking_form); a form posted within 2 seconds, or without it, gets the normal confirmation and books nothing.
  • Rate limits. Bookings: 5 per client address, then one every 2 minutes, and 30 per page, then 30 an hour. Pages and slot lookups: 120 per client address, then 2 a second. Reschedule and cancel posts: 20 per address, then one every 30 seconds. Behind a reverse proxy, set ONESEND_TRUST_PROXY.
  • Per email address. At most 3 bookings per address and day in a workspace (429 too_many_bookings); a reschedule is a new booking and counts.
  • Nothing the visitor typed goes to the visitor. Anyone can fill in the form with someone else's address, so the page could otherwise relay text through your mailbox. The invitation to the visitor is titled with the event type and your name (Intro call with Olive Host), and has no notes, answers or guest names (in the message and in invite.ics); the cancellation the same. Their name and answers go only to you: the event in your calendar and your notice. (Confirming the visitor's address before anything is sent was considered: it would delay every booking and still mail the address once; with nothing they typed in it, that mail carries only your own text.)
  • Per workspace. At most ONESEND_BOOKING_DAILY_EMAILS booking mails (default 500: invitations, notices, cancellations; counted in the database) a workspace sends a day. Past it the pages take no more bookings that day (429 too_many_bookings), and cancellations go without their emails.
  • Input limits. Name 200 characters, email 254, answers 2,000 each; the client address is stored only as a keyed hash (ip_hash).

Data

Tables (migration 0045): booking_profiles, booking_event_types, bookings, booking_locks. Every row has workspace_id (purged with the workspace). The workspace export includes profiles, event types and bookings, except bookings into a personal calendar (like the calendar's events); booking_locks is not exported (derived from bookings) and is pruned two days after the slots pass (maintenance job).

A booking costs a bounded number of database statements (well under 250, also on Cloudflare D1's 1,000 per invocation): the page and event type, the rate limits, the checks for the day, the slot locks (one multi-row insert), the daily-limit row, the booking, the event and the queued emails. booking_locks rows of the daily limit (<date>T~day:<type>:<n>) are pruned with the slots.