/kununu/companies/salaries

POST /api/kununu/companies/salaries

Price: 10 credits

Get Kununu (kununu.com) salary benchmarks for a company by alias or profile URL

How to use it

Get Kununu (kununu.com) salary benchmarks for a DACH company by alias (URL segment like 'bmwgroup') or profile URL. Returns per job-role salary ranges (min/max/median/average and entry count), salary satisfaction breakdown, compensation score with industry comparison, and the highest/lowest paid roles. All amounts are gross yearly pay in the currency of the country edition the company is listed under, reported on the response as `currency` (EUR for de/at, CHF for ch).

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 (URL segment like 'bmwgroup') or a full company profile URL (examples: "bmwgroup", "sap", "https://www.kununu.com/de/bmwgroup"; minLength: 1; pattern: ^(?:https?://[^\s]+|[A-Za-z0-9][A-Za-z0-9._-]*)$)
• count integer required — Max number of job-role salary ranges to return (min: 1)
• country string — Country edition the company is listed under (default: "de"; one of: "de", "at", "ch")

Response

• @type string (default: "KununuCompanySalary")
• alias string required
• url string required
• country_code string required
• currency string required
• total_count integer nullable
• compensation object nullable
  • @type string (default: "KununuSalaryCompensation")
  • score number nullable
  • rounded_score number nullable
  • industry_comparison number nullable
  • review_count integer nullable
• satisfaction object nullable
  • @type string (default: "KununuSalarySatisfaction")
  • positive_percentage number nullable
  • neutral_percentage number nullable
  • negative_percentage number nullable
  • positive_count integer nullable
  • neutral_count integer nullable
  • negative_count integer nullable
  • total_reviews integer nullable
• highest_paid object nullable
  • @type string (default: "KununuSalaryStat")
  • job_title string required
  • average number nullable
• lowest_paid object nullable
  • @type string (default: "KununuSalaryStat")
  • job_title string required
  • average number nullable
• ranges array (default: [])
  • @type string (default: "KununuSalaryRange")
  • job_role_id string nullable
  • job_role_title string required
  • job_role_title_slug string nullable
  • range_min number nullable
  • range_max number nullable
  • median number nullable
  • average number nullable
  • entry_count integer nullable
  • market_range_min number nullable
  • market_range_max number nullable
  • market_median number nullable
  • market_average number nullable
  • market_entry_count integer nullable
  • is_claimed boolean 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.