/habrcareer/vacancies/search

POST /api/habrcareer/vacancies/search

Price: 5 credits

Search Habr Career IT vacancies by keyword and filters

How to use it

Search Habr Career (career.habr.com) IT job vacancies by keyword with rich filters — qualification level (Intern/Junior/Middle/Senior/Lead), skills, minimum salary and currency, remote-only, salary-present-only, city, and employment type; order by relevance, date, or salary. Alternatively browse a whole specialization (e.g. backend, data_scientist) via the specialization filter. Each result carries the vacancy id, title, salary range, hiring company (id, alias, rating, accreditation), qualification, employment, skills, divisions, locations, reaction count, and publication date.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• text string nullable — Search query
• count integer required — Max number of vacancies to return (min: 1)
• specialization string nullable — Specialization alias to browse (e.g. backend, frontend, data_scientist); resolved from the specializations reference. Cannot be combined with the other filters.
• qualification string nullable — Required qualification level (one of: "Intern", "Junior", "Middle", "Senior", "Lead")
• skills array nullable — Skill ids to filter by
• salary integer nullable — Minimum salary (min: 0)
• currency string nullable — Salary currency (one of: "rur", "usd", "eur", "uah", "kzt")
• remote boolean nullable — Only remote-friendly vacancies
• with_salary boolean nullable — Only vacancies that specify a salary
• city_id integer nullable — City id to filter by (e.g. 678 = Moscow)
• employment_type string nullable — Employment type (one of: "full_time", "part_time")
• sort string nullable — Result ordering (one of: "relevance", "date", "salary_desc", "salary_asc")

Response

• @type string (default: "HabrcareerVacancySearchItem")
• id integer required
• url string required
• 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
• is_remote boolean nullable
• is_marked boolean nullable
• divisions array (default: [])
• skills array (default: [])
• locations array (default: [])
• reaction_count integer 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 — The entity was not found, or a precondition failed 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.