Appointments
Get Doctor Schedule
The doctor’s full weekly schedule across all locations, with server-resolved location names
GET
Doctor schedules are a central (clinic-wide) resource: no
Returns
X-Location-Id
header is required, and the response covers every location the doctor works at.
Each schedule block carries a server-resolved locationName — the frontend
never maps location IDs to names.
A day may appear more than once (split shift): each block is an independent
day + location + time-range assignment.
Path Parameters
The doctor’s user ID
Response
The doctor’s user ID.
Schedule blocks. Each carries
day, locationId, locationName (resolved
server-side), startTime/endTime ("HH:MM" wall-clock), and optional
lunchStartTime/lunchEndTime.ISO 8601 dates the doctor is unavailable — doctor-wide, they apply at every location.
404 NOT_FOUND when the doctor has no schedule configured yet (render
an empty state, not an error).

