Skip to main content
GET
Doctor schedules are a central (clinic-wide) resource: no 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

doctorId
string
required
The doctor’s user ID

Response

doctorId
string
The doctor’s user ID.
workingDays
array
Schedule blocks. Each carries day, locationId, locationName (resolved server-side), startTime/endTime ("HH:MM" wall-clock), and optional lunchStartTime/lunchEndTime.
exceptions
array
ISO 8601 dates the doctor is unavailable — doctor-wide, they apply at every location.
Returns 404 NOT_FOUND when the doctor has no schedule configured yet (render an empty state, not an error).