List availability

The ID of an AppointmentType. If given, only scheduler availabilities for that type of appointment will be listed.

Some appointments might not have a type at all, so this boolean flag determines if scheduler availabilities for such appointments will be listed or not.

The date/time to display scheduler availabilities, in ISO format, including timezone information. See the request sample in curl displayed at the side. This queryParameter should be passed twice, to specify a date/time range. Example: ?date=>2022-08-10T09:49:47-07:00&date=<2022-09-09T23:59:59-03:00 Notice the greater-than (>) and less-than (<) operators.

Filter the availabilities by the ID of a Facility where the doctor/provider may be seen by a patient.

Only display the availability that was chosen by the patient who answered this form. If a form template with type pre-scheduling is set in the scheduler settings, then Luma's scheduler UI will require the patient to answer those form template questions, store the answers in a patientForm object, and then redirect them to another page listing the availabilities to be scheduled. Once the patient picks an availability and books an appointment, Luma will update the availability with the patientForm ID.

Filter scheduler availabilities that were booked after patients answered the questions of this template ID. The field patientForm will only bring one availability that was chosen by the patient who answered that form. This field will bring multiple availabilities, because it does not refer to the form answers of a single patient, but rather, to the form template. Multiple patients may have seen the questions of a template.

Only display scheduler availabilities for the ID of the provider/doctor given on this query parameter.

Filter availabilities by status. It must be available, as other statuses were already booked or canceled.

Determines which property will be used to order the response. Currently the only option available is date.

Determines the direction in which the sorting will happen:

• ascending (earliest date to latest), or
• descending (latest date to earliest).

The ID of the root account user.

Flag for logical deletion where 1 means deleted.

The ID of the user who created this object.

The ID of the user who updated this object.

The date/time when this object was created.

The date/time when this object was updated.

How many items to fetch per page

Response properties which will be replaced by the referenced objects, separated by commas.

Response properties that should be returned, separated by commas.