Explore documentation
  1. Welcome to Incidents 👋
  2. Frequently Asked Questions
  3. On-call scheduling and alerting
    1. Get started
    2. Slack and other integrations ↗
    3. Connecting external calendars
    4. Advanced guide
  4. Incident management
    1. Get started
    2. Post mortems
    3. Metadata & Catalog
    4. Screening alerts
    5. Reporting ↗
  5. Monitoring
    1. Get started
    2. Working with monitors
    3. Customizing monitors
    4. Monitor types
  6. Status pages
    1. Get started
    2. Advanced guide
  7. Incidents API
    1. Getting an API token
    2. Monitors
    3. Heartbeats
    4. On-call & incidents
      1. On-call schedule
      2. On-call schedule events
      3. On-call schedule rotations
        1. Get on-call schedule rotation GET
        2. Create on-call schedule rotation POST
        3. Remove on-call schedule rotation DELETE
      4. Escalation policies
      5. Escalation policy groups
      6. Severities
      7. Severity groups
      8. Incidents
      9. Comments
    5. Status pages
    6. Metadata
    7. Integrations
    8. Team members
    9. Organization roles
    10. Usage
    11. Reporting

Get an on-call schedule rotation

Returns the currently used on-call rotation for a single on-call schedule.

GET https://incidents.betterstack.com/api/v2/on-calls/{schedule_id}/rotation

URL parameters

schedule_id
required string

The ID of the on-call schedule you want to get events for. Use default to refer to the default on-call schedule for the team.

Query parameters

team_name
string

Required if using global API token to specify the team which owns the resource.

Headers

Authorization
required string

Bearer $TOKEN

200

Returns the on-call rotation if present. timezone is the time zone the rotation was configured with and is null when it was never set. effective_timezone is the time zone the rotation actually runs on. working_hours lists the windows during which the rotation pages anyone, ordered from Sunday, and is empty for a rotation that is active around the clock.

Response body

{
  "rotation_length": 1,
  "rotation_interval": "day",
  "start_rotations_at": "2026-02-02T00:00:00.000Z",
  "end_rotations_at": "2028-02-02T00:00:00.000Z",
  "users": [
    "bob@betterstack.com",
    "alice@betterstack.com"
  ],
  "timezone": "Europe/Prague",
  "effective_timezone": "Europe/Prague",
  "working_hours": [
    {
      "day": "monday",
      "start_time": "09:00",
      "end_time": "17:00"
    },
    {
      "day": "tuesday",
      "start_time": "09:00",
      "end_time": "17:00"
    },
    {
      "day": "wednesday",
      "start_time": "09:00",
      "end_time": "17:00"
    },
    {
      "day": "thursday",
      "start_time": "09:00",
      "end_time": "17:00"
    },
    {
      "day": "friday",
      "start_time": "09:00",
      "end_time": "17:00"
    }
  ]
}
404

Returns 404 when the on-call schedule doesn't have a rotation defined

Example cURL

Example
curl --request GET \
  --url "https://incidents.betterstack.com/api/v2/on-calls/default/rotation" \
  --header "Authorization: Bearer $TOKEN"


Previous article

Response attributes

Next article

Create an on-call schedule rotation