Personio setup for application owners

There is nothing to register with Personio and no Personio credentials for you to hold. Personio has no OAuth app, no application-level Client ID or Secret, and no redirect URL: authentication is per consumer, and each consumer's own Personio administrator generates the credential for their account.

So this is a short guide. It covers the one part that is genuinely yours (telling consumers what to grant) and one part that is optional (the Personio Tech Partner programme).

1. Nothing to configure on the Apideck side

The connector asks the consumer for two connection fields, Client ID and Client Secret, which they enter in Apideck Vault when they connect. Apideck exchanges that pair for a short-lived access token and refreshes it for them. There are no application-owner credential fields to fill in: enable the connector for your integration on the Personio connector settings page and monitor connections from the Apideck Dashboard.

Because the credential belongs to the consumer, the walkthrough for creating it lives in the Personio connection guide. Link your consumers to that guide rather than reproducing the steps in your own onboarding material.

2. Tell consumers what to grant

This is the part worth your attention. Personio scopes access per credential: in the same form where the administrator generates the credential, they choose which resources it may read or write and which employee attributes it exposes.

That choice is silent. A credential created too narrowly still connects, still validates, and still returns 200, it simply returns partial or empty data, which surfaces in your product as missing fields rather than as a permissions error. Consumers cannot infer what to tick from Personio's UI, so tell them before they generate the credential:

• Employees: Read, plus Write if your integration creates or updates employees in Personio.
• Read on the section covering absences and time off, if you consume time-off requests.
• Readable employee attributes: name every attribute your integration depends on, including any custom ones you map. Only ticked attributes are transferred.

Listing the specific attributes you need is the highest-value thing you can put in your own onboarding copy. If a consumer reports missing fields, an under-scoped credential is the first thing to check: the administrator can widen the attribute selection in Personio without generating a new credential or reconnecting.

3. Partnership is optional, and your consumers need none

Apideck is already an approved Personio iPaaS partner (listed by Personio), so your consumers connect through that. None of them needs a partnership of their own, and you do not need one to ship your integration: any Personio administrator on a plan that includes API access can generate credentials.

Join the Tech Partner programme only if you want what it adds:

• A developer or extended trial Personio account for building and testing.
• A Personio Marketplace listing and visibility inside Personio's own software, plus partner identification on your API calls.

Apply through the Personio Tech Partner form. The contact for partner and integration questions is integration-partner@personio.de; ask them for an expected timeline once you apply. If the sign-up confirmation email never arrives, email that team rather than retrying with more addresses, because they can provision the account manually.

Marketplace listing carries its own thresholds (Personio quotes 50+ shared customers, an integration with 10+ active customer adoptions, and a technical quality review). Those gate the listing only. They do not gate API access, and they have no bearing on whether your consumers can connect.

FAQ

Do I paste any Personio credentials into Apideck? No. The only Personio credentials in play are the consumer's, entered per connection in Vault.

Do my consumers need to be Personio partners? No. They need a Personio plan that includes API access and an administrator to generate the credential.

A consumer is connected but data is missing. Almost always the credential's access levels or readable employee attributes, not the connection. See the connection guide troubleshooting table.

Still stuck? Contact Apideck Support.