Glassdoor job search

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

Jobs on Glassdoor (US site) for keywords and a location, with the site's filters (posted within N days, remote, easy apply, salary range, job type). Each job: id, title, company and its rating and logo, location, age in days, easy apply and sponsored flags, pay range (10th/50th/90th percentile, currency, period, source), occupation, description snippet, extracted attributes (skills, benefits, level) and the job link. total is Glassdoor's count; 30 per page; companies lists the hiring companies in the results. Pass next_page back as page; null on the last page. Also filters by minimum employer rating, company size and seniority.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
q string Keywords, e.g. data analyst. Required unless url is given. Example: data analyst
location string City, state or country, e.g. New York, Texas, United States. Example: New York
url string A glassdoor.com job search link (/Job/...htm), instead of q and location.
from_age 1 | 3 | 7 | 14 | 30 Posted within this many days: 1, 3, 7, 14 or 30.
remote string 1 = remote jobs only.
easy_apply string 1 = Easy Apply jobs only.
min_salary string Lowest annual pay (USD).
max_salary string Highest annual pay (USD).
job_type fulltime | parttime | contract | internship | temporary fulltime, parttime, contract, internship, temporary.
page integer Page number (1-30). Pass next_page from the previous response.
min_rating 1 | 2 | 3 | 4 Employer rating at least this many stars.
company_size 1-200 | 201-500 | 501-1000 | 1001-5000 | 5001+ Employer size (employees).
seniority entry | mid_senior | director | executive Seniority level.

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

Example

curl "https://api.api.sh/glassdoor/v1/jobs?q=data+analyst" \
  -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.