Personio
Service ID: personio
Always be on top of your HR management. With a holistic HR and applicant management software designed for companies with 10 to 1000 employees.
At a Glance
- Difficulty
- ⚡MODERATEConsumer-Supplied API Credentials Instead of a User-Consent OAuth Flow
- Authentication
- OAuth 2.0Each consumer's Personio administrator generates a Client ID and Secret in their own Personio account. Nothing for you to register.
- Webhooks
- Virtual webhooks↗ (Apideck polls for employee created, updated and terminated events)
- Partnership Required
- No(Apideck is already an approved Personio iPaaS partner. Personio's free Tech Partner programme is optional and adds a Marketplace listing.)
- Partnership Application
- Developer Portal↗
- Apideck Credentials
- Not available(Each consumer supplies their own Personio API credentials.)
- Costs
- No separate API fee; the API requires the Core Pro plan, whose pricing is quote-based.
- Sandbox Availability
- Available — Access Sandbox↗(Free, self-service Partner Developer Account from Personio's partner trial. A Personio free trial or a consumer's own account also work for testing.)
- Account Type Required
- A Personio account on a plan that includes API access (Core Pro at the time of writing).
- Consumer Access Level
- Administrator: only a Personio administrator can generate the API credentials.
- Rate Limits
- 2,000 requests/minute per IP overall, with tighter per-endpoint caps (300/minute on the employee list); HTTP 429 beyond either.
Responsibility matrix
| Task | You (Customer) | Your Consumer | Apideck |
|---|---|---|---|
| Personio account on a plan with API access | Share the plan requirement | ✓ | — |
| Generate API credentials | — | ✓ (administrator) | Instructions provided |
| Choose access levels and readable attributes | State what the integration needs | ✓ | — |
| Enter Client ID and Secret in Vault | Implement Vault | ✓ | — |
| Token exchange and refresh | — | — | ✓ |
| Build via the Unified API | ✓ | — | Maintains the connector |
| Connection sync | — | — | ✓ Polls via virtual webhooks |
| Monitor connections | ✓ Via the Apideck Dashboard | Can revoke the credentials | Logs and alerts |
Environments
- Single environment
- Personio uses the same credentials for testing and production: the Client ID and Secret a consumer's administrator generates, with no separate sandbox host or credential type. Apideck cannot supply temporary shared test credentials for this connector, because every connection uses credentials the consumer generates themselves. A trial or sandbox account will not mirror a specific consumer's plan, access levels or attribute settings, so take care when testing against live HR data.
🚨Important to Know About Personio
- Access is scoped at credential creation: the administrator picks which resources are readable or writable and which employee attributes are exposed, so a credential created too narrowly returns partial or empty data.
- Personio can exclude individual employees from API transfer. An 'Include in transfer' field on each employee record governs whether that person is shared, so a consumer's own configuration can legitimately hide records from your integration.
- Personio's 1 December 2026 cutoff for passing API credentials as query-string parameters does not affect this connector: it already sends them in the request body, so nothing changes for you.
📦
2 supported resources
View field mappings, supported operations, and schema details