---
title: "Create an absence type"
method: POST
path: "/companies/{company}/absence-types"
tags: ["Absence Types"]
---

# Create an absence type

`POST /companies/{company}/absence-types`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/absence-types`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Create an absence type for the authenticated company (resolved from the API key, never from the payload). `name`, `is_paid`, `requires_approval`, `measurement_unit` (`days`/`hours`), `color` (hex `#RRGGBB`) and `visibility` (`everyone`/`managers_only`) are all required. Returns the created type with its generated `id` (UUID v7).

## Path parameters

- `company` string, uuid, required

## Headers

- `Idempotency-Key` string
- `Factuarea-Version` string, date

## Request body

- CreateAbsenceTypeRequest
  - `name` string, required: Absence type name.
  - `is_paid` boolean, required: Whether the absence is paid (the employee is compensated for the period).
  - `requires_approval` boolean, required: Whether requesting this absence requires a manager's approval.
  - `measurement_unit` 'days' | 'hours', required: Unit in which the absence is measured: `days` or `hours`.
  - `color` string, required: Type color for the calendar, in `#RRGGBB` hexadecimal format.
  - `visibility` 'everyone' | 'managers_only', required: Who can see the type: `everyone` or `managers_only`.

## Response `201`

Absence type created. The `Location` header contains the canonical URL of the new absence type.

- object
  - `data` AbsenceType, required: A configurable absence type for the Control Horario (time tracking) module — what an employee can request (holidays, sick leave, paid leave, …). Its flags decide whether the period is paid (`is_paid`) and whether it needs manager approval (`requires_approval`); `measurement_unit` fixes whether balances are tracked in days or hours.
    - `id` string, uuid, required: Opaque identifier of the absence type, a UUID v7 (e.g. `01931b3e-7c4a-7f2e-9a8b-3c5d6e7f8a9b`).
    - `object` 'absence_type', required: Always `absence_type`.
    - `name` string, required: Human-readable name of the absence type (e.g. `Vacaciones`).
    - `is_paid` boolean, required: Whether the absence is paid (the employee is compensated for the period).
    - `requires_approval` boolean, required: Whether requesting this absence requires a manager’s approval.
    - `measurement_unit` 'days' | 'hours', required: Unit in which the absence is measured: `days` or `hours`.
    - `color` string, required: Hex color `#RRGGBB` used to render the type on the calendar.
    - `visibility` 'everyone' | 'managers_only', required: Who can see the type: `everyone` or `managers_only`.
    - `is_system` boolean, required: Whether it is a default system type seeded for every company.
    - `status` 'active' | 'archived', required: Lifecycle status: `active` (usable) or `archived` (retired from use).
    - `created_at` string, date-time, nullable, required: Creation timestamp (ISO 8601).
    - `updated_at` string, date-time, nullable, required: Last-update timestamp (ISO 8601).

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company. `profile_not_found`: the company in the path does not exist, is not in the API key scope or belongs to the other environment (live or test).
- `409`: The request conflicts with data that already exists or with a request running at the same time. `resource_conflict`: another request was reserving identifiers for the same kind of record at that moment and this one could not complete its reservation. Nothing was written; send the request again after a few seconds.
- `422`: Validation failed. The `error.param` field identifies which input is invalid.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)