Skip to main content
POST
Create Schedule

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

team_id
string
required

The ID of the team to create the schedule for.

Body

application/json
name
string
required

The name of the schedule.

timezone
string

IANA timezone identifier, e.g. "America/New_York". Defaults to "UTC" if not provided.

weeklyHours
weekly_hours · object

Weekly recurrence windows. Defaults to 09:00-17:00 Monday-Friday when omitted.

kind
enum<string> | null

ScheduleKind distinguishes a recurring weekly schedule's role.

Available options:
SCHEDULE_KIND_UNSPECIFIED,
SCHEDULE_KIND_WORK_HOURS,
SCHEDULE_KIND_BLACKOUT
respectedHolidayWindowIds
string[]

HOLIDAY windows owned by team_id that pause this schedule's SLA clock.

scopedId
string | null

Copy-invariant identity. Omit to have the server mint one.

Response

200 - application/json

Success

data
data · object

Schedule represents a recurring weekly time pattern. A WORK_HOURS schedule feeds the SLA clock (when it runs); a BLACKOUT schedule feeds the change-management conflict engine (when changes are blocked).