Skip to main content

What a booking consumes besides a person

GET 
/api/resources

A room, a device, a vehicle, a seat — and a person. Naming one is what lets a booking hold it, and holding it is a database guarantee, not a check: two confirmed bookings can never carry the same resource_id over overlapping time. Cancelling frees it immediately; back-to-back appointments may share it.

kind: person is a PRACTITIONER: somebody the business schedules who usually has no login here at all. ?kind=person is the practitioner list, and there is deliberately no /api/practitioners beside this — two controllers writing one table would be two rule sets that drift.

Request​

Responses​

The resources.