/hh/employers/vacancies

POST /api/hh/employers/vacancies

Price: 10 credits

List active vacancies of a HeadHunter employer

How to use it

List the active job vacancies posted by a specific HeadHunter (hh.ru) employer. Returns each vacancy with its id, title, canonical url, salary range with currency and before/after-tax flag, area, address, required experience, employment form, work formats and schedule, professional role ids, response count, and publication date. Use count to control how many vacancies are returned.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• employer_id string required — HeadHunter employer id, or an employer URL containing it (examples: "1455", "https://hh.ru/employer/1455"; minLength: 1)
• count integer required — Max number of vacancies to return (min: 1; max: 2000)

Response

• @type string (default: "HhEmployerVacancyItem")
• id integer required
• name string required
• url string required
• salary object nullable
  • @type string (default: "HhSalary")
  • salary_from integer nullable
  • salary_to integer nullable
  • currency string nullable
  • is_gross boolean nullable
  • mode string nullable
  • mode_label string nullable
  • frequency string nullable
  • frequency_label string nullable
• area_id integer nullable
• area_name string nullable
• address string nullable
• experience string nullable
• employment_form string nullable
• work_formats array (default: [])
• work_schedule_by_days array (default: [])
• working_hours array (default: [])
• professional_role_ids array (default: [])
• accept_temporary boolean nullable
• internship boolean nullable
• response_count integer nullable
• published_at string nullable
• created_at 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 — Employer not found or has no vacancies 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.