In the Personio account under Settings > Integrations > API Credentials, create API credentials to obtain a Client ID and Client Secret.
POST to https://api.personio.de/v1/auth with a JSON body containing client_id and client_secret to receive a Bearer access token.
Store the token; it is valid for approximately 24 hours and can be reused for all API calls within that window without re-authenticating.
Call GET https://api.personio.de/v1/company/employees with the Authorization: Bearer <token> header to retrieve the employee list.
Use query parameters such as limit and offset for pagination, and the attributes parameter to request specific employee fields.
Known gotchas
The access token is valid for approximately 24 hours — build token refresh logic that re-authenticates when the token is near expiry rather than on every request.
API credentials control which employee attributes are accessible; if a field is missing from responses, check that the credential's attribute permissions include that field in the Personio settings.
Personio's API enforces rate limits per credential; running parallel high-volume syncs with a single credential may trigger throttling — back off and retry on 429 responses.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp