Appointments
Get Schedule Form Schema
Backend-driven descriptor for the schedule editor: fields, options, validation hints and current values
GET
The schedule editor is rendered from this descriptor — the frontend never
hardcodes day lists, location options or validation patterns. The
Validation hints in the schema are UX helpers only — the backend re-validates
everything on save (assigned location, overlaps, lunch-within-block).
schedule-blocks section is repeatable: fields defines one block row and
the UI renders N rows with add/remove.
Location options are restricted server-side to the doctor’s assigned locations.
When the doctor has a single location, the field arrives disabled: true with
that location preselected — the backend decides that rule, not the frontend.
Path Parameters
The doctor’s user ID
Response
es-CO or en-US — all labels arrive pre-localized.One repeatable
schedule-blocks section (repeatable: true, minItems: 1)
whose fields describe a block row: day (select, 7 localized options),
locationId (select, only assigned locations), startTime/endTime/
lunchStartTime/lunchEndTime (time fields with "HH:MM" validation hints).The doctor’s current schedule (same shape as Get Doctor Schedule), used to
populate the initial rows.
null when no schedule exists yet.