/habrcareer/salaries

POST /api/habrcareer/salaries

Price: 1 credit

Get Habr Career IT salary analytics (min/max/percentiles/median + bonus) by specialization

How to use it

Get Habr Career (career.habr.com) IT salary analytics for a specialization, broken down by qualification level (All/Intern/Junior/Middle/Senior/Lead). Each group returns the minimum, maximum, 25th/75th percentiles, median salary, the sample size (total), and a salary breakdown into base value plus bonus and bonus percent. Optionally filter the sample by skills, company, city, employment type, or remote-only. Omit the specialization to get whole-market figures.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• specializations array nullable — Specialization aliases (e.g. backend, frontend, data_scientist); omit for the whole market
• qualification string nullable — Qualification level to filter the sample (one of: "All", "Intern", "Junior", "Middle", "Senior", "Lead")
• skills array nullable — Skill aliases to filter the sample (e.g. python)
• company string nullable — Company alias to filter the sample (e.g. yandex)
• city_id integer nullable — City id to filter the sample (e.g. 678 = Moscow)
• employment_type string nullable — Employment type to filter the sample (one of: "full_time", "part_time")
• remote boolean nullable — Restrict the sample to remote-friendly positions

Response

• @type string (default: "HabrcareerSalaryGroup")
• name string required
• min integer nullable
• max integer nullable
• p25 integer nullable
• p75 integer nullable
• median integer nullable
• total integer nullable
• salary_total integer nullable
• salary_value integer nullable
• bonus integer nullable
• bonus_percent 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 — The entity was not found, or a precondition failed 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.