# delete_absence

Behavior, inputs, outputs and permissions for delete_absence.

Source: https://docs.getridian.com/developers/tools/delete_absence/
Language: en
Reviewed: 2026-10-06

This reference is generated from the published tool contract.

## Behavior and boundaries

Deletes an absence, e.g. when plans change. The member gets booking slots again for that period. Bookings that were already handed over stay with the substitute. Confirm with the user first.

## Permissions

Granted scopes, accounts, calendars and visibility rules limit access. Workspace administrators do not automatically gain access to other users’ accounts.

`bookings:write`

[Consent and boundaries](https://docs.getridian.com/developers/authentication/)

## Input

```json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "absence_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 64,
      "description": "absence_id from list_absences."
    }
  },
  "required": [
    "absence_id"
  ],
  "additionalProperties": false
}
```

## Output

```json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "absence_id": {
      "type": "string"
    },
    "deleted": {
      "type": "boolean"
    }
  },
  "required": [
    "absence_id",
    "deleted"
  ],
  "additionalProperties": false
}
```

## Errors and retries

Check the tool result for errors. Do not blindly retry writes after a timeout. Check the current resource or send status first.

[Error handling](https://docs.getridian.com/developers/errors/)