How the API works
A job-posting feed for products that need complete, current, original job data on a schedule: job boards, search engines, labour-market research, recruiting tools and AI assistants.
- Where postings come from: company career sites, the hiring platforms behind them (Greenhouse, Lever, Ashby, Workday, Oracle, SmartRecruiters, Workable, Recruitee, Personio, BambooHR, Teamtailor, Breezy, ADP), Germany's Federal Employment Agency, and EURES (the public employment services of 30 European countries).
- How fresh it is: large employers are re-checked daily, others on a schedule set by how much they hire. The public employment services are read in full weekly and for new postings every few hours. A posting is in the feed the moment it is indexed, with no enrichment delay.
- How postings close: every source is re-read; a posting it no longer lists is closed and appears in
expired-jobs. A change to its title, location, pay, type, department or text appears inmodified-jobswith the fields that changed. - What comes with each posting: the exact original URL, the complete text where the source provides it, the full page text where it does not, normalised location (city, region, country, coordinates, time zone), pay, experience, work arrangement, employment type, language, skills, benefits, the posting's own responsibilities and requirements, and the employer's profile.
- How fields are derived: by rules over the posting's own text, with no language model. Nothing is invented: a fact the posting does not state stays
null. The same input always gives the same output.