Personio De Personio API
Browse all Personio De APIs65
AI ReadinessAI-Aware (B)65/100
Agent-ready OpenAPI document · curated by JenticHR recruitingEmployee Managementbearer46 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage the full employee lifecycle including person records, absences, attendance, compensations, recruiting applications, and organizational units. Supports 46 endpoints across HR operations for European companies.
Use for: I need to create a new employee record in Personio, List all absence periods for a specific person, I want to add an attendance entry for today, Get all open positions in the recruiting pipeline
Not supported: Does not handle payroll processing, tax calculations, or benefits administration - use for employee records, absences, attendance, and recruiting data only.
Jentic 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.
Install Jentic One Beta
Connect the Personio API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Personio API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpersonio.de%2Fpersonio-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpersonio.de%2Fpersonio-api" | 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.
Capabilities
What an agent can do with Personio API.
Create and manage employee records with employment history and personal details
Track absence periods with daily breakdowns and absence type categorization
Record and query attendance periods for timesheet management
Manage compensation records and types for payroll preparation
Access recruiting pipeline data including candidates, applications, and open positions
Configure webhooks for real-time HR event notifications
Download and list employee documents for compliance and records management
Use Cases
Patterns agents use Personio API for, with concrete tasks.
★ Automated Employee Onboarding
Create person records and associated employments programmatically when new hires are confirmed. The API supports POST /persons for creating employee records, GET /persons/{person-id}/employments for managing employment history, and POST /compensations for setting up salary data. Agents can trigger complete onboarding workflows from an accepted offer letter.
Create a new person via POST /persons with name, email, and department, then create an employment record via the employments endpoint with start date, position title, and contract type
Absence and Attendance Management
Track employee absences and attendance programmatically for timesheet compliance and leave balance calculations. The API provides full CRUD on absence-periods and attendance-periods, plus GET /absence-types for category lookup and GET /absence-periods/{id}/breakdowns for daily detail. Agents can automate leave requests, approvals, and timesheet reconciliation.
Create an absence period via POST /absence-periods for employee ID 456 with type 'vacation', start date '2026-07-01', and end date '2026-07-05', then verify via GET /absence-periods/{id}/breakdowns
Recruiting Pipeline Integration
Access the full recruiting pipeline including open positions, candidates, and applications. GET /recruiting/jobs lists open positions, GET /recruiting/candidates retrieves candidate profiles, and GET /recruiting/applications shows application status across the pipeline. Agents can sync this data with ATS tools or produce hiring funnel reports.
List all open positions via GET /recruiting/jobs, then retrieve applications via GET /recruiting/applications filtered by job ID to assess the current candidate pipeline
Compensation and Payroll Preparation
Manage compensation records for payroll preparation by creating and querying salary data, compensation types, and employment terms. POST /compensations creates new compensation entries, GET /compensations lists existing records, and GET /compensations/types provides the compensation category taxonomy. This enables automated payroll data feeds.
Create a compensation record via POST /compensations for employee ID 789 with annual salary amount, effective date, and compensation type ID
AI Agent HR Operations via Jentic
AI agents discover and execute Personio HR operations through Jentic without building custom integrations. Agents search for HR capabilities by intent, receive operation schemas with Bearer auth handled by Jentic's vault, and manage employees, absences, or recruiting data through a unified interface. Integration takes under an hour versus days of direct API work.
Search Jentic for 'create an employee absence record', load the POST /absence-periods schema with auth resolved, and execute with employee ID, absence type, and date range
Key Endpoints
46 endpoints — jentic publishes the only available openapi specification for personio api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/persons
List all employee records
POST
/persons
Create a new person record
POST
/absence-periods
Create an absence period
POST
/attendance-periods
Create an attendance entry
GET
/recruiting/applications
List recruiting applications
POST
/compensations
Create a compensation record
POST
/webhooks
Create a webhook subscription
GET
/reports/{id}
Get a specific report
GET
/persons
List all employee records
POST
/persons
Create a new person record
POST
/absence-periods
Create an absence period
POST
/attendance-periods
Create an attendance entry
GET
/recruiting/applications
List recruiting applications
POST
/compensations
Create a compensation record
POST
/webhooks
Create a webhook subscription
GET
/reports/{id}
Get a specific report
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
Personio API
- AI-Aware (B)65/100
63
Foundational Compliance63
Developer Experience & Jentic Compatibility50
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
63
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
93%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
60%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
50
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
39%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
60%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Personio API by hand means obtaining a bearer token from its auth endpoint, targeting api.personio.de/v2, and handling the request formatting for persons, absences, attendance, and recruiting yourself. Through Jentic you install once, import the Personio API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Personio puts the report id in the URL path (/reports/{id}), so a rule can pin your agent to reading one report; for the person, absence, and attendance operations the target travels in the request body, so there you limit the agent to the operations it needs, such as listing persons or creating an absence period. You choose the operations it may call, so writes like creating persons or registering webhooks are not included unless you add them.
Credential isolation
Your Personio token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list employees' or 'record an absence period', and Jentic returns the matching Personio operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Personio API through Jentic.
Why is there no official OpenAPI spec for Personio API?
Personio does not publish an OpenAPI specification for their v2 API. Jentic generates and maintains this spec so that AI agents and developers can call Personio API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Personio API use?
The Personio API uses Bearer token authentication. Obtain a token via POST /auth/token with your client_id and client_secret. The token is then included in the Authorization header for all subsequent requests. Through Jentic, token acquisition and refresh are handled automatically.
Can I manage employee absences in bulk?
The API handles absence periods individually via POST /absence-periods and PATCH /absence-periods/{id}. For bulk operations, agents iterate over employee IDs and create or update absence records sequentially. Each absence requires a person ID, absence type, start date, and end date.
How do I access recruiting data through Jentic?
Search Jentic for 'list recruiting applications' to discover GET /recruiting/applications. Load the schema and execute to retrieve application records. Related endpoints include GET /recruiting/jobs for positions, GET /recruiting/candidates for candidate profiles, and GET /recruiting/categories for job categories.
What HR data can I access through the Personio API?
The API covers persons (employee records), employments (job history), absence periods (leave tracking), attendance periods (timesheets), projects, compensations (salary data), organizational units, legal entities, recruiting data (jobs, candidates, applications), documents, reports, and webhooks. It spans 46 endpoints across the full employee lifecycle.
Can I set up webhooks for employee data changes?
Yes. POST /webhooks creates a subscription with a callback URL and event filter. GET /webhooks lists active subscriptions, PATCH /webhooks/{id} updates configuration, and DELETE /webhooks/{id} removes them. GET /webhooks/{id}/events shows the event history for a specific webhook.
Can I limit what my agent is allowed to do with the Personio API?
Yes. Because you run Jentic One yourself, your own rules decide which Personio operations and credentials the agent can use, so you can grant just what it needs, such as listing persons or creating an absence period, and leave writes like creating person records or registering webhooks out unless you add them. For reports the report id sits in the URL path (GET /reports/{id}), so a rule can pin the agent to reading a single report. For the person, absence, and attendance operations the target travels in the request body, so there you scope the agent by the specific operations it may call rather than by a fixed record.
GET STARTED