Personio Jobs Scraper: Salary Bands Included

Every open role from any Personio careers site, with the structured salary band Personio publishes and most systems do not: min, max, currency and period as separate fields. Plus seniority, schedule and years of experience. No API key, no proxy.

Features

• Any personio board, from the URL or token you already have. No API key, no login, no cookies, no proxy: this reads the public feed personio publishes so that job boards can index it.
• Every posting, not the first page. Paging is handled, including the places where personio reports a total it does not honour.
• One row per job, as clean JSON, with the same field names on every run.
• Filters that cost you nothing. Rows dropped by titleKeywords, locationKeywords or remoteOnly are never charged for.
• Errors are per company. One bad id does not end the run, and error rows are not charged.
• Run it on a schedule and the rows become a record of who started hiring and when.

How to use it

1. Click Try for free, or add this Actor to a task.
2. Put one or more board ids in the input. The example below is a real one.
3. Optionally narrow it with titleKeywords, locationKeywords or remoteOnly. Filtered rows are not billed.
4. Run it. Results appear in the dataset and can be exported as JSON, CSV, Excel or fetched from the API.

Input

Input	Type	Default	What it does
companies	array of strings	none	Not supported on personio: it returns the same empty response for a company that does not exist and for one with no open roles, so a derived token could never be confirmed
boards	array of strings	none	Board tokens to read, one per line, e.g. alasco
titleKeywords	array of strings	none	Keep only roles whose title contains any of these, one per line, e.g. security or staff engineer
locationKeywords	array of strings	none	Keep only roles whose location contains any of these, one per line, e.g. London or Israel
remoteOnly	true or false	false	Keep only roles flagged remote by the ATS, or whose title or location says remote or anywhere
includeDescription	true or false	false	Fetch the description text as well
maxResultsPerCompany	number	1000	Ceiling on roles taken from any single board
maxItems	number	none	A hard ceiling on rows for the entire run, across every company

{
  "boards": ["alasco"],
  "titleKeywords": ["engineer"],
  "remoteOnly": true
}

Output

One row per job. This is the shape, with the fields personio actually publishes:

{
  "title": "Senior Software Engineer",
  "location": "Berlin, Germany",
  "url": "https://boards.example.com/jobs/8130725",
  "jobId": "8130725",
  "postedAt": "2026-08-20T09:14:02Z",
  "departments": ["Engineering"],
  "offices": ["Berlin"],
  "description": "We are looking for...",
  "employmentType": "full-time",
  "compensation": "EUR 70000 - 90000 per year",
  "salaryMin": 70000,
  "salaryMax": 90000,
  "salaryCurrency": "EUR",
  "salaryPeriod": "year",
  "isRemote": true,
  "company": "alasco",
  "atsPlatform": "personio",
  "boardToken": "alasco",
  "boardUrl": "https://boards.example.com/alasco",
  "schedule": "full-time",
  "seniority": "senior",
  "yearsOfExperience": "3-5"
}

Field
title	the role as the company wrote it
location	as published, not normalised
url	the public posting, ready to open
jobId	the ATS's own id, stable across runs
postedAt	ISO 8601 UTC
departments	list
offices	list
description	opt in, off by default because it is expensive at the source
employmentType	full time, contract, intern, as the source says
compensation	the published range, as text
salaryMin	number
salaryMax	number
salaryCurrency	ISO code
salaryPeriod	year, month or hour
isRemote	true only for genuinely remote roles
company	what you asked for, echoed back
atsPlatform	which system it came from
boardToken	the board id used
boardUrl	the public board this came from
city	where the location names one
country	derived from the location, and from the job URL where the location is a phrase like "2 Locations"
region	state or province, where the location names one
schedule
seniority	derived from the title: intern, junior, senior, staff, lead, principal, director or executive. Empty where the title does not say, which is most of them
workArrangement	remote, hybrid or onsite
yearsOfExperience

What people use this for

Hiring data is not really about jobs. It is the earliest public signal a company gives that something changed, and it is why three different kinds of buyer end up on the same dataset:

