Topolo Docs Topolo Platform
Open workspace

Delete availability override — Calendar

Remove one override and let the weekly schedule apply again.

Remove one override and let the weekly schedule apply again.

Action: app_topolo_calendar.availability.overrides.delete · DELETE /api/admin/availability/overrides/{overrideId}

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

FieldPresenceDeclared constraintMeaning
overrideIdrequiredstringOverride ID discovered with availability.overrides.list; belongs to the selected host.

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:

{
  "overrideId": "ovr_example"
}

Illustrative HTTP 200 source response:

{
  "ok": true,
  "overrides": []
}

ok acknowledges the delete statement; verify the ID is absent in overrides. This does not mean the date is closed: deleting a closed-day override may reopen it under weekly rules.

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

Effects and verification

  • Deletes the named override only for this host.
  1. Read overrides.list and availability.get; verify the intended resulting day behavior.

Refusals and recovery

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

HTTPErrorSupported response
403forbiddenReconcile the declared permission, organization and verified resource grant with the legitimate access owner; do not switch context to bypass a refusal.
404no_hostRead host.get; if it returns host:null, create the intended workspace host through host.update before retrying.

Recovery: Re-create the saved date/window, optionally using the prior id only after confirming current ownership. Check for bookings made during the changed availability.

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

  • app_topolo_calendar.availability.overrides.list: Discover date override IDs before updating or deleting one.
  • app_topolo_calendar.availability.overrides.create: Create an override, or update a discovered override by its ID.
  • app_topolo_calendar.availability.get: Read the current host’s complete weekly rules and date overrides.

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

Output schema:

{
  "type": "object",
  "title": "Delete availability override response",
  "description": "Operation result returned by availability.overrides.delete.",
  "properties": {
    "success": {
      "type": "boolean"
    },
    "id": {
      "type": "string"
    },
    "data": {
      "oneOf": [
        {
          "type": "object",
          "title": "availability record",
          "properties": {
            "id": {
              "type": "string",
              "description": "Stable identifier when the availability 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-availability.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.
  • Deleting a nonexistent or foreign-host override can produce ok:true without proving a row existed; verify the intended ID and scope.