The API requires a Plus plan. See the plan feature matrix. If you do not have one yet, subscribe first so you can create an API key.
Step 1: Get your API key
Every request needs an API key. Without it, the API rejects the call. Sign in to the absentify Dashboard and generate a key. If you signed up with email, confirm your address before you create one. See Authentication for how to send the key.Step 2: Set up authentication
Send the key on every request:- Header name:
x-api-key - Header value: Your API key
Step 3: Make your first request
GET /requests lists absence requests that overlap a date range. start and end are required.
"your_api_key_here" with the key from step 1. This example returns every request that overlaps June 2026.
Date and time format
Many endpoints accept date or time parameters. Examples include the requiredstart and end parameters when listing requests or absences, and employment_start_date and birthday when creating a member.
Always send dates and times in ISO 8601:
When you send a time of day, always include a time-zone designator (
Z for UTC, or an offset such as +02:00). A value without one is interpreted in the server’s time zone and may shift the result.
Dates and times in API responses are also ISO 8601 with a UTC Z suffix, for example 2026-06-01T00:00:00.000Z.
end is inclusive. start=2026-06-01&end=2026-06-30 returns everything that overlaps June, including absences on 30 June.
For /requests, /requests_per_day, and /absences_per_day, the start…end window may span at most 1826 days (5 years). Wider or inverted ranges return 400. Retrieve longer periods in consecutive, smaller windows. See Limits.
Filtering by member or department
List endpoints such as/requests, /requests_per_day, and /absences_per_day accept optional request_member_ids and department_ids filters.
Pass multiple IDs as a comma-separated string, for example department_ids=dept1,dept2. Semicolons (;) are also accepted, for backward compatibility.
locale (for example locale=de). See Localized names.
Next steps
- Review Limits for the request rate and the date-range cap.
- See Responses for success and error payloads.
- See the introduction for allowances and localized names.