On-call quickstart
By the end of this guide you’ll have a schedule called Primary on-call that hands off every Monday at 09:00 in your timezone, rotating between two engineers. You need at least two users in the account (invite teammates).
Rotations of more than one person need a responder pack. See plans and limits.
1. Create the schedule
Section titled “1. Create the schedule”-
Go to Respond → On-Call and click New schedule.
-
Name:
Primary on-call. Time zone: pick yours (defaults to UTC). Click Create schedule.
With an API key exported as SITEQWALITY_API_KEY:
curl -X POST https://api.siteqwality.com/on_call_schedule \ -H "Authorization: Bearer $SITEQWALITY_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "Primary on-call", "timezone": "America/Los_Angeles" }'Save the returned id as SCHEDULE_ID; you’ll attach a layer to it next.
2. Add a rotation layer
Section titled “2. Add a rotation layer”-
Open the schedule and click Add layer beside Layers.
-
Configure:
- Rotation type:
Weekly. - Handoff day:
Monday. - Handoff time:
09:00. - Participants: add Alice and Bob in the order you want them to rotate.
- Rotation type:
-
Click Add layer.
participants takes user IDs, which GET /account/info lists.
curl -X POST https://api.siteqwality.com/on_call_schedule/$SCHEDULE_ID/layer \ -H "Authorization: Bearer $SITEQWALITY_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "rotation_type": "weekly", "handoff_day": 1, "handoff_time": "09:00", "participants": [ "11111111-aaaa-4bbb-9ccc-dddddddddddd", "22222222-aaaa-4bbb-9ccc-eeeeeeeeeeee" ] }'handoff_day is 0=Sunday … 6=Saturday. handoff_time is HH:MM in 24-hour format, interpreted in the schedule’s timezone.
3. Confirm who’s on call right now
Section titled “3. Confirm who’s on call right now”Open the schedule. Its page shows who is on call now, until when, and who is next, then every shift of the next two weeks with any gap called out.
curl https://api.siteqwality.com/on_call_schedule/$SCHEDULE_ID/on_call \ -H "Authorization: Bearer $SITEQWALITY_API_KEY"The response names who is on call, when the shift started and ends, and the shift after it. Add ?at=2026-11-02T09:30:00Z to ask about another moment, or call /on_call_schedule/$SCHEDULE_ID/shifts for the next two weeks. See the reference.
4. Wire it into an escalation policy
Section titled “4. Wire it into an escalation policy”A schedule on its own doesn’t page anyone; an escalation policy has to target it. The escalation quickstart builds one whose first level pages Primary on-call.