/blind/companies/salaries

POST /api/blind/companies/salaries

Price: 20 credits

Get Blind (teamblind.com) verified salary percentiles and recent submissions for a company

How to use it

Get Blind (teamblind.com) verified total-compensation data for a company by name/alias (URL segment like 'Google'), optionally scoped to a country (location). Returns salary percentiles (count, min, max, median, 25th, 70th, 90th) and the recent salary submissions, each with job title, level, specialization, years of experience, location, work type and the total compensation broken into base, bonus and equity.

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 name/alias (the URL segment, e.g. 'Google') or a full company profile URL (examples: "Google", "Microsoft", "https://www.teamblind.com/company/Google"; minLength: 1)
• location string — Country segment used by Blind salary pages (default: "united-states"; examples: "united-states", "india")

Response

• @type string (default: "BlindCompanySalaries")
• company string required
• location string required
• percentiles object nullable
  • @type string (default: "BlindSalaryPercentiles")
  • count integer nullable
  • minimum number nullable
  • maximum number nullable
  • median number nullable
  • percentile_25 number nullable
  • percentile_70 number nullable
  • percentile_90 number nullable
• submissions array (default: [])
  • @type string (default: "BlindSalarySubmission")
  • id string required
  • job_title string nullable
  • level string nullable
  • specialization string nullable
  • years_of_experience integer nullable
  • location string nullable
  • work_type string nullable
  • total_compensation number nullable
  • base number nullable
  • bonus number nullable
  • equity number nullable
  • submitted_at integer 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 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.