API and several attributes

Thank you very much. This is what I missed.  

Hi ​@Weena ,

I am experiencing the same issue; however, the solution described here does not work in my case.

I have selected multiple attributes that should be exposed via the API.
However, when calling the API for persons, only the attributes listed in the documentation are returned.

For example, these attributes are selected for the exposure: 

The get request for persons or a specific person responses these attribuets:

{'custom_attributes': [], 'email': 'example-user@my-company.com', 'employments': [{'id': 'xxxxxxxxxxxxxxxxxxxxxxxxxxx'}], 'first_name': 'Example', 'id': '12345678', 'last_name': 'User', 'preferred_name': 'Example User', 'status': 'ACTIVE', '_meta': {'links': {'employments': {'href': 'https://api.personio.de/v2/persons/1234567/employments'}}}}

The additional attributes are missing. 

My current request looks like that: 

GET https://api.personio.de/v2/persons/123456

or for more than one person:

GET https://api.personio.de/v2/persons?limit=50&cursor={{next_cursor}}

header:
Authorization: Bearer {{access_token}}
Accept: application/json

Is there any additional configuration or step required to retrieve all selected attributes for employees via the API?

Thank you very much in advance.

Best regards,
Adrian

Hi,
i have the same Issue than Adrian.

Is it possible that it's because the permissions in the API are identical to the permissions of the user who created the API?

Hi ​@Adrian Bartsch and ​@Frank Eggert, 

please try the employments-endpoint in addition to the persons-endpoint. Some attributes are linked to the employment instead of the person directly. The documentation can be found here: https://developer.personio.de/reference/get_v2-persons-person-id-employments

I hope this helps! 🙂

Best,
Christoph

Hi ​@Christoph S. ,

thanks for your answer.

i already tried to get information from the employments endpoint.

But these are not the informations that i need actually.

The reference lists the customs attributes only in the persons endpoint
(shown in the response 200).

Best regards
Frank