Discussions
The data is invalid
I'm submitting the recruiting form to https://api.personio.de/recruiting/applicant and getting this response {"success":false,"error":{"code":0,"message":"The given data was invalid.","errors":{"custom_863":["Parameter custom_attribute_custom_863 existiert nicht"]}}} please guide
Multiple Valid Bearer Tokens
Hi there, we are currently in the planning stage of using the Personio API for internal reporting. Unfortunately, I am tasked with planning our workflows, but cannot currently actively test against the API, because some data security topics need resolving first. That's why I'm asking here.
Is there a way to get employees that fulfill a specific criteria?
Hi, I want to create a sync between Salesforce and Personio. Is it possible to only get employees that meet a certain criteria like salesforceId= null or something?
company/attendances only start or end time possible?
Hi,
Access Personio by a perl script ?
Is there a way to access employee data by a script witten in perl?
Is there any way to fetch the not confidential details like date of birth
Changes of last_name & first_name not shown in historical data
Hi,
"The token has been blacklisted" after every request
Hi,
Rate Limit Monitor
Hi,
Confusing SMTP mechanism
We just started using SMTP relaying through our mail server to replace Personio mailbox by an internal one when we respond to an incoming mail.
Our setting is the public IP address of our exchange server with port 25 and non-encrypted mail transfer.
When we introduced this setting we needed to put a policy in place on our firewall. First aspect of this policy was to accept only connections from the 3 known Personio mail servers. Due to tests with encryption we started with a couple of open ports like 25, 465, 587, ... This worked fine especially for the setting I wrote above and so we decided to leave it for the moment. But now we wanted to restrict our firewall following our security guidelines to the needed rules and we cut the list of open ports to the only left port 25. When we did this, for our surprise the smtp connection timed out from this moment.
So we rolled back and had a look into our log and figured out the currently needed setting... For some reason it seems to be part of the Personio communication process, that port 465 needs to be open at the start of each SMTP communcication. It will not be actively used, but when we have it open, the communication starts on port 25 as configured, when we close it, the communication in Personio times out and there is nothing more to be seen in our Deny-Logs our somewhere else.