/indeed/salaries

POST /api/indeed/salaries

Price: 10 credits

Get Indeed salary aggregates for a job title

How to use it

Get Indeed salary statistics for a job title. Returns estimated median, min, max and mean pay broken down by pay period (hourly, daily, weekly, monthly, yearly), the top-paying companies and top-paying cities for the role, and related job titles with their average pay.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job_title string required — Job title to look up salary data for, or a career-page URL containing it (examples: "software engineer", "https://www.indeed.com/career/software-engineer/salaries"; minLength: 1)

Response

• @type string (default: "IndeedSalary")
• url string required
• location string nullable
• currency string nullable
• display_period string nullable
• description string nullable
• salaries array (default: [])
  • @type string (default: "IndeedSalaryStat")
  • period string required
  • median number nullable
  • min number nullable
  • max number nullable
  • mean number nullable
  • data_point_count integer nullable
• top_paying_companies array (default: [])
  • @type string (default: "IndeedTopCompany")
  • name string nullable
  • alias string nullable
  • review_count integer nullable
  • salary_mean number nullable
  • salary_period string nullable
  • salary_count integer nullable
• top_paid_cities array (default: [])
  • @type string (default: "IndeedTopCity")
  • name string nullable
  • median number nullable
  • period string nullable
• related_titles array (default: [])
  • @type string (default: "IndeedRelatedTitle")
  • salary_mean number nullable
  • salary_period 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 — No salary data found for this job title 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.