---
title: "List all absence requests"
method: GET
path: "/companies/{company}/absence-requests"
tags: ["Absence Requests"]
---

# List all absence requests

`GET /companies/{company}/absence-requests`

## Request

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

List your company’s absence requests with cursor-based pagination. Supports filtering by `employee_id` (UUID v7), `absence_type_id` (UUID v7), `status` (`pending`/`approved`/`rejected`/`cancelled`) and by date range (`from`/`to`, `YYYY-MM-DD`).

## Path parameters

- `company` string, uuid, required

## Query parameters

- `employee_id` string, uuid, nullable
- `absence_type_id` string, uuid, nullable
- `status` 'pending' | 'approved' | 'rejected' | 'cancelled' | 'null', nullable
- `from` string, date, nullable
- `to` string, date, nullable
- `limit` integer
- `starting_after` string, uuid
- `ending_before` string, uuid

## Headers

- `Factuarea-Version` string, date

## Response `200`

- object: Cursor-paginated list envelope shared by every v1 listing endpoint. `data` holds the page items; `has_more` signals whether another page exists; `next_cursor` is the cursor to pass back for the following page. Treat it as strictly opaque: send it through verbatim, never parse it and never assume a format — it is not the same across listings, and each listing documents its own cursor parameter. Concrete listings narrow `data` to their resource type via `allOf`.
  - `data` object[], required: Items on the current page.
    - `id` string, uuid, required: Opaque identifier of the absence request, a UUID v7.
    - `object` 'absence_request', required: Always `absence_request`.
    - `employee_id` string, uuid, required: UUID v7 of the employee the request belongs to.
    - `absence_type_id` string, uuid, required: UUID v7 of the requested absence type.
    - `absence_type_name` string, required: Human-readable name of the absence type (e.g. `Vacaciones`).
    - `color` string, required: Hex color `#RRGGBB` of the absence type, used to render the request on the calendar.
    - `status` 'pending' | 'approved' | 'rejected' | 'cancelled', required: Lifecycle status of the request: `pending`, `approved`, `rejected` or `cancelled`.
    - `start_date` string, date, required: First day of the absence (`YYYY-MM-DD`).
    - `end_date` string, date, required: Last day of the absence (`YYYY-MM-DD`).
    - `day_amount` string, required: Requested amount (working days or hours) as an exact decimal string.
    - `measurement_unit` 'days' | 'hours', required: Unit the request is measured in: `days` or `hours`.
    - `note` string, nullable, required: Optional note the employee attached when requesting.
    - `reviewer_user_id` string, uuid, nullable, required: UUID v7 of the user who approved or rejected the request; `null` while pending.
    - `review_note` string, nullable, required: Reason given on rejection (or note on approval); `null` while pending.
    - `reviewed_at` string, date-time, nullable, required: Timestamp of the approval/rejection (ISO 8601); `null` while pending.
    - `created_at` string, date-time, required: Creation timestamp (ISO 8601).
  - `has_more` boolean, required: Whether more pages are available after this one.
  - `next_cursor` string, nullable, required: Opaque cursor for the next page, or `null` when `has_more` is `false`. The example below shows the shape used by most listings; others return a different one, so pass the value back verbatim instead of validating it.

## 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).
- `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)