/hh/employers

POST /api/hh/employers

Price: 10 credits

Get HeadHunter employer details by id

How to use it

Get full details of a HeadHunter (hh.ru) employer (company) by its id. Returns the company name, HTML and plain-text descriptions, logo and cover images, official website, location, industries, company category and size, number of currently active vacancies, awards and ranking badges (including the company's place in the hh.ru employer rating), IT-accreditation and verification flags, and whether employee reviews are available.

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: "1740", "https://hh.ru/employer/1740"; minLength: 1)

Response

• @type string (default: "HhEmployer")
• id integer required
• name string required
• url string required
• description string nullable
• description_text string nullable
• image string nullable
• cover string nullable
• site_url string nullable
• site_hostname string nullable
• area_name string nullable
• country_code string nullable
• category string nullable
• size_category string nullable
• organization_form_id integer nullable
• industries array (default: [])
  • @type string (default: "HhEmployerIndustry")
  • id integer nullable
  • name string nullable
• badges array (default: [])
  • @type string (default: "HhEmployerBadge")
  • type string nullable
  • description string nullable
  • position string nullable
  • year integer nullable
  • url string nullable
• hh_rating_position string nullable
• hh_rating_year integer nullable
• active_vacancy_count integer nullable
• has_open_reviews boolean nullable
• is_accredited_it boolean nullable
• is_trusted boolean nullable
• is_accepted boolean nullable
• is_zp_employer boolean nullable
• has_divisions 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 — Employer 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.