---
title: "Create absence"
method: POST
path: "/hris/absences"
tags: ["Unified HRIS API"]
---

# Create absence

`POST /hris/absences`

Create a new absence.

Check [this page](/hris/features/creating-absences) for a detailed guide.

<Note>
  This endpoint requires the permission **Manage absences** to be enabled in [your scope config](/scopes).
</Note>

### Example Request Body

```json
{
  "employee_id": "wXJMxwDvPAjrJ4CyqdV9",
  "absence_type_id": "3YKtQ7qedsrcCady1jSyAkY1",
  "start_date": "2019-09-17",
  "end_date": "2019-09-21",
  "start_time": "08:30:00",
  "end_time": "16:00:00",
  "start_half_day": false,
  "end_half_day": false,
  "employee_note": "Visiting the aliens"
}
```

## Headers

- `X-Integration-Id` string, required

## Request body

- PostHrisAbsencesRequestBody
  - `employee_id` string, required — The ID of the employee in Kombo or their ID in the remote system by prefixing it with `remote:` (e.g., `remote:12312`)
  - `absence_type_id` string, required — The ID of the absence type in Kombo (not its `remote_id`).
  - `status` 'REQUESTED' | 'APPROVED' — The state that the absence should be created in. Some tools may approve absences automatically if they were created for an absence type that does not require approval.
  - `start_date` string, date-time, required — The date that the absence starts. This is a plain date (i.e., `yyyy-MM-dd`), with all time information discarded.
  - `end_date` string, date-time, required — When the absence ends.The date that the absence ends. This is a plain date (i.e., `yyyy-MM-dd`), with all time information discarded.
  - `start_half_day` boolean — `true` if the absence should start in the middle of the day.
  - `end_half_day` boolean — `true` if the absence should end in the middle of the day.
  - `amount` number, double — The amount of time of the absence. Specifying this also requires specifying `unit`. This is supported by very few tools.
  - `unit` 'HOURS' | 'DAYS' — The time unit of the `amount` value. Specifying this also requires specifying `amount`.
  - `employee_note` string, nullable, required — A note describing the reason for this absence.
  - `start_time` string — The time of when the absence begins. Follows the format `HH:mm` or `HH:mm:ss` (e.g., `14:45:15`). If `start_time` is specified, `end_time` has to be specified as well.
  - `end_time` string — The time of when the absence ends. Follows the format `HH:mm` or `HH:mm:ss` (e.g., `14:45:15`). If `end_time` is specified, `start_time` has to be specified as well.
  - `remote_fields` object — Additional fields that we will pass through to specific HRIS systems.
    - `a3innuvanomina` object — Fields specific to A3 Innuva Nómina.
      - `benefit_type_id` 'Delegated Payment' | 'No Right to Benefit' | 'Direct payment' — Required for illness absences. Benefit type: Delegated Payment, No Right to Benefit, or Direct payment.
    - `adpworkforcenow` object — Fields specific to ADP Workforce Now.
      - `employment_id` string — [Required] The employment ID of the employee that the absence will be added to.
      - `paid_leave` boolean — Whether the absence is paid or not.

## Response `200`

POST /hris/absences Positive response

- PostHrisAbsencesPositiveResponse
  - `status` 'success', required
  - `data` object, required
    - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
    - `remote_id` string, nullable, required — 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.
    - `employee_id` string, required — 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.
    - `approver_id` string, nullable, required — **(⚠️ Deprecated - We won't increase coverage for this feature)** The Kombo ID of the employee who is responsible for approving this absence.
    - `start_date` unknown, required
    - `end_date` unknown, required
    - `start_half_day` boolean, nullable, required — `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. For multi-day absences, this only applies to the first day of the absence.
    - `end_half_day` boolean, nullable, required — `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. For multi-day absences, this only applies to the last day of the absence.
    - `start_time` unknown, required
    - `end_time` unknown, required
    - `amount` number, double, nullable, required — The amount of time this absence takes.
    - `unit` 'HOURS' | 'DAYS', nullable, required — The unit of time for this absence. Can be `HOURS` or `DAYS`.
    - `status` union — The absence’s current status. In rare cases where we can’t find a clear mapping, the original string is passed through.
      - 'REQUESTED' | 'APPROVED' | 'DECLINED' | 'CANCELLED' | 'DELETED'
      - string — If we can't find a clear mapping: The original string passed through.
    - `employee_note` string, nullable, required — A note the employee has added to this absence.
    - `type_id` string, nullable, required — The Kombo absence type ID of this absence.
    - `remote_created_at` string, date-time, nullable, required — The date and time the object was created in the remote system.
    - `remote_updated_at` string, date-time, nullable, required — A timestamp retrieved from the remote system, describing when the resource was last updated.
    - `changed_at` string, date-time, required — The timestamp when this specific record was last modified. This field only updates when properties directly on this record change, NOT when related or nested models change. For filtering that considers nested data changes, use the `updated_after` parameter which will return records when either the record itself OR its related models have been updated.
    - `remote_deleted_at` string, date-time, nullable, required — 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.
    - `remote_data` object, nullable, required — 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.
  - `warnings` object[], required — These are the interaction warnings that are shown in the dashboard. They are meant to provide debug information to you. We recommend logging them to the console.
    - `message` string, required

## Other responses

- `default` — The standard error response with the error codes for the HRIS use case.

---

[API](https://skmtc.net/kombo/apis/kombo-api.md) · [All operations](https://skmtc.net/kombo/apis/kombo-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/kombo/kombo-api/revisions/149bf44faf1a/schema)