HH APItashkent.hh.uz ↗
Search candidate resumes on HeadHunter Uzbekistan (hh.uz). Returns titles, experience, age, activity dates, and status for matched profiles. Paginated results.
What is the HH API?
The tashkent.hh.uz API exposes one endpoint — search_resumes — that queries the HeadHunter Uzbekistan job portal and returns up to 8 fields per candidate profile, including resume title, total experience, job-search status, last-seen date, and a direct URL to the full profile. It covers Uzbekistan's largest job portal and supports keyword queries in both Latin and Cyrillic script.
curl -X GET 'https://api.parse.bot/scraper/87e29be8-5b08-4e10-8a39-f36fa0bc995d/search_resumes?query=python+developer&order_by=relevance' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for employee resumes/CVs by keyword query. Returns paginated resume listings with title, age, job search status, total experience, and activity dates. Pages are 0-indexed; anonymous access limits visible results to a few pages. Each page returns up to ~20 results.
| Param | Type | Description |
|---|---|---|
| page | integer | 0-indexed page number for pagination. |
| queryrequired | string | Search query for resumes — job title, skill, or keyword (e.g. 'python developer', 'бухгалтер'). |
| order_by | string | Sort order for results. Omitted defaults to relevance. |
| search_period | string | Filter by resume activity period in days. '0' means all time, '1' means last day, '7' means last week, '30' means last month. |
| experience_period | string | Filter resumes by experience period. Common values: 'all_time', '1_year', '3_years', '5_years'. |
{
"type": "object",
"fields": {
"page": "integer current page number (0-indexed)",
"total": "integer total number of resumes matching the query",
"resumes": "array of resume objects with title, resume_id, age, status, experience, last_seen, updated, url",
"has_more": "boolean indicating whether more pages are available"
},
"sample": {
"data": {
"page": 0,
"total": 660862,
"resumes": [
{
"age": "32года",
"url": "https://hh.uz/resume/fed3ec5500072fa70a0039ed1f455951653241",
"title": "Python Developer",
"status": "Не ищет работу",
"updated": "16 августа",
"last_seen": "16 августа",
"resume_id": "fed3ec5500072fa70a0039ed1f455951653241",
"experience": "6лет 8месяцев"
}
],
"has_more": true
},
"status": "success"
}
}About the HH API
What the API returns
The search_resumes endpoint accepts a query string and returns a paginated list of candidate resume summaries from hh.uz. Each item in the resumes array includes: title (the candidate's stated position or headline), resume_id, age, status (whether the candidate is actively looking), experience (total work experience), last_seen and updated timestamps, and a direct url to the profile. The response also surfaces total (total matching resumes) and has_more to drive pagination.
Filtering and pagination
Results are 0-indexed via the page parameter, with each page returning up to approximately 20 resumes. Use search_period to restrict results by when a resume was last active — pass '1' for the last day, '7' for the last week, '30' for the last month, or '0' for all time. Use experience_period to filter by candidate experience range: accepted values include 'all_time', '1_year', '3_years', and '5_years'. The order_by parameter controls sort order; omitting it defaults to relevance ranking.
Query language and coverage
The query parameter accepts any keyword, job title, or skill in either Latin or Cyrillic script — for example, 'python developer' or 'бухгалтер'. This makes the endpoint usable for both Uzbek-language and Russian-language resume searches, reflecting the bilingual nature of the hh.uz platform. Results are scoped to the Tashkent regional domain of HeadHunter.
The HH API is a managed, monitored endpoint for tashkent.hh.uz — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when tashkent.hh.uz changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official tashkent.hh.uz API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a candidate sourcing tool that filters resumes by experience period and keyword to shortlist applicants for a role
- Track how many active job seekers (status field) match a given skill on hh.uz over time
- Aggregate resume counts by query term using the total field to gauge talent supply for specific skills in Uzbekistan
- Monitor last_seen and updated timestamps to identify recently active candidates for outreach
- Compile ranked lists of candidates for a given job title using the order_by parameter
- Integrate resume search results into an ATS or internal recruiting dashboard with direct profile URLs
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does hh.uz have an official developer API?+
What does the status field in each resume object indicate?+
status field reflects the candidate's current job-search state as shown on their hh.uz profile — for example, whether they are actively looking, open to offers, or not currently seeking. This is useful for filtering outreach lists to candidates who are most likely to respond.How many pages of results can I retrieve?+
total field reports. Use search_period and experience_period filters to narrow results and stay within the accessible range.Does the API return full resume details like education, skills sections, or contact information?+
search_resumes endpoint returns summary-level fields: title, age, status, experience, last_seen, updated, and a URL to the full profile. Detailed resume sections such as education history, individual job entries, or contact details are not included. You can fork this API on Parse and revise it to add an endpoint that fetches full profile detail using the returned resume URL.