A free, hosted job listings API with 1.8M+ listings across 60k companies. Get comprehensive active and historical job data from 30+ applicant tracking systems, with companies spanning industries and stages.
The normalization layer is where I'd want to understand the depth of work done. Thirty-plus ATSs means thirty-plus ways to express job title, seniority, and employment type — and raw aggregation without opinionated normalization just moves the cleanup problem to whoever's consuming the API. How standardized are fields like seniority level or work location across sources, or is that still left to the builder?
Historical job data is super useful for trend analysis. Do you expose fields like salary ranges and remote policy consistently, or is that only available when the ATS includes it?
the use case i'd want to validate before building on this is freshness. job postings have a short shelf life and a listing that was active three days ago might already be filled or pulled. what does the update frequency look like across the 1.8M listings and is there a way to query only postings updated within a specific window so i'm not surfacing stale data to end users. that latency question is probably the thing that determines whether this works for real-time job search applications or only for market analysis
Unified ATS access is the part people underestimate. Anyone who built a jobs-data side project knows you start scraping LinkedIn/Indeed and rebuild it monthly when something breaks. 30+ ATS in one schema removes the worst part of the stack. Free tier is a strong play for early devs.
About Job Postings API on Product Hunt
“View, monitor, and analyze 1.8M+ US jobs”
Job Postings API launched on Product Hunt on June 7th, 2026 and earned 157 upvotes and 10 comments, placing #4 on the daily leaderboard. A free, hosted job listings API with 1.8M+ listings across 60k companies. Get comprehensive active and historical job data from 30+ applicant tracking systems, with companies spanning industries and stages.
Job Postings API was featured in API (98.2k followers), Artificial Intelligence (470.3k followers) and Data (2.3k followers) on Product Hunt. Together, these topics include over 109.6k products, making this a competitive space to launch in.
Who hunted Job Postings API?
Job Postings API was hunted by Sam Crombie. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Job Postings API stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Sam Crombie
The normalization layer is where I'd want to understand the depth of work done. Thirty-plus ATSs means thirty-plus ways to express job title, seniority, and employment type — and raw aggregation without opinionated normalization just moves the cleanup problem to whoever's consuming the API. How standardized are fields like seniority level or work location across sources, or is that still left to the builder?