Who of the people is absent and until when (tenant:access)
POST /api/hr/v1/presence/query
Module: HR · operationId: queryPresence · Tag: Absences · Auth: access token (Authorization: Bearer <accessToken>)
Presence badges ("abwesend bis …"): date is the day asked for (default: today in the tenant's
time zone). Only approved absences count (also with a pending cancellation); absences that follow
each other directly or across a weekend form one stretch, until is its last day. Only absent
people are listed, never with type or status; unknown and inactive e-mails are left out. Follows
the team calendar: with absencesVisibleToColleagues off only the caller and the people the
caller decides absences for are answered. At most 500 e-mails (400).
Request body
application/json (required)
emails(array of string (email), required): E-mail addresses of the people asked fordate(string (date)): Day asked for, default: today in the tenant's time zone
Example:
{
"date": "2026-11-19",
"emails": [
"julia.hagen@muster-it.example",
"sophie.huber@muster-it.example",
"jonas.bauer@muster-it.example"
]
}
Responses
- 200 Absent people (
application/json) - 400 Error (
application/json)
Fields of the 200 answer:
absent(array of object): Only the absent people; never with type or statusemail(string (email)): E-mail address of the absent personuntil(string (date)): Last day of the absence stretch
Example 200 answer:
{
"absent": [
{
"email": "julia.hagen@muster-it.example",
"until": "2026-11-20"
}
]
}
Example request
curl -X POST 'https://api.mbcom.cloud/api/hr/v1/presence/query' \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H 'Content-Type: application/json' \
--data '{"date":"2026-11-19","emails":["julia.hagen@muster-it.example","sophie.huber@muster-it.example","jonas.bauer@muster-it.example"]}'