Hello Simon
Hope you are doing great.
I’m not sure to fully understand, because we can’t access your data as we would need your Client Key & ID to perform the API’s calls. And I’m not sure that’s what you want 
Which dynamic field specifically are you referring to ? Is it a custom one ? If so, did you took the ID and not the name ?
Do you mind sharing your code instead of the API endpoints ?
Also, where are you based ? Are you sure to use the correct timestamp here ?
Thanks for your answers,
Nathan
Hi Nathan,
thanks for your answer. Indeed, I don't want to share any credentials ;-)
The images I have added are not visible above, so thats makes it a little bit harder to understand my qustion.
Yes, it is a dynamic field (see screenshots below).
The code is not relevant, we are sending the second request in our solution. The behavior is reproducable with Insomnia / Postman.
From my perspective, the timestamp is not relevant. The first and the second screenshot are referring to the same personio employee ID. Or is the “updated since” filter not sending back the current data of an employee (and the data of another point in time?). From my understanding, the data is always the data as of now?!
Hello @SimonOe,
This is way better with the screenshots !
I can confirm this is not the expected behaviour. You should probably open a ticket to Personio support. If you have included the correct headers, Personio will be able to help quickly on that.
Was the value set to “408” at some point ? Or is it just coming out of the blue ?
You should try without the update_since filter, I’m curious to see if it’s not impacting the results you get here ..
Sorry not being able to help you further,
Nathan
