Personio (via Apideck)

Access Personio through Apideck's HRIS unified API — one of 58 HRIS connectors that share the same method surface. Code you write here ports to BambooHR, Workday, Deel and 54 other HRIS connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Personio plumbing.

Quick facts

Apideck serviceId: personio
Unified API: HRIS
Auth type: oauth2
Apideck setup guide: Connection guide
Gotchas: page
Personio docs: https://developer.personio.de
Homepage: https://www.personio.com/

At a glance

Implementation difficulty: moderate — Consumer-Supplied API Credentials Instead of a User-Consent OAuth Flow
Vendor partnership required: no (developer portal) — Apideck is already an approved Personio iPaaS partner. Personio's free Tech Partner programme is optional and adds a Marketplace listing.
Apideck-managed credentials: not available — Each consumer supplies their own Personio API credentials.
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.
Sandbox: available (signup) — 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.
Costs: No separate API fee; the API requires the Core Pro plan, whose pricing is quote-based.
Rate limits: 2,000 requests/minute per IP overall, with tighter per-endpoint caps (300/minute on the employee list); HTTP 429 beyond either.
Authentication: Each 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)

Important to know:

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.

Facts synced from Apideck's connector metadata API — GET /connector/connectors/personio (overview field) is the live, authoritative version.

When to use this skill

Activate this skill when the user explicitly wants to work with Personio — for example, "sync employees in Personio" or "list time-off requests in Personio". This skill teaches the agent:

Which Apideck unified API covers Personio (HRIS)
The correct serviceId to pass on every call (personio)
Personio-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

HRIS: https://specs.apideck.com/hris.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List employees in Personio
const { data } = await apideck.hris.employees.list({
  serviceId: "personio",
});

Portable across 58 HRIS connectors

The Apideck HRIS unified API exposes the same methods for every connector in its catalog. Switching from Personio to another HRIS connector is a one-string change — no rewrite, no new SDK.

// Today — Personio
await apideck.hris.employees.list({ serviceId: "personio" });

// Tomorrow — same code, different connector
await apideck.hris.employees.list({ serviceId: "bamboohr" });
await apideck.hris.employees.list({ serviceId: "workday" });

This is the compounding advantage of using Apideck over integrating Personio directly: code against the unified HRIS API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.