About
Schedule and manage appointments, attach SMS reminders and linked contacts, and read or replace the key owner’s availability schedule. Enough for an integration or agent to book, reschedule, and cancel appointments and to drive the open slots the booking pages offer. All operations go through the developer API gateway — one endpoint, called byoperationId. If you haven’t set up a key yet, start with the
Developer API Overview.
Operations
Reading appointments and availability (READ scope)
Writing appointments and availability (WRITE scope)
Organization guardAny appointment, contact, or reminder id you pass is org-guarded — supplying a
foreign organization’s id returns
403 forbidden. This covers the appointmentId
on update/delete, contactIds/addContactIds, participant userIds/addUserIds,
and the appointmentReminderWorkflowGroupId. The availability operations
(getMyAvailabilitySchedule, setMyAvailabilitySchedule) take no entity id and
always act on your own schedule. See
Authorization for the model.