Read one repeat series and its visits
/api/booking-series/{id}The series row plus every book_appointments row it generated, in date order, each with its OWN current status, not just the ones still upcoming. What the "End series" confirm step (BookingDetailDialog) reads to say how many visits are actually about to be cancelled, versus already past or already cancelled individually; that distinction needs the full list, not a second round trip filtered ahead of time.
Authorization
sessionCookie The dashboard's Supabase Auth session cookie, set at sign-in. Large sessions are split across
numbered chunks (…auth-token.0, .1), so treat this as a cookie family rather than one name.
Every request re-validates it against the Auth server (getUser()), never by decoding the cookie
locally: a JWT nothing has checked is not a credential. Tenancy is then read from the verified
app_metadata.company_id claim and enforced by row-level security; it is never read from request
input, on any route, ever.
role (admin / staff) is deliberately not in RLS. It gates specific actions in route code,
the operations marked admin below, so hiding a button in the UI is cosmetic only, and a route's
own check is the enforcement.
In: cookie
Path Parameters
book_booking_series id.
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/booking-series/string"{ "series": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "status": "active" }, "visits": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "starts_at": "2019-08-24T14:15:22Z", "status": "pending" } ]}Whether this booking is part of a repeat series GET
One id in, one (possibly null) id out. Its own tiny route rather than folding `seriesId` into GET /api/appointments/{id}'s already-large select: `series_id` (migration 0149) is a brand-new column, and the same "isolated, tolerated read" a brand-new column always gets here (see loadCardOnFileForBooking in lib/billing/checkout.ts for the precedent): folding it into a shared select would 42703 the WHOLE row for every booking on screen the moment this column isn't confirmed live yet, not just this one field. What BookingDetailDialog fetches once on open to decide whether to offer "End series" at all.
End a series early PATCH
"End a series early from any of its visits: the rest cancel in one go and the customer hears once" (the shipped spec this follows). Only `{"status":"cancelled"}` is accepted: there is no other transition a series makes. Cancels every visit in the series that is both in the future AND not already `cancelled`/`completed`; a visit that already happened, or was cancelled individually by the guest or staff before this ran, is left exactly as it was rather than double-touched. `book_booking_series.status` flips to `cancelled` in the same action, which is what refuses a second call on an already-ended series with 409. One `series_cancelled` notification job is queued for the whole batch, not one per visit.