Company Jobs from Greenhouse, Lever, Personio & Teamtailor

Turn a list of company job pages into one clean table of open jobs. Paste the job page of each company (for example https://jobs.lever.co/spotify) and get one row per job: title, department, location, remote status, publish date, salary when the company publishes it, and the link to the ad.

The Actor reads the open job feeds that the job systems publish for exactly this purpose: the Greenhouse Job Board API, the Lever Postings API, the Personio XML feed and the Teamtailor RSS feed. No login, no browser, no proxy, no API key.

Typical uses: recruiters and staffing agencies tracking target accounts, sales teams using hiring as a buying signal, job boards and aggregators, market research on who hires for which roles, and watching competitors' hiring (run it daily with "Published within the last days").

Supported job systems

System	Paste this	Notes
Greenhouse	https://job-boards.greenhouse.io/stripe or greenhouse:stripe	Department, office location, published and updated dates, pay range when the company publishes it
Lever	https://jobs.lever.co/spotify or lever:spotify (EU: https://jobs.eu.lever.co/name or lever-eu:name)	Team, department, commitment, workplace type, country, salary range when published
Personio	https://stark.jobs.personio.de or personio:stark	Department, offices, employment type, schedule, created date
Teamtailor	https://career.teamtailor.com or teamtailor:career.teamtailor.com	Department, role, remote status, city and country. Companies with their own domain: teamtailor:jobs.example.com

Personio and Teamtailor are widely used in Germany and the Nordics. Only companies that use one of these systems and have not switched off the public feed can be read. Other job systems are not supported yet.

Input

Field	Meaning	Default
companies	Job page URLs or the short forms above, one per line	required
titleKeywords	Keep jobs whose title, department or team contains one of these words	all jobs
locationContains	Keep jobs whose location or country contains one of these words (for example Denmark, Copenhagen, Remote)	all jobs
remoteOnly	Keep only remote jobs (see limits below)	off
publishedWithinDays	Keep only jobs published in the last N days (0 = no limit). Jobs without a date are kept	0
maxJobsPerCompany	Newest jobs first. You pay per job returned	200
includeDescription	Add the description as plain text (e-mail addresses and phone numbers are removed)	off
descriptionMaxChars	Longest description per job	2000
maxConcurrency	Companies read in parallel (requests to one website are always at least 1 second apart)	5
delaySeconds	Pause between requests to one website (minimum 1)	1

Example:

{
  "companies": [
    "https://job-boards.greenhouse.io/stripe",
    "https://jobs.lever.co/spotify",
    "https://stark.jobs.personio.de",
    "https://career.teamtailor.com"
  ],
  "titleKeywords": ["engineer", "developer"],
  "locationContains": ["Stockholm", "Copenhagen", "Remote"],
  "publishedWithinDays": 30
}

Output example

{
  "ats": "lever",
  "company": "spotify",
  "companyName": null,
  "jobId": "2d67c471-9015-41c0-a041-b982ec4a14fd",
  "title": "Account Executive - Commercial, Spotify Technology",
  "department": "Operations and Business Support",
  "team": "Platform",
  "location": "London",
  "country": "GB",
  "workplace": "hybrid",
  "remote": false,
  "employmentType": "Permanent",
  "publishedAt": "2026-10-23T21:51:17Z",
  "updatedAt": null,
  "url": "https://jobs.lever.co/spotify/2d67c471-9015-41c0-a041-b982ec4a14fd",
  "applyUrl": "https://jobs.lever.co/spotify/2d67c471-9015-41c0-a041-b982ec4a14fd/apply",
  "salaryMin": null,
  "salaryMax": null,
  "salaryCurrency": null,
  "salaryInterval": null,
  "description": null,
  "scrapedAt": "2026-10-27T22:44:58Z"
}

Fields that a job system does not publish are null. Dates are UTC.

Besides the dataset, every run saves a record COMPANY_SUMMARY in the key-value store: one entry per input value with the status (ok, failed, blocked, invalid), how many jobs the feed held and how many were returned. Use it to see which companies could not be read and why.

Limits and honesty

• Only open feeds. The Actor reads the job systems' public feeds, not the companies' websites. If a company turned its feed off, or the company name is wrong, the entry is reported as failed and not charged.
• robots.txt is respected. Before the first request to each website the Actor reads its robots.txt; if the path is not allowed, or robots.txt cannot be read, that company is skipped and listed as blocked.
• Fields differ per job system. team is filled for Lever (team) and Teamtailor (role) only; country for Lever and Teamtailor only; salary mostly for Greenhouse and sometimes Lever; Personio publishes no remote flag and no salary. Greenhouse has no remote flag either, so remoteOnly counts a Greenhouse job as remote only when its location text says "remote".
• Salary is only what the company publishes in the structured field. Many companies write the salary in the description text instead; the Actor does not parse text for numbers.
• Descriptions can name a contact person. They are off by default. When on, e-mail addresses and phone numbers are removed (best effort), but names in free text cannot be removed reliably.
• Counts can lag. The Actor shows what the job system's feed holds at the moment of the run; a feed may be cached by the provider.
• One Greenhouse, Lever, Personio or Teamtailor board is read at most 3,000 jobs.
• Output contains job facts only: no applicant data and no named recruiters. Check how you may use the data for your own purpose.

Pricing

Pay per job returned. Companies that cannot be read are not charged. If you set a maximum cost per run, the Actor stops when the limit is reached and says so in the log and the run status.

Sources

Greenhouse Job Board API (developers.greenhouse.io/job-board.html), Lever Postings API (github.com/lever/postings-api), Personio XML job feed, Teamtailor RSS feed (support.teamtailor.com, "RSS feed: how-to guide").