Skip to main content
POST
Delete schedules

Restrictions

Usage

  • A schedule still referenced by an escalation rule cannot be deleted: the call fails with HTTP 400 ReferenceExist, nothing is deleted, and data.refs lists the referencing rules (kind, name, href).
  • The caller must be able to edit every listed schedule: the account owner or an admin, the schedule’s creator, or a member of its team. Otherwise the call returns AccessDenied and nothing is deleted.
  • If the reference check cannot be completed, the call returns InternalError and nothing is deleted.
  • IDs that do not exist are ignored. The deletion of all listed schedules happens in one transaction.
  • Every call is recorded in the account audit log.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Request carrying a list of schedule IDs.

schedule_ids
integer<int64>[]
required

Schedule IDs to operate on; obtain them from POST /schedule/list. At most 100 items per request; split larger sets into several calls. Duplicates are ignored.

Maximum array length: 100

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object

Empty response.