Discussions

Hello Personio Support Team,

We are currently developing an internal integration that consumes the Personio public API to retrieve employees’ worked hours (using the GET /v2/attendance-periods endpoint), in order to compare these hours with data from other internal systems.

During our testing, we have identified a consistent discrepancy between:

1. The worked hours displayed in the Personio web UI (Time Tracking / Timesheet)

2. The worked hours retrieved via the public API (attendance-periods), even when filtering by:

   • person.id
   • date ranges
   • status=CONFIRMED
   • and summing WORK periods (and subtracting BREAK periods)

Specifically, the Personio UI shows daily consolidated working hours that do not always match the aggregation of attendance periods returned by the public API. This difference is particularly noticeable when:

• manual adjustments are made to the timesheet after initial tracking,
• multiple short or fragmented periods exist,
• or internal time tracking rules are applied.

We have also observed that the Personio UI appears to rely on a different internal endpoint (e.g. /svc/attendance-bff/v1/timesheet/...) that returns already consolidated daily data, whereas the public API exposes more granular “raw” attendance periods.

---

Questions

Could you please help us clarify the following points?

1. Is there any public and supported API endpoint that returns daily consolidated working hours exactly as displayed in the Time Tracking UI?

2. If not, is it correct to assume that:

   • the public API (attendance-periods) is not guaranteed to match the final values shown in the UI,
   • and that discrepancies between the UI and API results are expected by design?

3. Which data source or endpoint does Personio recommend for integrations that need to retrieve employees’ worked hours in a consistent and supported way?

Our goal is to rely exclusively on official and supported APIs, and avoid depending on internal or undocumented endpoints.

---

Thank you very much for your support.
We look forward to your clarification.

Alejandro E.