Skip to content

Toolset employer_resumes

Resume search (52 params), saved searches, comments.

11 tools. Mutations require an explicit confirm=true argument; Auth marks tools that need an hh.ru token.

Tool Operation Auth Confirm Description
employer_add_applicant_comment POST /applicant_comments/{applicant_id} yes yes Add a comment on an applicant (paid access). body (form-encoded): {"text": str, "access_type": str}; access_type ids are listed in applicant_comment_access_type (get_dictionaries). Returns 201.
employer_assign_saved_search_manager PUT /saved_searches/resumes/{saved_search_id}/managers/{manager_id} yes yes Transfer a saved resume search to another manager of the company (manager ids from employer_list_managers). Returns 204 on success.
employer_create_saved_search POST /saved_searches/resumes yes yes Create a saved resume search (auto-search). All filters are query parameters, the same set as employer_search_resumes minus the text.logic/text.field/text.period triad (not representable here; a created search uses the default text matching mode). Returns 201 with the Location header pointing to the new search.
employer_delete_applicant_comment DELETE /applicant_comments/{applicant_id}/{comment_id} yes yes Delete own comment on an applicant (paid access, author only). Returns 204 on success.
employer_delete_saved_search DELETE /saved_searches/resumes/{id} yes yes Delete a saved resume search by id. Returns 204 on success.
employer_get_saved_search GET /saved_searches/resumes/{id} yes – Get one saved resume search by id, including its query, new_items counter (refreshed hourly) and last_used.
employer_list_applicant_comments GET /applicant_comments/{applicant_id} yes – List comments on an applicant: own comments plus comments of colleagues shared with the company (paid access). order_by ids come from applicant_comments_order (get_dictionaries).
employer_list_saved_searches GET /saved_searches/resumes yes – List saved resume searches (auto-searches) of the current employer, paginated (per_page max 10, default 5).
employer_search_resumes GET /resumes yes – Search the hh.ru resume database (employer access, paid service – check with employer_get_manager_method_access). Frequent filters (text, area, salary_from/salary_to, currency, experience, employment_form, label, order_by, page, per_page and others) are top-level parameters. Rare or niche filters are grouped into the nested advanced object: pass only the fields you need, unset fields are not sent. The advanced object also carries the dotted spec parameters text.logic, text.field, text.period and text.company_size. Resolve ids first: dict_areas, dict_professional_roles, dict_metro, get_languages. Results are grouped per applicant.
employer_update_applicant_comment PUT /applicant_comments/{applicant_id}/{comment_id} yes yes Update own comment text or access type (paid access, form-encoded body); omitted fields of body keep their previous values. Returns 204.
employer_update_saved_search PUT /saved_searches/resumes/{id} yes yes Update a saved resume search: pass either name (rename) or subscription (true/false) in one request – the spec forbids both together. Returns 204 on success.