Skip to main content
DELETE
Delete Workforce Absence
← Own Workforce API Delete a single absence or accident record. Irreversible, and there is no endpoint that creates one back — restoring it means re-importing through the Imports API.
A record that describes an accident and the sick leave it caused is one row. Deleting it removes both events, not just one of them. There is no way to delete only the absence half and keep the accident.
Deleting a record changes the reported absence hours and accident counts for every period it fell in.

Request

Headers

string
required
Your API key for authenticationExample: sk_live_1234567890abcdef
string
required
Your organization UUIDExample: a8315ef3-dd50-43f8-b7ce-d839e68d51fa

Path Parameters

string
required
Record UUID — the id of the row, not accident_id or absenteeism_idExample: 6f2c8d13-4a5b-4c6d-9e0f-1a2b3c4d5e6f

Response

204 No Content with an empty body.

Example

Common Errors

401 Unauthorized

Cause: the key is invalid, or it does not belong to the organization in x-organization-id — the two are looked up as a pair. A request carrying no credentials at all answers AUTH_REQUIRED instead.

403 Forbidden

Cause: the key’s owner is not an enabled member of the organization, or their role cannot write.

404 Not Found

Cause: no record with that id inside your perimeter. A record whose employee belongs to another organization answers 404, never 403. Passing an accident_id or absenteeism_id instead of the row id also answers 404.

Bulk delete absences

Delete many by id

Bulk delete by filters

Delete a filtered set