# HeadHunter (hh.ru) Jobs Scraper (`scrapyx/hh-jobs-scraper`) Actor

Scrapes job vacancies with full descriptions from HeadHunter — the largest job site in Russia, Kazakhstan, Uzbekistan and Belarus. Keyword and region search with salary, experience, schedule and date filters, plus direct vacancy-URL lookup.

- **URL**: https://apify.com/scrapyx/hh-jobs-scraper.md
- **Developed by:** [Ibnu Adzim](https://apify.com/scrapyx) (community)
- **Categories:** Jobs, Business, Automation
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.35 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## HeadHunter (hh.ru) Jobs Scraper

Extract job vacancies — with full descriptions, employers, salaries and regions — from HeadHunter, the largest job site in Russia, Kazakhstan, Uzbekistan and Belarus (hh.ru, hh.kz, hh.uz, rabota.by).

### Why use this actor

- **No account, no login, no API key.** HeadHunter's own developer API refuses anonymous traffic; this actor reads the public site directly, so there is nothing to register or renew.
- **Four countries from one actor.** hh.ru, hh.kz, hh.uz and rabota.by all run on one search index — pick the site, then filter to any country, region or city.
- **The whole ad, not just the card.** Every result can carry the complete vacancy text, key skills, employer profile, exact publication date and salary breakdown (gross/net, per month or per shift).
- **Filters that actually apply.** Region, experience, employment type, schedule (including remote-only), minimum salary, "posted in the last 24 hours", and sort-by-date for monitoring runs. Region values are verified against HeadHunter's own region list before the run starts — an unrecognised region is reported as an error instead of quietly returning nationwide results.
- **Stable JSON output** suitable for pipelines, databases and spreadsheets, with automatic retries built in.
- Runs on Apify's schedule; export to JSON, CSV or Excel.

### How it works

1. You give it one or more search keywords (Russian or English), plus any filters you want — region, salary, schedule, how recently the ad was posted.
2. It runs each keyword as its own search and walks through the result pages, collecting every distinct vacancy until it reaches your limit or the site runs out of results.
3. For each vacancy it optionally opens the full ad to add the complete description, key skills and employer details.
4. You can also hand it specific vacancy URLs or ids to scrape directly, skipping search entirely — the two modes can be combined in one run.
5. Everything lands in one dataset: a summary row per search, then one row per vacancy.

No scrapers, browsers, or blocks to babysit.

### Input

```json
{
  "site": "hh.ru",
  "keywords": ["python"],
  "areas": ["1"],
  "maxItemsPerQuery": 100,
  "includeVacancyDetails": true,
  "searchFields": [],
  "experience": "",
  "employment": [],
  "schedule": ["remote"],
  "searchPeriod": "",
  "onlyWithSalary": false,
  "orderBy": "publication_time",
  "vacancyUrls": ["https://hh.ru/vacancy/136131345"],
  "maxConcurrency": 4,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}
```

| Field | Type | Description |
|---|---|---|
| `site` | string | Which portal to read: `hh.ru` (Russia), `hh.kz` (Kazakhstan), `hh.uz` (Uzbekistan), `rabota.by` (Belarus). All four share one index, so this sets the site context (locale, currency, vacancy URLs) — use `areas` to actually filter by country. |
| `keywords` | array | One search per entry; each gets its own summary row. Russian or English. Leave empty to browse everything matching your filters. |
| `areas` | array | Region ids or names: `113` Russia, `1` Moscow, `2` Saint Petersburg, `40` Kazakhstan, `160` Almaty, `159` Astana, `97` Uzbekistan, `2759` Tashkent, `16` Belarus, `1002` Minsk. Names as HeadHunter spells them (`Алматы`) work too. |
| `vacancyUrls` | array | Scrape specific ads directly. Full URL (`https://hh.ru/vacancy/136131345`) or bare id. Can be combined with a keyword search. |
| `maxItemsPerQuery` | integer | Stop after this many vacancies per search. `0` = unlimited (up to the site's own 2000-per-search ceiling). |
| `includeVacancyDetails` | boolean | Fetch each ad's full text and employer details (one extra request per vacancy). Turn off for a fast listing-only crawl. |
| `searchFields` | array | Match the keyword only in `name` (title), `company_name`, or `description`. Empty = search everywhere. |
| `experience` | string | `noExperience`, `between1And3`, `between3And6`, `moreThan6`. |
| `employment` | array | `full`, `part`, `project`, `volunteer`, `probation`. |
| `schedule` | array | `fullDay`, `shift`, `flexible`, `remote`, `flyInFlyOut`. |
| `searchPeriod` | string | Only ads posted in the last `1`, `3`, `7` or `30` days. |
| `onlyWithSalary` | boolean | Skip ads that don't state pay. |
| `salary` | integer | Minimum salary, in the site's own currency. |
| `orderBy` | string | `relevance`, `publication_time`, `salary_desc`, `salary_asc`. |
| `maxConcurrency` | integer | Requests in flight at once (1–16). |
| `proxyConfiguration` | object | Residential recommended for scheduled runs. |

### Output

#### Summary row — one per search

```json
{
  "_input": "hh.ru | text='python' | area=Москва",
  "_source": "S1-search-state",
  "_scrapedAt": "2026-08-12T16:44:20Z",
  "recordType": "SEARCH_SUMMARY",
  "site": "hh.ru",
  "siteName": "Russia (hh.ru)",
  "totalResults": 1312,
  "returnedCount": 2,
  "pagesFetched": 1,
  "areasApplied": [
    { "input": "1", "id": "1", "name": "Москва", "status": "validated" }
  ],
  "resultCap": 2000,
  "resultCapReached": false,
  "requestParams": [
    { "key": "page", "value": "0" },
    { "key": "items_on_page", "value": "100" },
    "... 3 more"
  ]
}
```

| Field | Type | Description |
|---|---|---|
| `totalResults` | integer | How many vacancies HeadHunter says match the search. |
| `returnedCount` | integer | How many this run actually collected. |
| `pagesFetched` | integer | Result pages read. |
| `areasApplied` | array | Each requested region, its resolved id and name, and whether it was `validated` (checked against HeadHunter's region list) or `unverified`. |
| `resultCap` / `resultCapReached` | integer / boolean | The site serves at most 2000 results per search; `resultCapReached` is `true` when more matches exist than can be paged through. Narrow the search to reach the rest. |
| `_warning` | string | Present when something needs your attention, e.g. the 2000 ceiling was hit. |

#### Vacancy row — one per job

```json
{
  "_input": "hh.ru | text='python' | area=Москва",
  "_source": "S1-search-state+S2-vacancy-detail",
  "_scrapedAt": "2026-08-12T16:44:20Z",
  "recordType": "VACANCY",
  "site": "hh.ru",
  "vacancyId": "131031614",
  "vacancyUrl": "https://hh.ru/vacancy/131031614",
  "searchContext": { "keyword": "python", "page": 0, "rank": 1 },
  "name": "Cпециалист по автоматизации технических процессов",
  "company": {
    "id": 9498112,
    "name": "Яндекс Крауд",
    "visibleName": "Яндекс Крауд: Бэк-офис",
    "accreditedITEmployer": false,
    "@trusted": true
  },
  "compensation": {
    "from": 78000, "to": 78000, "currencyCode": "RUR", "gross": false, "mode": "MONTH"
  },
  "area": { "@id": 1, "name": "Москва", "path": ".113.232.1." },
  "publicationTime": { "@timestamp": 1786440622, "$": "2026-08-11T12:30:22.769+03:00" },
  "@workSchedule": "remote",
  "workFormats": [{ "workFormatsElement": ["REMOTE"] }],
  "workScheduleByDays": [{ "workScheduleByDaysElement": ["FIVE_ON_TWO_OFF"] }],
  "workingHours": [{ "workingHoursElement": ["HOURS_8"] }],
  "workExperience": "between1And3",
  "employmentForm": "FULL",
  "responsesCount": 0,
  "totalResponsesCount": 2616,
  "links": {
    "desktop": "https://hh.ru/vacancy/131031614",
    "mobile": "https://m.hh.ru/vacancy/131031614"
  },
  "vacancyDetails": {
    "vacancyId": 131031614,
    "name": "Cпециалист по автоматизации технических процессов",
    "description": "<p>Откликайтесь, если самостоятельно писали код и составляли SQL-запросы, увлечены технологиями и хотите строить карьеру в динамичной IT-отрасли</p> <p><strong>Какие задачи вас ждут</strong></p> <ul> <li> <p>Создавать и дорабатывать технические процессы, используя Groovy, Python и внутренние инструменты</p> </li> ...",
    "publicationDate": "2026-08-11T12:30:22.769+03:00",
    "workFormats": ["REMOTE"],
    "keySkills": null,
    "address": { "mapData": null, "metroStations": null }
  }
}
```

| Field | Type | Description |
|---|---|---|
| `vacancyId` / `vacancyUrl` | string | Id and canonical link for the ad. |
| `name` | string | Job title. |
| `company` | object | Employer: id, name, display name, logos, IT-accreditation flag, trusted flag. |
| `compensation` | object | Salary range, currency, whether it's gross or net, and the period (`MONTH`, shift, etc.). Absent or `noCompensation` when pay isn't stated. |
| `area` | object | Region id, name, and its position in HeadHunter's region tree. |
| `publicationTime` | object | When the ad was published, as a timestamp and an ISO date. |
| `workFormats`, `workScheduleByDays`, `workingHours`, `workExperience`, `employmentForm` | mixed | Remote/on-site, shift pattern, hours per day, required experience, employment type. |
| `responsesCount` / `totalResponsesCount` | integer | How many people have applied — useful as a competition signal. |
| `searchContext` | object | Which keyword, page and rank this row came from. Absent in direct-URL mode. |
| `vacancyDetails` | object | The full ad: complete HTML `description`, `keySkills`, `publicationDate`, address with metro stations, employer branding, and ~60 more fields. `null` when `includeVacancyDetails` is off. |

Rows are passed through with HeadHunter's own field names, so new fields upstream flow straight into your dataset instead of being dropped.

#### Error row

Every input produces at least one row. Failures are reported, never silently skipped:

```json
{
  "_input": "https://hh.ru/vacancy/1",
  "_source": "none",
  "_scrapedAt": "2026-08-12T16:41:52Z",
  "recordType": "ERROR",
  "site": "hh.ru",
  "_error": "not_found",
  "_errorDetail": "vacancy archived or removed"
}
```

### Notes and limits

- **2000 results per search, set by the site itself.** Any search reporting more matches than that hits the ceiling — the summary row flags it in `resultCapReached` and `_warning`. Split by region, by `searchPeriod`, or by narrower keywords to get the rest.
- **Choosing a site does not filter by country.** All four portals share one index, so `hh.kz` alone still returns Russian vacancies. Use `areas` for real country/city filtering.
- **Unknown regions are refused, not guessed.** HeadHunter answers an unrecognised region id with a normal-looking page of *unfiltered* results, so this actor checks every region up front and returns an `invalid_area` error instead of shipping nationwide data labelled as a city search.
- **Vacancies expire.** Ads archived between the search and the detail fetch are marked with a `_detailError` on that row; the rest of the run is unaffected.
- **HeadHunter mixes a few sponsored placements into results.** Most are ordinary job ads and are returned normally. The occasional promotional slot that isn't a job at all is marked `not_a_vacancy` on its row instead of being passed off as a vacancy.
- Residential proxy is recommended for scheduled runs.

# Actor input Schema

## `site` (type: `string`):

Which regional HeadHunter portal to read. All four share one search index, so this does NOT restrict results to that country — it sets the site context (locale, currency, vacancy URLs). To actually filter by country or city, use Regions below.

## `keywords` (type: `array`):

One search per entry — each keyword runs as its own query and gets its own SEARCH\_SUMMARY row. Russian or English both work. Leave empty to browse every vacancy (optionally narrowed by Regions and the filters below).

## `areas` (type: `array`):

Region ids to filter by, e.g. 113 = Russia, 1 = Moscow, 2 = Saint Petersburg, 40 = Kazakhstan, 160 = Almaty, 159 = Astana, 97 = Uzbekistan, 2759 = Tashkent, 16 = Belarus, 1002 = Minsk. A region name as HeadHunter spells it (e.g. Алматы) also works. Every value is checked against HeadHunter's own region dictionary before the run starts, and a query with an unknown region is refused rather than silently returning nationwide results.

## `vacancyUrls` (type: `array`):

Scrape specific vacancies directly, skipping search entirely. Accepts a full vacancy URL (https://hh.ru/vacancy/136131345) or a bare numeric vacancy id. Can be combined with a keyword search in the same run.

## `maxItemsPerQuery` (type: `integer`):

Stop paginating a query after this many vacancies. Set to 0 for unlimited — note that HeadHunter itself serves at most 2000 results per query no matter how many matches exist, so unlimited means 'up to 2000'. Narrow by region, period or keyword to reach the rest.

## `includeVacancyDetails` (type: `boolean`):

Fetch the complete ad (full HTML description, key skills, employer details, exact address, publication date) for every result via one extra request per vacancy. Turn this off for a fast listing-only crawl — search results already carry title, employer, salary, region, work schedule and the vacancy URL.

## `searchFields` (type: `array`):

Restrict where the keyword is matched. Leave empty to search everywhere.

## `experience` (type: `string`):

Required work experience.

## `employment` (type: `array`):

Employment types to include. Leave empty for all.

## `schedule` (type: `array`):

Work schedules to include, e.g. pick 'Remote' for remote-only. Leave empty for all.

## `searchPeriod` (type: `string`):

Only vacancies published in the last N days. Useful for scheduled runs that should pick up new postings only.

## `onlyWithSalary` (type: `boolean`):

Skip ads that do not state pay.

## `salary` (type: `integer`):

Minimum salary in the site's own currency (RUB on hh.ru, KZT on hh.kz, UZS on hh.uz, BYN on rabota.by). Leave empty for no minimum.

## `orderBy` (type: `string`):

Result ordering. 'Publication date' is the right choice for monitoring runs.

## `maxConcurrency` (type: `integer`):

Upper bound on requests in flight at once, across search paging and vacancy-detail fetches. This is the main speed control here: hh pages are heavy (~2s each), so a run with details is dominated by request latency. Measured on 20 vacancies — 4 gave 13.0s, 8 gave 8.5s, and 12 gave no further gain while worsening the slowest requests. Lower it if you start seeing errors in the log.

## `proxyConfiguration` (type: `object`):

Apify Proxy on the shared datacenter pool. This is the default because it is included in your plan at no extra cost and this target works through it. If you start seeing blocks, challenges or empty results, switch the group here to Residential -- it uses real consumer IPs and gets through more, but Apify bills residential traffic per gigabyte, so leave it off unless you need it.

## Actor input object example

```json
{
  "site": "hh.ru",
  "keywords": [
    "python"
  ],
  "areas": [
    "1"
  ],
  "vacancyUrls": [],
  "maxItemsPerQuery": 100,
  "includeVacancyDetails": true,
  "searchFields": [],
  "experience": "",
  "employment": [],
  "schedule": [],
  "searchPeriod": "",
  "onlyWithSalary": false,
  "orderBy": "",
  "maxConcurrency": 8,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `items` (type: `string`):

One row per scraped record. See the dataset's default view for field definitions.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "python"
    ],
    "areas": [
        "1"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/hh-jobs-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": ["python"],
    "areas": ["1"],
}

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/hh-jobs-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "python"
  ],
  "areas": [
    "1"
  ]
}' |
apify call scrapyx/hh-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapyx/hh-jobs-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/sexJVfz2yiQBxGBah/builds/JEuNcjwJgWWENeu5l/openapi.json