Discussions

Hello Personio API team,

We're trying to write the "new" salary type (13.+14. Gehalt) via the compensation API but the type-id (019c03e0-d08e-a061-f800-d12cd2e0f87a) gets rejected - but the same type is writeable (and written - we migrated ALL employees) via the web-interface.

Hi Forum,

Hello,

Hello,

hi everyone 👋
we're looking for advice from anyone who can help us out. our organization uses Workday globally and will be using Personio to support our team in Germany for HR, payroll, absence, time and benefits. globally we recruit and hire in Workday and then pass the record on to other systems that pick up the record or changes and take further steps.
we've had a look through the API documentation and it seems pretty limited. if anyone has built integrations for this kind of setup – even if it was for a different platform feeding data into Personio – feel free to reach out so we can learn from your experience.
thanks so much 🙏

There seems to be another problem with the updated_at field, the API returns the updated_at field with a Z that is indicating UTC timezone, but the value seems to be just the local time at which the update was made with a Z at the end, it's not the real UTC value.

Hi,

Hello together,

These response objects do not contain a reference to the legal entity the object belongs to. Currently my customer tries to address this issue by renaming the objects so the missing information is part of the name, but this is obviously not a permanent and failsafe solution.