---
title: "Delete absences."
method: GET
path: "/employee_absence/delete"
tags: ["Time Tracking|Absence"]
---

# Delete absences.

`GET /employee_absence/delete`

This endpoint enables the deletion of absences based on various filters. Please note that each absence day is a
unique instance with a distinct ID. In case the `dryRun` flag is enabled, the response will be simulated, and no
live data will be altered. Please be aware that absences have the potential to impact the time account of
employees.

## Query parameters

- `filter[byEmployeeReference][]` string[]
- `filter[from]` string
- `filter[to]` string
- `filter[byAbsenceTypeId][]` integer[]
- `filter[byId][]` integer[]
- `dryRun` boolean

## Response `200`

Success Response:

- StandardEmployeeAbsenceDeleteResponse
  - `deletedAbsences` object[] — The absences.
    - `id` integer — The internal id of the absence.
    - `employeeId` integer — The internal id of the employee.
    - `employeeReference` string — The employee personal number.
    - `name` string — The employee name.
    - `date` string — Represents a date. (ISO 8601) ICU-Format: yyyy-MM-dd
    - `absenceType` string — The absence type.
    - `absenceTypeId` integer — The internal id of the absence.
    - `absenceExternalId` string — The external id of the absence.
    - `halfDay` boolean — Is it only a half day absence.
    - `actualDuration` integer — The actual duration of the absence. If a absence is a full day absence the duration represents the target worktime on that day.
    - `externalId` string — External-ID of the absence type.
    - `updatedAt` string — Represents a date. (ISO 8601) ICU-Format: yyyy-MM-dd

---

[API](https://skmtc.net/geocapture/apis/geocapture-api.md) · [All operations](https://skmtc.net/geocapture/apis/geocapture-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/geocapture/geocapture-api/versions/869b05603541/schema)