POST /api/habrcareer/companies
Price: 1 credit
Get Habr Career company profile by alias
Get a Habr Career (career.habr.com) company profile by its alias or URL. Returns the company id, alias, title, description, logo, website, IT accreditation flag, employee rating with category breakdown, recommended-by percent with positive/neutral/negative split, employer-rating awards (main place/year and named badges), recent employee reviews (score, recommendation, pros/cons), published vacancy count, member/subscriber/want-to-work-here counts, typed contacts (email/phone/social/messenger), office addresses, office photos, and the company's open vacancies.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)company string required — Habr Career company alias, or a company URL containing it (examples: "tbank", "https://career.habr.com/companies/tbank"; minLength: 1)@type string (default: "HabrcareerCompany")id integer requiredalias string requiredurl string requiredweb_url string nullabledescription string nullableimage string nullableis_accredited boolean nullablerating number nullablerecommended_by_percent integer nullablerecommended_by object nullable@type string (default: "HabrcareerCompanyRecommendedBy")positive integer nullableneutral integer nullablenegative integer nullableratings array (default: [])@type string (default: "HabrcareerCompanyRating")average number nullablemain_award object nullable@type string (default: "HabrcareerCompanyAward")place integer nullableyear integer nullablesize string nullableother_awards array (default: [])@type string (default: "HabrcareerCompanyAward")place integer nullableyear integer nullablesize string nullablereviews_url string nullablereviews array (default: [])@type string (default: "HabrcareerCompanyReview")score number nullablerecommended_by_percent integer nullablecreated_at string nullableadvantages string nullabledisadvantages string nullableabout string nullablepublished_vacancy_count integer nullablemember_count integer nullablesubscriber_count integer nullablewant_work_here_count integer nullablecontacts array (default: [])@type string (default: "HabrcareerCompanyContact")type string nullablekind string nullablevalue string nullableurl string nullableaddresses array (default: [])@type string (default: "HabrcareerCompanyAddress")address string nullablelat number nullablelng number nullablephotos array (default: [])skills array (default: [])vacancies array (default: [])@type string (default: "HabrcareerVacancySearchItem")id integer requiredurl string requiredsalary object nullable@type string (default: "HabrcareerSearchSalary")salary_from integer nullablesalary_to integer nullablecurrency string nullableformatted string nullablesalary_qualification string nullablepredicted_salary object nullable@type string (default: "HabrcareerSearchSalary")salary_from integer nullablesalary_to integer nullablecurrency string nullableformatted string nullablecompany object nullable@type string (default: "HabrcareerSearchCompany")id integer nullablealias string nullableimage string nullablerating number nullableis_accredited boolean nullableweb_url string nullablequalification string nullableemployment string nullableis_remote boolean nullableis_marked boolean nullabledivisions array (default: [])skills array (default: [])locations array (default: [])reaction_count integer nullablepublished_at string nullablepublished_label string nullable422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.