---
title: "Get a chronological list of absences"
method: GET
path: "/api/absences"
tags: ["Absences"]
---

# Get a chronological list of absences

`GET /api/absences`

## Request

- Base URL: `https://app.timetastic.co.uk` (the document declares no server; this is the origin it was published from)
- URL: `https://app.timetastic.co.uk/api/absences`
- Auth: none declared

Find out "who is off" on a certain day or range of days - whether thats public holidays, bookings, non working days or other events.
            Bookings are returned with times matching the user's work schedule so a multiple day booking will show start and end times <em>for that day</em> even if the booking covers multiple days
            <strong>Limited to 31 days per query. Rate limited to 1 request per second</strong>.

## Query parameters

- `Start` string, date
- `End` string, date
- `AbsenceQueryType` 0 | 1 | 2 | 3: <remarks> <strong>AllEvents:</strong> Returns Bookings, Non working days, Public Holidays, Locked Dates, Birthdays and Work anniversaries. <strong>AllAbsences:</strong> Returns everything we consider an absence: Bookings, Public Holidays and Non working days <strong>Bookings:</strong> Returns Bookings only <strong>PublicHolidays:</strong> returns Public Holidays only </remarks> - `0` — **AllEvents**: Locked dates, birthdays, work anniversaries, absences, non working days, public holidays, everything on the wallchart basically - `1` — **AllAbsences**: Just absences - non-working days, public holidays, bookings - `2` — **Bookings**: Just bookings - `3` — **PublicHolidays**: Just public holidays

## Response `200`

- TimetasticCoreCommandsAbsenceDay[]
  - `date` string, date
  - `absences` TimetasticCoreCommandsAbsence[], nullable
    - `absenceType` 'Booking' | 'PublicHoliday' | 'NonWorkingDay' | 'LockedDate' | 'Birthday' | 'WorkAnniversary': Whether it's an absence, locked date, public holiday, etc. - `Booking` - `PublicHoliday` - `NonWorkingDay` - `LockedDate` - `Birthday` - `WorkAnniversary`
    - `start` string, date-time: Start date/time of the event (for non working days this is based off the user's work schedule so you get the exact time the user isn't working)
    - `end` string, date-time: End date/time of the event (for non working days this is based off the user's work schedule so you get the exact time the user isn't working)
    - `detail` string, nullable: Leave Type name, locked date summary, public holiday name
    - `entityId` integer, nullable: Holiday ID, Locked Date ID etc.
    - `userId` integer, nullable: The userID this relates to
    - `userName` string, nullable: The user's name as displayed in Timetastic
    - `startUtc` string, date-time, nullable: UTC equivalent of Start, using the organisation timezone.
    - `endUtc` string, date-time, nullable: UTC equivalent of End, using the organisation timezone.

## Other responses

- `400`: If the start and end dates are invalid. Check the end is after the start date and that they don't cover more than 31 days

---

[API](https://skmtc.dev/timetastic/apis/timetastic-api.md) · [All operations](https://skmtc.dev/timetastic/apis/timetastic-api/llms.txt) · [OpenAPI document](https://skmtc.dev/timetastic/apis/timetastic-api/revisions/709ccb0412c3?raw)