Delete external calendar — Calendar

Disconnect a calendar and remove its local busy-time effect.

Action: app_topolo_calendar.external_calendars.delete · DELETE /api/admin/external-calendars/{calendarId}

Declared permission: app_topolo_calendar.availability: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.availability: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:

{
  "calendarId": "cal_example"
}

Illustrative HTTP 200 source response:

{
  "ok": true
}

ok acknowledges the source disconnect/delete sequence. Read the list to confirm absence and recheck availability, because formerly blocked times may open. It is not proof remote provider events were removed.

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

Effects and verification

• Disconnects a linked Nexus connection if present, then deletes the Calendar record and its local busy blocks.

1. Read external_calendars.list and relevant availability; reconcile partial disconnect/delete uncertainty before repeating.

Refusals and recovery

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

Recovery: No undelete operation restores the original connection identity or imported snapshot. Reconnection is a new authorized operation with provider consent/credentials and sync verification.

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

Related actions

• app_topolo_calendar.external_calendars.list: Discover external calendar IDs, connection state and sync history.
• app_topolo_calendar.external_calendars.sync: Replace an external calendar’s imported busy-time snapshot.

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": {
    "calendarId": {
      "type": "string",
      "minLength": 1
    }
  },
  "required": [
    "calendarId"
  ],
  "additionalProperties": false
}

Output schema:

{
  "type": "object",
  "title": "Delete external calendar response",
  "description": "Operation result returned by external_calendars.delete.",
  "properties": {
    "success": {
      "type": "boolean"
    },
    "id": {
      "type": "string"
    },
    "data": {
      "oneOf": [
        {
          "type": "object",
          "title": "external record",
          "properties": {
            "id": {
              "type": "string",
              "description": "Stable identifier when the external 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-external-calendars.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.