Skip to main content
POST
Create user availability schedule

Authorizations

Authorization
string
header
required

Use the Access Token generated with user type as Sub-Account (OR) Private Integration Token of Sub-Account.

Headers

Version
enum<string>
required

API Version

Available options:
2021-04-15

Body

application/json
timezone
string
required

Timezone for the schedule (IANA timezone identifier)

Pattern: ^[A-Za-z_]+/[A-Za-z_]+$
Example:

"America/New_York"

locationId
string
required

Location ID where this schedule applies

Example:

"IkqiJlXJ7o9h61tCHHod"

name
string
required

Human-readable name for the schedule

Example:

"Business Hours Schedule"

userId
string
required

User ID associated with the schedule

Example:

"IkqiJlXJ7o9h61tCHHod"

rules
object[]

Schedule rules defining when the schedule is active

Example:
calendarIds
string[]

Calendar IDs associated with the schedule

Example:

Response

Schedule created successfully

schedule
object
required
Last modified on March 8, 2026