/habrcareer/resumes/search

POST /api/habrcareer/resumes/search

Price: 5 credits

Search Habr Career IT specialists (resumes) by keyword and filters

How to use it

Search Habr Career (career.habr.com) IT specialists / resumes by keyword with filters — qualification level, skills, city, minimum desired salary and currency, remote-ready, relocation-ready, and salary-specified-only; order by relevance, last visited, or salary. Each result carries the candidate username, name, avatar, specialization, qualification, desired salary, job-search availability, city, age, total experience, skills, communities (GitHub/Behance), citizenships, foreign languages, last job, company history, and education (university, faculty, plus additional courses). Direct contacts require an authorized recruiter account and are not returned.

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 (position, skill, or keyword)
• count integer required — Max number of resumes to return (min: 1)
• qualification string nullable — Qualification level (one of: "Intern", "Junior", "Middle", "Senior", "Lead")
• skills array nullable — Skill ids to filter by
• city_id integer nullable — City id to filter by (e.g. 678 = Moscow)
• salary integer nullable — Minimum desired salary (min: 0)
• currency string nullable — Salary currency (one of: "rur", "usd", "eur", "uah", "kzt")
• remote boolean nullable — Only candidates open to remote work
• relocation boolean nullable — Only candidates ready to relocate
• with_salary boolean nullable — Only candidates who specify a desired salary
• sort string nullable — Result ordering (one of: "relevance", "last_visited", "salary_desc", "salary_asc")

Response

• @type string (default: "HabrcareerResumeItem")
• id string required
• name string required
• url string required
• image string nullable
• specialization string nullable
• qualification string nullable
• salary_value integer nullable
• salary_currency string nullable
• salary_label string nullable
• availability string nullable
• city string nullable
• city_id integer nullable
• is_remote boolean nullable
• is_relocation_ready boolean nullable
• is_expert boolean nullable
• age integer nullable
• experience_months integer nullable
• last_visited_at string nullable
• skills array (default: [])
• divisions array (default: [])
• communities array (default: [])
• citizenships array (default: [])
• foreign_languages array (default: [])
• company_count integer nullable
• companies_history array (default: [])
  • @type string (default: "HabrcareerResumeCompanyHistory")
  • company string nullable
  • experience string nullable
• last_job object nullable
  • @type string (default: "HabrcareerResumeJob")
  • position string nullable
  • company string nullable
  • duration string nullable
• education object nullable
  • @type string (default: "HabrcareerResumeItemEducation")
  • university string nullable
  • university_url string nullable
  • faculty string nullable
  • duration string nullable
• additional_education array (default: [])
• about array (default: [])

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.