Glassdoor API: how to get job postings and salary data from Glassdoor

Glassdoor’s official partnership API is closed to most companies — they require an enterprise agreement and review every applicant. Most posts about the “Glassdoor API” either link to that gated program or describe scraping techniques that don’t survive contact with production traffic.

Here’s how to access Glassdoor’s public job postings (and basic salary insights) through a third-party endpoint that doesn’t require an enterprise contract.

What’s in (and not in) the official API

The Glassdoor Partner API, when you can get access, returns: job postings, company profiles, salary aggregates, and review aggregates. What you can’t get: per-review text, individual interview reports, or live salary submissions. Those stay behind the consumer sign-up wall.

JobsPipe’s Glassdoor source

We index Glassdoor’s public job listing pages and serve them through the same normalized schema as every other source:

curl https://api.jobspipe.dev/v1/jobs \
  -H "Authorization: Bearer $JOBSPIPE_KEY" \
  -G \
  -d "source=glassdoor" \
  -d "query=staff product manager" \
  -d "location=remote"

The compensation field is populated from Glassdoor’s “Estimated Pay” ranges when present, and parsed from the description otherwise. We don’t expose Glassdoor’s review or interview data — that’s explicitly user-contributed content under stricter TOS.

Why not just scrape Glassdoor yourself

Glassdoor sits behind Cloudflare with a fairly aggressive bot challenge layer. From a single residential IP you get maybe 50 requests before a CAPTCHA wall. To run it in production you need a proxy pool (~$500/mo entry), constant maintenance of the parsing layer (Glassdoor re-skins frequently), and the legal posture conversation with your team.

JobsPipe handles all of that. You hit one HTTP endpoint, get structured JSON, and don’t pay the maintenance tax.