Skip to main content
POST
Preview
🔑 Requires the schedules.view scope.

Authorizations

Authorization
string
header
required

API key from your incident.io dashboard (Settings → API keys)

Path Parameters

id
string
required

The ID of the schedule to preview entries for.

Example:

"01FDAG4SAP5TYPT98WGR2N7W91"

Body

application/json
schedule
object
required
Example:
entry_window_end
string<date-time>

The end of the window to preview entries for. Defaults to four weeks after entry_window_start.

Example:

"2021-01-08T00:00:00Z"

entry_window_start
string<date-time>

The start of the window to preview entries for. Defaults to now.

Example:

"2021-01-01T00:00:00Z"

Response

200 - application/json

OK response.

schedule_entries
object
required

The schedule entries for a window of time, grouped by where they come from.

scheduled are the entries produced by the schedule's rotation rules before any overrides are taken into account. overrides are the one-off changes that apply within the window. final is the effective schedule after overrides have been merged in — this is normally the list to use when working out who is on-call.

Example: