/glassdoor/jobs

POST /api/glassdoor/jobs

Price: 10 credits

Get a Glassdoor (glassdoor.com) job listing by id (or job URL): title, full description, location, estimated pay range, posting age, employment types, extracted skills, years of experience and education requirements, remote-work type, easy-apply flag, apply link and the hiring company (name, rating, logo).

How to use it

Fetch a single Glassdoor job by numeric listing id or a job URL. Returns one item with id, title, url, description (plain text), location, location_type, latitude, longitude, age_in_days, is_easy_apply, is_expired, apply_url, job_types (such as Full-time or Contract), skills, years_of_experience (such as 2 or 5), education (such as Bachelors degree or High school diploma or GED), remote_work_types (such as WORK_FROM_HOME), pay (currency, period such as ANNUAL/HOURLY, source, min/median/max estimate) and employer (id, name, image, rating, url). The pay range is Glassdoor's estimate unless pay.source is EMPLOYER_PROVIDED, and about one listing in six carries no range at all. years_of_experience and education come from Indeed's own extraction on the listing text and are populated on roughly half of listings, remote_work_types on about one in eight. Listings expire on a live board, so an id harvested days ago can return 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Glassdoor job listing id or a job URL containing it (examples: "1010126621706", "https://www.glassdoor.com/job-listing/full-stack-developer-JV_KO0,20.htm?jl=1010126621706"; minLength: 1)

Response

• @type string (default: "GlassdoorJob")
• id string required
• url string nullable
• description string nullable
• location string nullable
• location_type string nullable
• latitude number nullable
• longitude number nullable
• age_in_days integer nullable
• is_easy_apply boolean nullable
• is_expired boolean nullable
• apply_url string nullable
• job_types array (default: [])
• skills array (default: [])
• years_of_experience string nullable
• education string nullable
• remote_work_types array (default: [])
• pay object nullable
  • @type string (default: "GlassdoorJobPay")
  • currency string nullable
  • period string nullable
  • source string nullable
  • min number nullable
  • median number nullable
  • max number nullable
• employer object nullable
  • @type string (default: "GlassdoorJobEmployer")
  • id string nullable
  • name string nullable
  • image string nullable
  • rating number nullable
  • url string 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 — Job not found, expired or removed (well-formed but nonexistent listing id) 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.