List who is currently on-call, with support for filtering by escalation policy, schedule, and user. Returns on-call entries grouped by escalation policy level.
curl --request GET \
--url https://api.rootly.com/v1/oncalls \
--header 'Authorization: Bearer <token>'{
"errors": [
{
"title": "<string>",
"status": "<string>",
"code": "<string>",
"detail": "<string>"
}
]
}Documentation Index
Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
comma separated if needed. eg: user,schedule
user, schedule, escalation_policy Start of time range in ISO-8601 format (e.g., 2025-01-01T00:00:00Z). Defaults to current time.
End of time range in ISO-8601 format (e.g., 2025-01-01T00:00:00Z). Defaults to 'since' time.
When true, returns only the first on-call user per escalation policy level
Timezone for response times (e.g., America/New_York). Defaults to UTC.
Comma-separated escalation policy IDs
Comma-separated schedule IDs
Comma-separated user IDs
Comma-separated service IDs
Comma-separated group IDs (teams)
Comma-separated notification types to include. One or both of: audible, quiet. When present, oncalls are returned from every non-deferral escalation path whose notification_type is in the filter, sorted audible-first. When absent, only the default path's oncalls are returned (existing behavior).
success
Was this page helpful?
curl --request GET \
--url https://api.rootly.com/v1/oncalls \
--header 'Authorization: Bearer <token>'{
"errors": [
{
"title": "<string>",
"status": "<string>",
"code": "<string>",
"detail": "<string>"
}
]
}