Docs

Type a word or a question. Esc closes the search.

Sign in Start free

Delete an on-call rotation

Returns status 204 without a response body after deleting the selected rotation.

DELETE https://app.upfour.io/v1/oncall-schedules/{scheduleID}
DELETE https://app.upfour.io/v1/oncall-schedules/{scheduleID}
Authorization
AuthorizationA pls_ key. It stays in this browser tab. Needs oncall.write.
Path

Sent directly from your browser to https://app.upfour.io/v1. Mutating calls get an automatic Idempotency-Key when the field is empty.

Request
Responsenot sent yet
Fill in a key and press Send request (⌘↵).
The answer appears here.
scope oncall.write stable returns 204

Parameters

FieldTypeDescription
scheduleID required uuid path parameter

Returns

A successful request returns 204 with no response body.

Errors

Only the errors this operation can return. Every error uses the same envelope.

Status Code Meaning
400 bad_request The request is malformed or fails validation.
404 not_found The requested resource does not exist or is outside the caller's scope.
409 oncall_schedule_in_use The on-call rotation is still a target of an alert plan step, so it was not deleted. When: Deleting an on-call rotation that an alert plan step targets as oncall:<id>. details.alert_plans lists those plans. Fix: Remove the rotation from the steps of those alert plans first, then delete it.
403 permission_denied The credentials do not permit this action.

Every call can also return unauthorized (401), rate_limit_exceeded (429) or internal_error (500 / 502). See Responses and errors.