POST /api/hh/resumes/search
Price: 10 credits
Search HeadHunter resumes (guest-visible cards)
Search HeadHunter (hh.ru) resumes. Returns anonymized candidate cards visible to guests — desired job title, age, gender, expected and predicted salary, total work experience in months, key skills, photo and online flags, job-search status, language, and activity timestamps (contacts and identity are not exposed). Filter by keyword, region, experience level, recency and ordering.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)text string — Search query matched against resume title, skills and work history (default: ""; examples: "python")area string nullable — Region id to search within (e.g. 1 for Moscow, 2 for Saint Petersburg) (examples: "1")experience string nullable — Total work experience bucket (one of: "noExperience", "between1And3", "between3And6", "moreThan6")period string — Limit to resumes updated within this many days (default: "0"; one of: "0", "1", "3", "7", "30", "365")order_by string — Result ordering (default: "relevance"; one of: "relevance", "publication_time", "salary_desc", "salary_asc")count integer required — Max number of results (min: 1; max: 5000)@type string (default: "HhResumeSearchItem")id string requiredurl string requiredage integer nullablegender string nullablesalary object nullable@type string (default: "HhResumeSalary")amount integer nullablecurrency string nullablepredicted_salary object nullable@type string (default: "HhResumeSalary")amount integer nullablecurrency string nullabletotal_experience_months integer nullablekey_skills array (default: [])has_photo boolean nullableis_online boolean nullablejob_search_status string nullablelang string nullablesource string nullablelast_activity_at string nullablecreated_at integer nullableupdated_at integer 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 — 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.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.