Cal.com

Writes

• Create booking

  read back

  calcom-create-booking

  Book one meeting of an event type for one attendee, at a start time from find-available-slots. Cal.com emails the attendee and the host and adds it to the host's calendar. An event type that needs confirmation creates the booking as pending.

• Reschedule booking

  read back

  calcom-reschedule-booking

  Move one accepted or pending booking to a new start time. Cal.com cancels the old booking, creates a new one with a new uid, and emails the attendees. A pending booking stays pending.

• Cancel booking

  read back

  calcom-cancel-booking

  Cancel one booking. Cal.com emails the attendees and the host and removes it from the calendar.

• Confirm booking

  read back

  calcom-confirm-booking

  Confirm one pending booking of an event type that needs the host's confirmation. Cal.com emails the attendee that it is confirmed.

• Decline booking

  read back

  calcom-decline-booking

  Decline one pending booking of an event type that needs the host's confirmation. Cal.com emails the attendee, with the reason when given.

• Mark attendee absent

  read back

  calcom-mark-attendee-absent

  Mark one attendee of a past booking as a no-show. This can start the event type's no-show workflows.

• Mark host absent

  read back

  calcom-mark-host-absent

  Mark the host of a past booking as a no-show.

• Add guest

  read back

  calcom-add-guest

  Add one guest to an existing booking. Cal.com emails the guest an invitation and updates the calendar event.

Reads

• Get me

  calcom-get-me

  Get the Cal.com user the key belongs to: id, username, email, name, time zone and defaultScheduleId. Bookings and event types are read as this user.

• List event types

  calcom-list-event-types

  List event types, the kinds of meeting that can be booked: id, title, slug, length in minutes, locations, booking fields and booking URL. Without a username it lists the key owner's own event types, hidden ones included. With a username it lists that user's public event types. Cal.com returns them all at once, with no page cursor; an account with very many event types can be cut at 64 KB, so then read one with get-event-type.

• Get event type

  calcom-get-event-type

  Get one event type: title, slug, length and the lengths a booker may choose, locations, booking fields (including any required custom fields), confirmation policy, recurrence, seats and booking URL.

• Find available slots

  calcom-find-available-slots

  Find the free times for one event type between two dates, grouped by date, each with a start and an end. Ask for a week or less at a time so the answer stays small. Times come back in time_zone (UTC when left out). Pass booking_uid_to_reschedule when looking for a new time for an existing booking, so its own time counts as free.

• List schedules

  calcom-list-schedules

  List the key owner's availability schedules: id, name, time zone, weekly hours, date overrides and which one is the default.

• Get schedule

  calcom-get-schedule

  Get one availability schedule: name, time zone, weekly hours (days with a start and end time), date overrides and whether it is the default. The default schedule's id is defaultScheduleId from get-me.

• List bookings

  calcom-list-bookings

  List the key owner's bookings, 20 per page: uid, title, status, start and end, event type, location, hosts and attendees. Filter by status (one at a time), attendee email or name, event type, or a time range. Cal.com returns pagination.nextCursor while pagination.hasMore is true; pass it as cursor for the next page.

• Get booking

  calcom-get-booking

  Get one booking by uid: title, description, status (accepted, pending, cancelled, rejected), start, end, duration, event type, location or meeting link, hosts, attendees with their absent flag, guests, cancellation or rescheduling reason, and the uid it was rescheduled from or to. A recurring booking's own uid returns every occurrence as a list.

• List booking attendees

  calcom-list-booking-attendees

  List the attendees of one booking, guests included: id, name, email, time zone, language, phone number and whether they were marked absent.