Skip to main content
PATCH
Update 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

id
string
required

Body

application/json
name
string | null
timezone
string | null
weeklyHours
WeeklyHours · object | null

WeeklyHours defines business hours for each day of the week. Each day may hold any number of non-overlapping windows; an empty day is closed.

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
respected_holiday_window_ids · object

Omit to preserve the current set; send an empty ids list to clear it.

scopedId
string | null

Rekeys the copy-invariant identity. Omit to preserve it.

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).