Glassdoor company reviews

GET https://api.api.sh/glassdoor/v1/reviews
1 credit / call jobs & b2b try it in the playground →

Employee reviews of a company on Glassdoor, with paging, sort (relevance, newest, lowest rating), a text search and a current-employees filter. Each review: id, title, date, overall rating, pros, cons, advice to management, job title, location, current/former, employment status and length, recommend / CEO approval / business outlook, sub-ratings, helpful votes and employer responses. Also the company's ratings, rating distribution and review counts. Pass next_page back as page; null on the last page. Optional filters: overall star rating, reviewer employment_status, job_title and review language; applied_filters echoes them.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
company string Company name, e.g. Microsoft. Example: Microsoft
employer_id string Glassdoor employer id, instead of company.
url string Any glassdoor.com employer link, instead of company.
sort relevance | newest | lowest_rating relevance (default), newest, lowest_rating.
q string Only reviews mentioning these words.
current string 1 = current employees only.
per_page integer Reviews per page (1-50, default 10).
page integer Page number. Pass next_page from the previous response.
rating 1 | 2 | 3 | 4 | 5 Only reviews with this overall star rating.
employment_status string Reviewer employment types, comma separated (default full_time,part_time): full_time, part_time, contract, intern, freelance.
job_title string Only reviews from this job title (e.g. Software Engineer).
language string Review language, three-letter code (default eng; e.g. fra, deu, spa, por).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/glassdoor/v1/reviews?company=Microsoft" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.