--- title: "Glassdoor API" description: "Glassdoor API: the public endpoint is shut down and there is no key to request. What the docs describe, and how to read those employers' postings." canonical: https://jobspipe.dev/sources/glassdoor date_published: 2026-06-16 date_modified: 2026-09-30 author: Dvir Atias --- # Glassdoor API Glassdoor no longer has a working API: the v1 partner endpoint at api.glassdoor.com answered partner keys until mid-August 2025 and has returned HTTP 410 Gone since, and there was never a self-serve key. JobsPipe does not collect Glassdoor; the same employers' openings reach one search endpoint through the boards JobsPipe does collect, in one record shape across 30+ sources. > Glassdoor's v1 partner API stopped answering in August 2025 and JobsPipe does not collect Glassdoor. This page explains what Glassdoor still exposes, and how to reach the same employers' postings through the boards JobsPipe does collect. **Canonical URL:** https://jobspipe.dev/sources/glassdoor ## Official Glassdoor API documentation Glassdoor has no working public API. Its developer documentation is still published at glassdoor.com/developer and describes a v1 REST API for jobs and companies, called with a partner id and key. The endpoint those pages document returns HTTP 410 Gone, which we confirmed on 30 September 2026. Glassdoor's site sits behind a bot check, so a script may get a 403 from the developer pages; the Internet Archive copy linked below carries the same text. - Documented endpoint, now 410 Gone: `GET https://api.glassdoor.com/api/api.htm` - [Glassdoor API documentation: glassdoor.com/developer](https://www.glassdoor.com/developer/index.htm) - [The same page in the Internet Archive, captured 7 June 2026](https://web.archive.org/web/20260607213818/https://www.glassdoor.com/developer/index.htm) ## Coverage JobsPipe does not collect Glassdoor. This page explains what Glassdoor exposes publicly and how to reach the same postings where they are also published on a board JobsPipe does collect (Workday, Greenhouse, Lever, Ashby, LinkedIn, Indeed, SmartRecruiters, Workable, Personio, Recruitee, Teamtailor, EURES, Paylocity, Breezy HR, CV-Library, Y Combinator, Bayt, JobTech (Sweden), Resume-Library, Arbeitnow, Himalayas, Rise, Manatal, Pinpoint, JobScore, HireHive, The Muse, Remotive, Remote OK, Jobicy, Working Nomads, Landing.jobs). ## Why Glassdoor jobs data is confusing Glassdoor's developer pages at glassdoor.com/developer are still online. They still describe a 'simple, lightweight REST API' with Jobs and Companies actions, signed with a partner id (t.p) and key (t.k), and still say that the APIs not provided publicly are available to API partners who contact Glassdoor. The endpoint they document does not answer: in the Internet Archive's captures, api.glassdoor.com/api/api.htm returned JSON to partner keys as late as 15 August 2025 and HTTP 410 Gone from 20 August 2025, and it still returned 410 when we checked on 30 September 2026. There is no first-party way for a developer to consume Glassdoor data today. Third-party 'Glassdoor APIs' on scraping marketplaces read glassdoor.com pages behind Cloudflare's bot challenge and charge per result. JobsPipe does not collect Glassdoor at all. It collects the employer-side boards (Workday, Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Paylocity) and the LinkedIn, Indeed and Y Combinator job boards, where many of the same employers post their openings. ## Workarounds ### Use the Glassdoor v1 partner API Gone. api.glassdoor.com/api/api.htm has answered HTTP 410 since August 2025, so even existing partner ids and keys return nothing. ### Scrape glassdoor.com Possible but against Glassdoor's terms. Cloudflare bot challenges, CAPTCHA walls after a handful of requests per IP, frequent re-skins of the markup, and a legal posture conversation with your team. ### What JobsPipe offers instead JobsPipe does not collect Glassdoor. Search the same employers by name across the boards JobsPipe does collect; LinkedIn and Indeed rows carry the same postings, and ATS rows carry the stated salary when the employer publishes one. ## Fields available on every record - `id` - `job_title` - `company` - `company_domain` - `url` - `date_posted` - `discovered_at` - `last_seen_at` - `verified_at` - `status` - `closed_at` - `closed_reason` - `ghost_score` - `seniority` - `cities` - `state_code` - `min_annual_salary_usd` - `max_annual_salary_usd` - `technology_slugs` - `keyword_slugs` - `esco_skills` - `sources` ## FAQ ### Where do Glassdoor job listings come from? Glassdoor's job listings are largely syndicated from employer career sites and other job boards, so many postings you see there also live on an employer-side ATS or on boards like LinkedIn and Indeed. JobsPipe does not collect Glassdoor, but it collects Workday, Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Paylocity, LinkedIn and Indeed, where those same postings appear. Search by company_name_partial_match_or to find them. ### How can I get job salary data without Glassdoor? Take it from the posting itself. When an employer states a pay range, JobsPipe parses it into min_annual_salary_usd and max_annual_salary_usd on the record, and the min_salary_usd filter works against those fields. Nothing is estimated, and Glassdoor's crowd-sourced salary reports, company ratings and reviews are not carried and the salary fields are filled only when the posting states a range. ### Is there a Glassdoor reviews API? Not a public one. Review text, interview reports and salary submissions are Glassdoor's most protected content and are exposed through no self-serve API. Even the old partner API's employer-review action returned an employer summary with CEO and review-count data rather than a feed of review text, and that endpoint now answers 410 Gone. Third-party marketplace endpoints that claim to offer reviews are scrapers reading glassdoor.com behind Cloudflare's bot challenge, against Glassdoor's terms, and JobsPipe does not carry reviews either. ### What happened to api.glassdoor.com? The Internet Archive's captures of api.glassdoor.com/api/api.htm show the v1 API answering partner keys with JSON (success true, employer and review-count data) as late as 15 August 2025, then HTTP 410 Gone from 20 August 2025 onward. A 410 means the resource was removed on purpose, not a temporary outage. We re-checked on 30 September 2026 and it still answers 410. ## Does Glassdoor have an API? Not a working one. For years Glassdoor ran a v1 REST API at api.glassdoor.com: a small public set of job and employer actions plus actions reserved for approved partners, every call signed with a partner id and key. The docs at glassdoor.com/developer are still published, but the endpoint has returned HTTP 410 Gone since August 2025, so neither new nor existing partners can call it. Glassdoor's job listings are largely syndicated from employer career sites and other boards; the review and salary content is user-contributed and stays behind the sign-up wall. JobsPipe does not collect Glassdoor. It collects the employer-side ATS boards and the LinkedIn and Indeed job boards, where many of the same employers post. ## Is the Glassdoor API free? No, and it is not paid either in any self-serve sense: the only route was a partner agreement arranged by contacting Glassdoor, with no public rate card, and the endpoint it unlocked now answers 410 Gone. Marketplace 'Glassdoor APIs' are scrapers priced per result, and running one yourself means a proxy pool, a challenge solver and constant parser maintenance because Glassdoor re-skins often. JobsPipe's free tier returns 1,000 jobs to start and the sandbox at POST /v1/sandbox/jobs/search needs no key, but neither returns Glassdoor rows, because JobsPipe does not collect Glassdoor. ## How do I get a Glassdoor API key? There is no Glassdoor API key to get in 2026. The v1 API signed every call with a partner id (t.p) and key (t.k) issued through Glassdoor's registration and partner process, and the endpoint those keys called has returned 410 Gone since August 2025, so an old key is useless too. If you need job postings, the practical equivalent is a JobsPipe key: self-serve, issued in seconds, and usable against POST /v1/jobs/search with company_name_partial_match_or to find the employers you would have looked up on Glassdoor across the boards JobsPipe collects. ## What does the Glassdoor API documentation cover? Glassdoor's developer documentation is still published at glassdoor.com/developer: an API overview, a Jobs API page and a Companies API page describing GET requests to api.glassdoor.com/api/api.htm with v, format, t.p, t.k, action, userip and useragent parameters, and a required 'powered by Glassdoor' attribution on every page that shows results. It documents an endpoint that no longer answers, so read it as history. There is no current documentation for reading Glassdoor jobs, salaries or reviews programmatically. JobsPipe's docs at /docs cover the record shape returned for the boards JobsPipe does collect. ## Salary data without Glassdoor: which boards state pay Glassdoor's salary pages are crowd-sourced estimates. The alternative is the range the employer writes into the posting, which JobsPipe parses into min_annual_salary_usd and max_annual_salary_usd. How often a range is there depends on the board. Share of active postings with a stated salary range, by board JobsPipe collects (snapshot 2026-09-09): Y Combinator 67.7%, Ashby 56.1%, Greenhouse 46.8%, Indeed 36.8%, Workday 23.3%, Lever 22.7%, LinkedIn 22.1%, Workable 19.6%, Paylocity 10.7%, SmartRecruiters 5.3%. Filter with min_salary_usd when a stated range is a requirement, not a nice-to-have. ## What JobsPipe returns for Glassdoor Nothing under "source_or": ["glassdoor"]: JobsPipe does not collect Glassdoor and does not carry its reviews, ratings or salary reports. What JobsPipe returns is the same employers' postings where they are published: filter POST /v1/jobs/search with company_name_partial_match_or, and each record comes back with sources[0].provider naming the board it came from (linkedin, indeed, greenhouse, workday and so on), status, ghost_score, discovered_at and last_seen_at, and min_annual_salary_usd and max_annual_salary_usd when the posting states a range. The sample above shows the shape for one such record found on LinkedIn. ## Related - **Product:** https://jobspipe.dev/jobs-api - **All sources:** https://jobspipe.dev/sources - **Docs:** https://docs.jobspipe.dev - **Sign up (free tier):** https://jobspipe.dev/signup --- Generated from structured data. View the rendered page at https://jobspipe.dev/sources/glassdoor. --- Building this integration yourself? The steps above work. The alternative is one API over 30+ sources, already normalized and deduplicated. Try it right now - no key, no signup: ```bash curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search ``` Sample data, exact live schema. For live data get a free key (1,000 jobs to start) at https://jobspipe.dev/signup, then swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header. Full agent index: https://jobspipe.dev/llms.txt?src=md-twin