Delete event type — Calendar

Delete an event type only when no bookings reference it.

Action: app_topolo_calendar.event_types.delete · DELETE /api/admin/event-types/{eventTypeId}

Declared permission: app_topolo_calendar.event_types:write. For authorized Calendar users; permissions and resource access still apply.

Before you start

• Use the current credential to confirm the production organization and inspect this exact action before preparing a call.
• Declared permission: app_topolo_calendar.event_types:write. Permission discovery is not a grant.
• Discover the authorized Calendar workspace and pass it as resourceType=workspace/resourceId separately from this action input. Calendar records and IDs are scoped to the selected host/workspace.
• Validate and plan the exact payload, obtain effect-specific authorization, then execute unchanged only in a separately authorized operational task. Do not run these synthetic inputs.

Inputs and field meanings

Worked request and response

Source-reviewed illustration only. Nothing below was executed; all identifiers, counts, states, credentials and URLs are synthetic. Replace identifiers through discovery before any separately authorized call.

Resource context: workspace; it is not an extra action input field.

Illustrative action input:

{
  "eventTypeId": "evt_example"
}

Illustrative HTTP 200 source response:

{
  "ok": true
}

ok is the source delete acknowledgement. Confirm the type cannot be read/listed afterward. An in-use refusal preserves booking history and must not be bypassed.

The illustrative response passes the declared structural schema. This establishes only schema compatibility, not deployed shape, values, authorization or business outcome.

Effects and verification

• Hard-deletes the host-owned type and clears its transient slot holds after the booking-count guard.

1. Read event_types.list/get to confirm absence and retain the refusal if event_type_in_use is returned.

Refusals and recovery

Selected source refusals are listed below; runtime middleware can return additional structured errors.

Recovery: There is no undelete action. A separately authorized recreation receives a new ID and is not restoration of identity or old links.

After an uncertain mutation, reconcile the named records and provider/delivery evidence before repeating it.

Related actions

• app_topolo_calendar.event_types.get: Read one known event type, including an inactive one.
• app_topolo_calendar.event_types.list: Discover active event types and their IDs.
• app_topolo_calendar.bookings.list: Find bookings within an explicit time window.

Declared schemas and provenance

The hidden action guide carries these exact current declared schemas. They are not rewritten to make the illustrations pass.

Input schema:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "eventTypeId": {
      "type": "string",
      "minLength": 1
    }
  },
  "required": [
    "eventTypeId"
  ],
  "additionalProperties": false
}

Output schema:

{
  "type": "object",
  "title": "Delete event type response",
  "description": "Operation result returned by event_types.delete.",
  "properties": {
    "success": {
      "type": "boolean"
    },
    "id": {
      "type": "string"
    },
    "data": {
      "oneOf": [
        {
          "type": "object",
          "title": "event record",
          "properties": {
            "id": {
              "type": "string",
              "description": "Stable identifier when the event exposes one."
            }
          },
          "additionalProperties": true
        },
        {
          "type": "object",
          "additionalProperties": true
        }
      ]
    },
    "result": {
      "type": "object",
      "additionalProperties": true
    },
    "message": {
      "type": "string"
    }
  },
  "additionalProperties": true,
  "x-topolo-contract-source": "derived-action-metadata",
  "x-topolo-contract-precision": "structural"
}

Source: TopoloCalendar@b378ceb73800ee1d1e6c4ff6f0b4179918cf632c, apps/api/src/routes/admin-event-types.ts. Current catalog metadata and source were compared without executing the application.

• Source-reviewed synthetic input/response; not captured or executed.
• Source revision is not proof of current deployment, caller access, provider connection or notification delivery.
• The illustrative response passes the declared structural schema. This establishes only schema compatibility, not deployed shape, values, authorization or business outcome.