/habrcareer/vacancies

POST /api/habrcareer/vacancies

Price: 5 credits

Get Habr Career vacancy details by id

How to use it

Get full details of a Habr Career (career.habr.com) IT job vacancy by its id or URL. Returns the job title, full HTML and plain-text descriptions, salary range with currency, hiring company (id, alias, rating, accreditation, logo), qualification level, employment type, remote flag, required skills, specializations, locations, and publication date.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• vacancy string required — Habr Career vacancy id, or a vacancy URL containing it (examples: "1000166570", "https://career.habr.com/vacancies/1000166570"; minLength: 1)

Response

• @type string (default: "HabrcareerVacancy")
• id integer required
• url string required
• description string nullable
• description_text string nullable
• salary object nullable
  • @type string (default: "HabrcareerSearchSalary")
  • salary_from integer nullable
  • salary_to integer nullable
  • currency string nullable
  • formatted string nullable
• salary_qualification string nullable
• predicted_salary object nullable
  • @type string (default: "HabrcareerSearchSalary")
  • salary_from integer nullable
  • salary_to integer nullable
  • currency string nullable
  • formatted string nullable
• company object nullable
  • @type string (default: "HabrcareerSearchCompany")
  • id integer nullable
  • alias string nullable
  • image string nullable
  • rating number nullable
  • is_accredited boolean nullable
  • web_url string nullable
• qualification string nullable
• employment string nullable
• employment_type string nullable
• is_remote boolean nullable
• is_archived boolean nullable
• divisions array (default: [])
• skills array (default: [])
• locations array (default: [])
• short_geo string nullable
• published_at string nullable
• published_label 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 — 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.