/salarycom/salaries/benefits

POST /api/salarycom/salaries/benefits

Price: 5 credits

Get Salary.com (salary.com) total compensation breakdown for a US job title: base salary, bonus and the value of benefits (social security, 401K/403B, disability, healthcare, pension, time off), each with its median and share of the total, nationally or for one city.

How to use it

Use to see how a US job title's total compensation splits between pay and benefits. Pass location as a city-state slug for a city-adjusted figure.

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 (examples: "software-engineer-i", "marketing manager"; minLength: 1)
• location string nullable — US city-state slug; omitted for the national figure (examples: "new-york-ny", "austin-tx")

Response

• @type string (default: "SalarycomBenefits")
• id string nullable
• job_title string nullable
• alias string nullable
• city string nullable
• state_code string nullable
• currency string nullable
• total_compensation number nullable
• components array (default: [])
  • @type string (default: "SalarycomBenefitComponent")
  • name string nullable
  • category string nullable
  • median number nullable
  • percent_of_total 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 compensation data found for this job or location 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.