/salarycom/salaries

POST /api/salarycom/salaries

Price: 10 credits

Get Salary.com (salary.com) salary data for a job title: national pay percentiles, hourly rate, total compensation, salary by state and top-paying cities, by-skill and by-education pay, career-level progression, historical medians and related jobs.

How to use it

Look up Salary.com salary data for a job title or role slug. Returns one report with job_title, description, category, base_pay (p10/p25/p50/p75/p90), total_compensation_median, hourly_median, salary_by_state (50 states + DC), top_paying_cities, skill_salaries, education_salaries, career_levels, historical_salaries and related_jobs.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Job title or role slug to look up salary data for (examples: "marketing manager", "software-engineer-i"; minLength: 1)
• path_type string — Salary page type (default: "benchmark"; one of: "benchmark", "general")
• country string — Country edition (default: "us"; one of: "us")

Response

• @type string (default: "SalarycomSalary")
• job_title string nullable
• alias string nullable
• description string nullable
• category string nullable
• education_required string nullable
• experience_months string nullable
• currency string nullable
• base_pay object nullable
  • @type string (default: "SalarycomPercentiles")
  • p10 number nullable
  • p25 number nullable
  • p50 number nullable
  • p75 number nullable
  • p90 number nullable
• total_compensation_median number nullable
• hourly_median number nullable
• skills array (default: [])
  • @type string (default: "SalarycomSkill")
  • name string nullable
  • posting_frequency string nullable
  • description string nullable
• skill_salaries array (default: [])
  • @type string (default: "SalarycomSkillSalary")
  • name string nullable
  • median number nullable
  • increase_percent number nullable
• education_salaries array (default: [])
  • @type string (default: "SalarycomEducationSalary")
  • name string nullable
  • median number nullable
• career_levels array (default: [])
  • @type string (default: "SalarycomCareerLevel")
  • median number nullable
• salary_by_state array (default: [])
  • @type string (default: "SalarycomLocationSalary")
  • name string nullable
  • region string nullable
  • median number nullable
• top_paying_cities array (default: [])
  • @type string (default: "SalarycomLocationSalary")
  • name string nullable
  • region string nullable
  • median number nullable
• historical_salaries array (default: [])
  • @type string (default: "SalarycomYearSalary")
  • year integer nullable
  • median number nullable
• related_jobs array (default: [])
  • @type string (default: "SalarycomRelatedJob")
  • alias string nullable
  • median 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 job 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.