Personio Job Scraper — Careers XML Feed

For European HR analytics and talent teams that need job data from Personio-powered companies — Celonis, SumUp, Taxfix, Gorillas, FlixBus, Trivago, and thousands more EU companies.

Pay per result — $1.50 / 1,000 jobs. No API keys. No proxy. No extra cost.

Scrape job postings from any Personio-powered company careers page via the public XML feed.

Personio is one of Europe's leading HR platforms, used by thousands of companies (Celonis, SumUp, Taxfix, Gorillas, FlixBus, Trivago, and more). Every Personio customer gets a public careers page at https://<slug>.jobs.personio.de backed by an XML feed — this actor makes that data queryable at scale.

EU companies use Personio: Personio is Europe's leading HR platform for mid-size companies. Find any company's slug from https://<slug>.jobs.personio.de.

---

What you get

Field	Description
title	Job title
company	Company slug
location	Primary office + additional offices combined
remote_type	remote / hybrid / null — inferred from location + title
seniority	intern / entry / mid / senior / staff / lead / manager / director / vp / principal / executive
department	Department name
team	Recruiting category / team name
employment_type	Employment type (permanent, working_student, etc.)
schedule	Full-time, part-time
salary	Always null — not exposed in the public XML feed
posted_at	ISO-8601 creation date
url	Direct job listing URL
apply_url	Apply URL (same as listing URL for Personio)
job_id	Personio numeric job ID
global_id	Dedupe key: personio:<company>:<job_id>
description_text	Plain-text job description (HTML stripped)
description_html	Full HTML description from all description sections
parse_confidence	0.0–1.0 score — drops when key fields are missing
warnings	List of codes explaining any confidence deductions
scraped_at	ISO-8601 run timestamp

---

How it works

Personio publishes a machine-readable XML feed at https://<slug>.jobs.personio.de/xml?language=en. This actor:

1. Fetches the XML for each company slug in your input list.
2. Parses all <position> elements including the inline <jobDescriptions> sections.
3. Normalizes the data into a flat, typed schema with seniority and remote-type enrichment.
4. Applies optional keyword filters (title / location / remote-only).
5. Pushes results to the Apify dataset and charges per job (PPE).

Zero auth. Zero proxy. $0 infra cost. The XML feed is fully public.

---

Input

Field	Type	Default	Description
companies	string[]	["personio", "celonis", "sumup"]	Personio company slugs
titleKeyword	string	—	Case-insensitive filter on job title
locationKeyword	string	—	Case-insensitive filter on location
remoteOnly	boolean	false	Only return remote jobs
maxJobsPerCompany	integer	50	Cap per slug (0 = unlimited)
includeDescriptions	boolean	true	Include description_text + description_html

Finding a company slug

The slug is the subdomain in the careers URL:

• https://celonis.jobs.personio.de → slug = celonis
• https://sumup.jobs.personio.de → slug = sumup

---

Pricing

This actor uses Pay Per Result (PPE) pricing — you only pay for jobs actually pushed to your dataset.

Price: $0.0015 per job ($1.50 per 1,000 jobs)

Worked example: 10 companies × 50 jobs = 500 results = $0.75. 20 companies × 100 jobs = 2,000 results = $3.00.

---

Output sample

{
  "title": "Senior Backend Engineer",
  "company": "celonis",
  "location": "Munich, Germany",
  "remote_type": null,
  "seniority": "senior",
  "department": "Engineering",
  "employment_type": "regular",
  "schedule": "full_time",
  "posted_at": "2026-05-15T00:00:00+00:00",
  "url": "https://celonis.jobs.personio.de/job/123456",
  "job_id": "123456",
  "global_id": "personio:celonis:123456",
  "parse_confidence": 1.0,
  "warnings": []
}

---

FAQ

Do I need an API key or proxy? No. Personio's XML feed (<slug>.jobs.personio.de/xml) is publicly accessible — no auth, no proxy, no browser required.

What output formats are available? JSON, JSONL, CSV, and Excel via the Apify dataset export, plus the Apify REST API.

Can I schedule daily runs? Yes — use Apify Scheduler. Use global_id (personio:<slug>:<job_id>) as a stable dedup key across runs.

Why is salary always null? Personio's public XML feed does not include compensation data. This is a platform limitation, not a scraper limitation — if and when Personio adds salary to the feed, this actor will surface it.

---

Differentiators vs competitors

Feature	This scraper	Typical Personio scrapers
schedule field (full-time / part-time)	Yes	No
team field (recruiting category)	Yes	No
parse_confidence score	Yes	No
Seniority (11 levels)	Yes	Rarely
Multi-company batch	Yes	Some
Inline descriptions (no extra API calls)	Yes	Some
global_id for dedup	Yes	No
Price	$1.50/1k	varies

parse_confidence (0.0–1.0) and warnings in every record — implemented in normalize_personio.py. Your pipeline detects data drift before output breaks.

Note: salary is always null — Personio's XML feed does not expose compensation. schedule (full-time / part-time) and team (recruiting_category) are Personio-unique fields not available on other ATS scrapers.

If your target company uses Recruitee instead of Personio, see our Recruitee Job Scraper.

Use with AI agents (MCP)

This actor is MCP-compatible. Use it as a data source in n8n, Make, or any LLM agent pipeline.

https://mcp.apify.com/?tools=bovi/personio-job-scraper

The flat schema with global_id (personio:<company>:<job_id>) is drop-in-ready for vector databases, EU HR analytics pipelines, and job-matching LLM workflows. Need Greenhouse, Lever, Ashby, SmartRecruiters and Recruitee in the same pipeline? Use the flagship Multi-ATS Job Scraper — 6 ATS, one unified schema.

---

Integrations

Built for European talent-intel and HR-analytics teams tracking open roles across Personio-powered companies — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Not affiliated with Personio

This actor uses the public, unauthenticated XML feed that Personio exposes for every customer careers page. It is not affiliated with, endorsed by, or supported by Personio SE & Co. KG.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.