Skip to main content
POST
Delete calendar

Restrictions

Usage

  • If escalation rules or silence rules still use the calendar, the call returns HTTP 400 with error.code = ReferenceExist and data.refs listing them.
  • The calendar’s own events are deleted together with it.
  • Only personal calendars can be changed, and only by the account owner, an administrator, the calendar creator, or a member of the calendar’s team; other callers get AccessDenied.
  • 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 body carrying a calendar ID.

cal_id
string
required

Calendar ID; obtain it from POST /calendar/list.

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 body.