DEVELOPERS / DEVELOPERS
delete_absence
Behavior, inputs, outputs and permissions for delete_absence.
Reviewed · 2026-10-06 / Ridian
This reference is generated from the published tool contract.
Behavior and boundaries
Section titled “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
Section titled “Permissions”Granted scopes, accounts, calendars and visibility rules limit access. Workspace administrators do not automatically gain access to other users’ accounts.
bookings:write
{ "$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
Section titled “Output”{ "$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
Section titled “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.