Create a package
/api/packagesAdds a catalog item: a set of prepaid visits covering one or more services. company_id comes from the verified JWT claim, never the body. Writes book_packages then book_package_services in two sequential statements (no RPC transaction); if the second write fails, the just-created package is deleted rather than left with no services on it. Appointments only, see migration 20260917130000's own header.
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
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/packages" \ -H "Content-Type: application/json" \ -d '{ "name": "string", "price": 0, "sessionsIncluded": 1, "serviceIds": [ "a486dd3f-c8ab-4226-b78c-e435f821cb91" ] }'{ "package": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08" }}Delete a product category DELETE
Never blocks and never takes products with it: the composite FK's column-scoped `on delete set null (category_id)` (0176) un-groups them in the same statement, same shape book_service_groups' own DELETE takes. **Appointments only**, see POST /api/products.
Update a package, or activate/deactivate it PATCH
Two shapes in one route, same posture PATCH /api/products/{id} takes. A body of exactly `{"active": true|false}` sets the flag and returns immediately. Any other body is a full replacement of the catalog fields (parsePackageInput's contract) followed by a delete-then-reinsert of book_package_services. RLS scopes the update, so an id from another org matches zero rows and returns 404. **Appointments only**, see POST /api/packages.