The appointments API lets you query, create, update, and delete clinic appointments. It also exposes time blocks — periods when a doctor is unavailable — which the booking engine uses when calculating available slots. All endpoints require a validDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/FerchoSG/healthcare-web/llms.txt
Use this file to discover all available pages before exploring further.
Authorization bearer token and x-clinic-id header scoped to the active clinic.
AppointmentStatus values
Appointments move through a defined lifecycle. The validstatus values are:
| Value | Description |
|---|---|
PENDING | Appointment has been created but not confirmed. |
CONFIRMED | Appointment confirmed by clinic staff. |
WAITING | Patient has arrived and is in the waiting room. |
IN_CONSULTATION | Patient is currently with the doctor. |
COMPLETED | Consultation is finished. |
CANCELLED | Appointment was cancelled. |
GET /appointments
Fetch appointments for a date range or a single date. Thex-clinic-id header scopes results to the active clinic.
Query parameters
Start of the date range in
YYYY-MM-DD format. Used together with endDate to fetch a range.End of the date range in
YYYY-MM-DD format. Used together with startDate.A single date in
YYYY-MM-DD format. When startDate equals endDate, the client sends date instead of the range pair.Appointment[]
UUID of the appointment.
UUID of the owning clinic.
UUID of the patient.
UUID of the doctor.
UUID of the booked service, or
null.ISO 8601 UTC start time.
ISO 8601 UTC end time.
Current
AppointmentStatus value.Patient-provided reason for the visit, or
null.Whether a reminder was sent to the patient.
ISO 8601 creation timestamp.
ISO 8601 last-updated timestamp.
POST /appointments
Create a new appointment. Request bodyUUID of the patient.
UUID of the doctor who will see the patient.
ISO 8601 UTC start time. Example:
2026-05-20T09:00:00Z.ISO 8601 UTC end time. Example:
2026-05-20T09:30:00Z.Optional free-text reason for the appointment.
Optional UUID of the service being booked.
Appointment
Returns the newly created appointment object. See the GET /appointments section for the full field list.
PATCH /appointments/:id/status
Update the status of an existing appointment. Use this endpoint to advance appointments through the lifecycle (e.g., fromCONFIRMED to WAITING).
Path parameters
UUID of the appointment to update.
New status value. Must be a valid
AppointmentStatus: PENDING, CONFIRMED, WAITING, IN_CONSULTATION, COMPLETED, or CANCELLED.Appointment
The updated appointment object.
PATCH /appointments/:id
Update appointment details such as the scheduled time or reason. Path parametersUUID of the appointment to update.
New ISO 8601 UTC start time.
New ISO 8601 UTC end time.
Updated reason for the appointment.
Updated appointment status.
Appointment
The updated appointment object.
DELETE /appointments/:id
Soft-delete an appointment. Returns HTTP 204 with no body on success. Path parametersUUID of the appointment to delete.
Time blocks
Time blocks mark periods when a doctor is unavailable. They are used by the booking engine to exclude those periods from available slots.GET /time-blocks
Fetch time blocks for a date range, optionally filtered by doctor. Query parametersStart of the range in
YYYY-MM-DD format.End of the range in
YYYY-MM-DD format.Filter results to a specific doctor UUID.
TimeBlock[]
UUID of the time block.
UUID of the doctor who is blocked.
UUID of the owning clinic.
ISO 8601 UTC start of the block.
ISO 8601 UTC end of the block.
Optional reason for the block.
ISO 8601 creation timestamp.
ISO 8601 last-updated timestamp.
POST /time-blocks
Create a new time block for a doctor. Request bodyUUID of the doctor to block.
ISO 8601 UTC start of the block.
ISO 8601 UTC end of the block.
Optional free-text reason for the block (e.g., “Congreso médico”).
TimeBlock
The newly created time block object.
DELETE /time-blocks/:id
Delete a time block. Returns HTTP 204 with no body on success. Path parametersUUID of the time block to delete.