/levelsfyi/companies/salaries

POST /api/levelsfyi/companies/salaries

Price: 10 credits

Get Levels.fyi (levels.fyi) compensation for a company and job title by level and percentile

How to use it

Get Levels.fyi (levels.fyi) compensation data for a company and a job title. Returns the median total compensation, base salary, stock and bonus, the 10/25/50/75/90 percentiles for each, average total/base/stock/bonus compensation broken down per career level, the level ladder mapping, and recent individual salary submissions. Identify the company by alias (URL segment like 'google') and the title by alias (like 'software-engineer').

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Company alias (the URL segment, e.g. 'google') or a full company profile URL (examples: "google", "microsoft", "https://www.levels.fyi/companies/google"; minLength: 1; pattern: ^(?:https?://[^\s]+|[A-Za-z0-9][A-Za-z0-9._-]*)$)
• job_title string required — Job title alias (the URL segment, e.g. 'software-engineer') (examples: "software-engineer", "data-scientist", "product-manager"; minLength: 1)

Response

• @type string (default: "LevelsfyiCompanySalary")
• company string required
• company_alias string required
• title_alias string required
• url string required
• median_total_compensation number nullable
• median_base_salary number nullable
• median_stock_grant number nullable
• median_bonus number nullable
• median_level string nullable
• sample_count integer nullable
• vesting_type string nullable
• base_salary_percentiles object nullable
  • @type string (default: "LevelsfyiPercentiles")
  • p10 number nullable
  • p25 number nullable
  • p50 number nullable
  • p75 number nullable
  • p90 number nullable
• total_compensation_percentiles object nullable
  • @type string (default: "LevelsfyiPercentiles")
  • p10 number nullable
  • p25 number nullable
  • p50 number nullable
  • p75 number nullable
  • p90 number nullable
• stock_grant_percentiles object nullable
  • @type string (default: "LevelsfyiPercentiles")
  • p10 number nullable
  • p25 number nullable
  • p50 number nullable
  • p75 number nullable
  • p90 number nullable
• bonus_percentiles object nullable
  • @type string (default: "LevelsfyiPercentiles")
  • p10 number nullable
  • p25 number nullable
  • p50 number nullable
  • p75 number nullable
  • p90 number nullable
• levels array (default: [])
  • @type string (default: "LevelsfyiLevelCompensation")
  • level string required
  • primary_level_name string nullable
  • secondary_level_name string nullable
  • total number nullable
  • base number nullable
  • stock number nullable
  • bonus number nullable
  • commission number nullable
  • sample_count integer nullable
  • sample_count_last_12_months integer nullable
  • url string nullable
• level_mapping array (default: [])
  • @type string (default: "LevelsfyiLevelMapping")
  • titles array (default: [])
  • description string nullable
  • percent_workforce number nullable
  • order integer nullable
• samples array (default: [])
  • @type string (default: "LevelsfyiSalarySample")
  • uuid string required
  • level string nullable
  • focus_tag string nullable
  • location string nullable
  • gender string nullable
  • years_of_experience number nullable
  • years_at_company number nullable
  • base_salary number nullable
  • total_compensation number nullable
  • stock_grant number nullable
  • bonus number nullable
  • offer_date 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 — Company or title not found 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.