/glassdoor/jobs/search

POST /api/glassdoor/jobs/search

Price: 20 credits

Search Glassdoor (glassdoor.com) jobs by keyword and location with filters for posting recency, employment type, seniority, remote, easy-apply, minimum company rating, salary range and distance. When the search could not be read to the end, the X-Warning response header states how many of the requested jobs were returned.

How to use it

Search Glassdoor jobs by keyword (and optional location). Returns jobs with id, title, url, employer_id, employer_name, employer_rating, image, location, location_type, age_in_days, is_easy_apply and an estimated pay range (pay_currency, pay_period, pay_min, pay_median, pay_max). Filters: date_posted, job_type, seniority, easy_apply, remote, company_rating (min 1-5), salary_min, salary_max, distance, sort. Glassdoor stops serving distinct listings for a query well before it runs out of matches, so a large count comes back short with no error: measured, a broad query yielded about 100 distinct jobs and a narrow one under 50. Read the length of the response rather than assuming count was met.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Job search keyword (examples: "software engineer"; minLength: 1)
• location string — City, state, country or US ZIP code to search within; the closest matching place is used. Leave empty to search the whole United States. A term that matches no place is dropped and the search runs country-wide, which an X-Warning response header reports (default: ""; examples: "New York", "Texas", "94105")
• count integer required — Max number of jobs to return (min: 1)
• date_posted string — Filter by posting recency (default: "any"; one of: "any", "last_day", "last_3_days", "last_week", "last_2_weeks", "last_month")
• job_type string — Filter by employment type (default: "any"; one of: "any", "full_time", "part_time", "contract", "internship", "temporary", "apprenticeship", "entry_level")
• seniority string — Filter by seniority level (default: "any"; one of: "any", "internship", "entry_level", "mid_senior", "director", "executive")
• easy_apply boolean — Only Easy Apply jobs (default: false)
• remote boolean — Only remote / work-from-home jobs (default: false)
• company_rating number nullable — Minimum company rating (1-5) (min: 1; max: 5)
• salary_min integer nullable — Minimum annual salary (min: 0)
• salary_max integer nullable — Maximum annual salary (min: 0)
• distance string — Search radius from the location (default: "miles_25"; one of: "exact", "miles_5", "miles_10", "miles_15", "miles_25", "miles_50", "miles_100")
• sort string — Result ordering (default: "relevant"; one of: "relevant", "date")

Response

• @type string (default: "GlassdoorSearchJob")
• id string required
• title string nullable
• url string nullable
• employer_id string nullable
• employer_name string nullable
• employer_rating number nullable
• image string nullable
• location string nullable
• location_type string nullable
• age_in_days integer nullable
• is_easy_apply boolean nullable
• pay_currency string nullable
• pay_period string nullable
• pay_min number nullable
• pay_median number nullable
• pay_max number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.