• Sales and go-to-market. A company that opens six engineering roles this month is a company with new budget. Job postings say which team is growing and in which city, weeks before anything shows up in a funding announcement.
• Investors and market research. Headcount by function, tracked over time, across a whole portfolio or a whole sector. Every row carries the company, the team and the date, so a weekly run is a time series.
• Recruiting and talent. Where a competitor is hiring, which roles they have been trying to fill for months, and what they are paying, since Personio is one of the two systems here that publishes a pay range.

Run it once for a snapshot. Run it on a schedule and the same rows become a record of who started growing and when.

Company ids must be exact, and here is why

{ "boards": ["alasco"] }

Domain guessing is deliberately switched off for personio. See the note below: a 200 from this API does not prove the company exists, so a guess could never be confirmed, and a confident wrong answer is worse than asking you for the id.

What makes personio different

• Personio publishes a structured salary band, and only two of the nine systems here publish salary at all. Measured: min 45000.00, max 55000.00, currencyCode EUR, type yearly, as four separate fields. Ashby, the other one, hands back a formatted string. Numbers sort; strings display. This Actor gives you both.

• The period matters and is easy to lose. "45000 - 55000 EUR" means nothing until you know whether it is a year or a month, so salaryPeriod is its own field rather than folded into the text.

• Not every role publishes a band, and that is the company's choice rather than a gap here. Measured on the reference board: one of four positions carried one.

• A subdomain that does not exist answers 429, not 404, which is also what too many requests looks like. So a guess can never be confirmed and this Actor asks for the exact company rather than inventing a confident wrong answer.

• This is the only XML source on the shelf, and its feed embeds unescaped HTML inside the descriptions, which makes a strict parser refuse the whole document. The reader here is tolerant on purpose: one malformed description cannot cost you the board.

Filters that cost you nothing

Filtered rows are not charged. Keywords match as plain text, so c++ and node.js mean exactly that rather than being read as regular expressions.

Integrations and API

Every run writes to a dataset you can export as JSON, CSV or Excel, or read from the Apify API. The Actor can be scheduled, called from another Actor, or wired into Make, Zapier, Slack, Google Sheets and the rest of Apify's integrations. It is also callable by an AI agent through the Apify MCP server, and the output schema means the agent gets field descriptions rather than raw JSON.

Looking for an Indeed or Glassdoor API? There isn't one, and this is why you don't need it

Indeed has no public jobs API. Neither does Glassdoor, ZipRecruiter or LinkedIn Jobs, and all four block you at the edge. Measured from an ordinary residential address on 2026-08-01, with normal browser headers:

indeed.com/jobs          403      0 bytes
glassdoor.com/Job/...    403      0 bytes
ziprecruiter.com         403      0 bytes
upwork.com/nx/search     403      0 bytes

Zero bytes. Cloudflare rejects the request before it reaches an application, so there is nothing to parse and no proxy budget that fixes it.

But none of those four originate job data. They aggregate it from company career pages, and those pages run on systems like personio that publish a free, keyless, public API, because companies want their openings indexed. That API answered with real jobs from the same connection, in the same minute.

Going to the source is also fresher. An aggregator shows you its last crawl. This shows you the board.

FAQ

Do I need an API key or an account with personio? No. This reads the public feed personio publishes for indexing. Nothing here is behind a login, a paywall or a bot wall.

What am I charged for? Rows returned. Rows removed by your filters are not charged, and neither are error rows.

Can I get only what changed since my last run? Run it on a schedule and compare jobId, which is stable across runs. For change tracking with the work already done, see the sibling Actors below.

A board came back empty. Is the company not hiring? On personio an empty board cannot be told apart from a wrong id, so the message says exactly that rather than claiming the company has nothing open.

Notes

• The source is a public API that companies publish deliberately. Nothing here is behind a login, a paywall or a bot wall.
• An empty board cannot be told apart from a wrong id on this system, and the message says so.
• Errors are per company. One bad token does not end the run, and error rows are not charged.