Skip to main content
POST
Delete calendar event

Restrictions

Usage

  • Pass either event_id, or both start_at and end_at (dates in YYYY-MM-DD, covering [start_at, end_at)); any other combination returns InvalidParameter.
  • Cleared days fall back to the linked holiday calendars and the weekly workdays.
  • 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

Calendar event delete request. Provide event_id, or both start_at and end_at.

cal_id
string
required

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

event_id
string

ID of the event to delete. Omit when clearing a date range.

start_at
string

Start date of the range to clear, in YYYY-MM-DD. Pass together with end_at instead of event_id.

end_at
string

End date of the range to clear, in YYYY-MM-DD (exclusive). Must be later than start_at.

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.