/glassdoor/salaries/search

POST /api/glassdoor/salaries/search

Price: 10 credits

Get Glassdoor (glassdoor.com) role-level salary estimates by job title: the overall pay distribution (base, additional and total pay percentiles) and the top-paying companies for that role with their own pay ranges.

How to use it

Look up Glassdoor salaries for a role (job title). Returns one report with role (job_title, currency, salary_count and total_pay / base_pay / additional_pay percentiles p10-p90) and top_paying_companies (employer_id, employer_name, employer_rating, image, job_title, currency, pay_period, salary_count and total_pay / base_pay / additional_pay percentile ranges).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• role string required — Job title / role to look up salaries for (examples: "software engineer"; minLength: 1)
• country string — Country edition (default: "us"; one of: "us", "gb", "ca", "de")
• count integer required — Max number of top-paying companies to return (min: 1)

Response

• @type string (default: "GlassdoorRoleSalaryReport")
• role object nullable
  • @type string (default: "GlassdoorRoleSalary")
  • job_title string nullable
  • currency string nullable
  • salary_count integer nullable
  • total_pay object nullable
    • @type string (default: "GlassdoorPayPercentiles")
    • p10 number nullable
    • p25 number nullable
    • p50 number nullable
    • p75 number nullable
    • p90 number nullable
  • base_pay object nullable
    • @type string (default: "GlassdoorPayPercentiles")
    • p10 number nullable
    • p25 number nullable
    • p50 number nullable
    • p75 number nullable
    • p90 number nullable
  • additional_pay object nullable
    • @type string (default: "GlassdoorPayPercentiles")
    • p10 number nullable
    • p25 number nullable
    • p50 number nullable
    • p75 number nullable
    • p90 number nullable
• top_paying_companies array (default: [])
  • @type string (default: "GlassdoorCompanySalary")
  • employer_id string nullable
  • employer_name string nullable
  • employer_rating number nullable
  • image string nullable
  • job_title string nullable
  • currency string nullable
  • pay_period string nullable
  • salary_count integer nullable
  • total_pay object nullable
    • @type string (default: "GlassdoorPayPercentiles")
    • p10 number nullable
    • p25 number nullable
    • p50 number nullable
    • p75 number nullable
    • p90 number nullable
  • base_pay object nullable
    • @type string (default: "GlassdoorPayPercentiles")
    • p10 number nullable
    • p25 number nullable
    • p50 number nullable
    • p75 number nullable
    • p90 number nullable
  • additional_pay object nullable
    • @type string (default: "GlassdoorPayPercentiles")
    • p10 number nullable
    • p25 number nullable
    • p50 number nullable
    • p75 number nullable
    • p90 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 — No salary data found for this role 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.