API Reference

Create custom trigger schedule

post
https://example.com/config-triggers/v1/trigger-schedules

weekDays selectedHours are integers 0-23 - not the IncidentScheduleHour enum names that the Add-CUTriggerSchedule cmdlet takes. Days with no hours are omitted. The schedule name must differ from every built-in and custom schedule name. Concurrent creates with the same name are not serialized upstream, so automation should not issue them in parallel.

Body Params

The schedule to create.

Request body for creating a custom trigger schedule. Server-set fields (scheduleId, source, inUseByCount) are ignored if sent.

string | null

Gets or sets the schedule name: 1-200 characters, no control characters, unique among built-in and custom schedules.

weekDays
array of objects | null

Gets or sets the week definition: up to 7 days, each day at most once, at least one day with at least one hour.

weekDays
Headers
string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Responses

Updated 19 days ago

Did this page help you?
Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 19 days ago

Did this page help you?