/hh/vacancies

POST /api/hh/vacancies

Price: 10 credits

Get HeadHunter vacancy details by id

How to use it

Get full details of a HeadHunter (hh.ru) job vacancy by its id. Returns the job title, salary range with currency and before/after-tax flag, HTML and plain-text descriptions, key skills, required experience, employment form, work formats and schedule, the hiring employer (id, name, logo, site), address with geo coordinates and nearest metro stations, professional role ids, publication date, and archived/premium flags.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• vacancy_id string required — HeadHunter vacancy id, or a vacancy URL containing it (examples: "133799732", "https://hh.ru/vacancy/133799732"; minLength: 1)

Response

• @type string (default: "HhVacancy")
• id integer required
• name string required
• url string required
• description string required
• description_text string nullable
• 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
• employer object nullable
  • @type string (default: "HhVacancyEmployer")
  • id integer nullable
  • name string nullable
  • alias string nullable
  • image string nullable
  • web_url string nullable
  • is_accredited_it boolean nullable
  • is_trusted boolean nullable
• address object nullable
  • @type string (default: "HhVacancyAddress")
  • city string nullable
  • street string nullable
  • building string nullable
  • display_name string nullable
  • district string nullable
  • lat number nullable
  • lng number nullable
  • metro_stations array (default: [])
    • @type string (default: "HhMetroStation")
    • id integer nullable
    • name string nullable
    • line_color string nullable
• area_id integer nullable
• area_name string nullable
• experience string nullable
• experience_label string nullable
• employment_form string nullable
• employment_form_label string nullable
• work_formats array (default: [])
• work_format_labels array (default: [])
• work_schedule_by_days array (default: [])
• work_schedule_by_days_labels array (default: [])
• working_hours array (default: [])
• working_hours_labels array (default: [])
• night_shifts boolean nullable
• internship boolean nullable
• accept_handicapped boolean nullable
• accept_labor_contract boolean nullable
• key_skills array (default: [])
• driver_license_types array (default: [])
• professional_role_ids array (default: [])
• platforms array (default: [])
• published_at string nullable
• valid_through_at string nullable
• is_archived boolean nullable
• is_premium boolean nullable
• contacts_hidden 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 — Vacancy not found or archived 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.