https://api.us.nylas.com/v3/calendars/availabilityGet availability
Returns availability information for the specified user or group of users. All participants' email addresses must be associated with valid Nylas grants, and should be unique within their application.
bufferThe amount of buffer time Nylas adds around existing meetings, in minutes. For example, if an account has a meeting scheduled from 10:00–11:00a.m., and you set a buffer of 30 minutes, Nylas treats 9:30–11:30a.m. as busy.
beforeThe amount of buffer time to add before meetings, in increments of five minutes. For example,
if an account has a meeting scheduled from 10:00–11:00a.m., and you set a before buffer of
30 minutes, Nylas treats 9:30–11:00a.m. as busy.
This value must be between 0 and 120, and must be divisible by 5.
afterThe amount of buffer time to add after meetings, in increments of five minutes. For example, if
an account has a meeting scheduled from 10:00–11:00a.m., and you set an after buffer of 15
minutes, Nylas treats 10:00–11:15a.m. as busy.
This value must be between 0 and 120, and must be divisible by 5.
default_open_hoursA default set of open hours to apply to all participants. You can overwrite these open hours for
individual participants by specifying open_hours on the Participant object.
round_robin_group_idThe ID on events that Nylas considers when calculating the order of round-robin participants. This is used for both max-fairness and max-availability calculations.
To calculate participant order correctly, set the metadata key key5 to the same value on any
events you want to consider for the current set of round-robin participants. You can set this
key to any value that helps you identify events used to calculate availability in this group
(for example, new_subscriber_onboarding).
Scheduler Configurations don't use this setting. Scheduler ranks hosts from the Configuration's own bookings.
open_hoursAn array of the participant's open hours. Nylas searches for free time slots within these hours.