From the blog · Page 2
How we build, what we learn, what we ship.
Posts about indexing public job postings at scale, salary parsing, and the systems that keep one universal JSON schema feeling small even as the source list keeps growing.
Glassdoor API: how to get job postings and salary data from Glassdoor
Glassdoor's official partnership API is closed to most companies. Here's how to access the same public job postings + salary insights through a third-party endpoint - no scraping, no IP rotation, no headless browsers.
ATS API: one integration for 30+ applicant tracking systems
Workday, Greenhouse, Lever, Ashby, BambooHR, SmartRecruiters, iCIMS, Workable - each has a different API shape. Here's how a unified ATS API replaces 30 integrations with one.
How to find old job postings: 6 ways to dig up an expired listing
Whether you're prepping for an interview, comparing comp bands historically, or hunting for a posting that was taken down - here are the practical ways to find old, expired, or archived job postings in 2026.
Lever API: pulling jobs from any Lever-hosted careers page
Lever exposes a public postings API at api.lever.co/v0/postings/{company}. Here's what it returns, what it's missing, and when you should use a normalized aggregator instead.
ZipRecruiter API: a modern alternative to the closed partner program
ZipRecruiter's official API requires a partner contract. Here's how to get ZipRecruiter job data - searchable, filterable, fresh - through a public REST endpoint instead.
JSearch API: what it returns, what it costs, and the direct-source alternative
JSearch is RapidAPI's most-installed jobs endpoint - but it's a wrapper, the RapidAPI markup adds 30%, and it lacks ATS coverage. Here's the technical comparison and when to use what.
Dice API: getting tech job postings without the partnership paperwork
Dice's job feed is the gold standard for US tech roles, but the official API is locked to enterprise integrations. Here's the dev-tier alternative - same data, REST endpoint, free tier.
Job posting API: one endpoint for every job on the web
If you've ever shopped around for a job-posting API and ended up with three vendors, four scrapers, and a deduplication script - this post is for you.
Indeed scraper vs Indeed API: why we deleted ours
Maintaining an Indeed scraper means fighting their anti-bot, rotating proxies, parsing changing HTML, and getting paged at 2am. Here's why the math turns into 'just use the API'.