Skip to main content
Customers book a time (appointments, classes, consultations) or a date range (rentals, stays) on the site. Bookings are part of Solo, Studio and agency client workspaces and use no credits. The quickest path is the block, which works on hosted sites and, with the origin allowed, on sites hosted elsewhere:
The workspace also has a hosted booking page on its address.

Set up a service

Other fields: buffer_before_minutes, buffer_after_minutes, max_advance_days, cancellation_hours, min_nights / max_nights (for date_range), images, color. Opening hours and blocked dates are set in the admin (Customers → Bookings) or with set_availability on the hosted connector. Workspace-wide settings: GET/PATCH /v1/booking/settings.

Availability and booking (public, no key)

These endpoints are rate limited per IP (5 a minute). A slot taken in the meantime returns 409 slot_unavailable: refresh availability and let the customer pick again.

Manage bookings (API key)

Lifecycle: confirm, cancel, complete, no-show. Also GET /v1/bookings/calendar, GET /v1/bookings/stats, and an admin-side lookup GET /v1/availability?service_id=&from=&to=. Webhooks: booking.confirmed, booking.cancelled, booking.completed. Calendar export: each workspace has a private iCal feed (/v1/public/calendar/{token}.ics) for Google or Apple Calendar; find the link in the admin.

Reference