Delete absence

The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.

The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.

The Kombo ID of the employee to which the absence belongs to. The ID can be used to retrieve the employee from the get employees endpoint.

(⚠️ Deprecated - We won't increase coverage for this feature) The Kombo ID of the employee who is responsible for approving this absence.

The date this absence starts in the yyyy-MM-dd format.

The date this absence ends in the yyyy-MM-dd format.

true if the absence starts in the middle of the day, false if not, and null if the absence type doesn't support half-day absences. If an absence goes across multiple days and start_half_day is set, it means that on the last day the absence is only on the first half of the day.

true if the absence ends in the middle of the day, false if not, and null if the absence type doesn't support half-day absences. If an absence goes across multiple days and end_half_day is set, it means that on the first day the absence only starts in the second half-day.

The time at which this absence starts. Follows the format HH:mm:ss (e.g., 14:45:15).

The time at which this absence ends. Follows the format HH:mm:ss (e.g., 14:45:15).

The amount of time this absence takes.

The unit of time for this absence. Can be HOURS or DAYS.

The absence’s current status. In rare cases where we can’t find a clear mapping, the original string is passed through.

A note the employee has added to this absence.

The Kombo absence type ID of this absence.

The timestamp when this object was last changed. This value is tracked by Kombo based on changes in the data.

The date and time the object was deleted in the remote system. Objects are automatically marked as deleted when Kombo can't retrieve them from the remote system anymore. Kombo will also anonymize entries 14 days after they disappear.

Includes the data fetched from the remote system. Please be aware that including this in you scope config might violate other scopes that are set.

Remote data always has the endpoint path that we got the data from as the top level key. For example, it could look like: { "/companies": { ... }}

This is not available on all plans. Reach out to Kombo if you need it.