The Personio Authentication API provides a single endpoint for obtaining access tokens to use with the Personio Personnel API. It accepts client credentials (client_id and client_secret) and returns a Bearer token that authenticates subsequent requests to Personio's HR management endpoints. This is the gateway to all Personio API operations.
1 endpointsJentic publishes the only available OpenAPI specification for Personio API, keeping it validated and agent-ready. The Personio API provides 46 endpoints for managing the full employee lifecycle including person records, employments, absence periods, attendance tracking, projects, compensations, recruiting pipelines, document management, and webhook configuration. It serves as the programmatic interface for Personio's HR platform used by European SMBs and mid-market companies.
46 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.