Trudvsem Russia Jobs Scraper | Работа России Вакансии

Collect Russian job vacancies from the official Trudvsem / Работа России open-data API (trudvsem.ru): job title, employer details, salary range, region, employment type, schedule, requirements, education, contacts and apply link. Filter by keyword, region or last-modified date. Pay per result (see the Pricing tab). The residential proxy is built in.

What data you get

One dataset row per vacancy (duplicates are removed by vacancy ID). Text values are returned in Russian, as published.

Field group	Fields
Identity	vacancy_id, job_title, job_url, source
Employer	company_name, company_code, company_inn, company_kpp, company_ogrn, company_email, company_url, is_hr_agency
Location	region, region_code, address, latitude, longitude, addresses (list of {location, latitude, longitude})
Compensation	salary_text, salary_min, salary_max, currency
Terms	employment_type, schedule, shift (list), term, conditions, work_places (number of openings), training_days, typical_position, work_place_type (object of flags)
Role detail	specialisation, profession_code, qualification, education, experience_years, requirements, duties, skills (list), social_protected
Contact	contact_person, contacts (list of {type, value})
Dates	created_date, modified_at
Run info	query, scraped_at, parse_confidence (0 to 1), warnings (list of data-quality notes)

Every field is always present; values the source does not publish are null or an empty list. Employer and contact fields are what the open-data source publishes for the vacancy.

How to use

1. Optionally enter keywords in Search keywords (job title, employer or duties; for example Python, водитель). Each keyword is searched separately and the results are merged. Leave it empty to browse the latest vacancies nationwide.
2. Optionally set a Region code (for example 7700000000000 for Moscow, 7800000000000 for Saint Petersburg).
3. Optionally set Modified since to an ISO date-time (for example 2026-06-20T00:00:00Z) to fetch only vacancies created or updated since your last run.
4. Set Max results. Leave Proxy configuration on the default (Apify Residential, Russia).
5. Click Start, then open the Vacancies overview table or export the dataset as JSON, CSV or Excel.

Input

Field	Type	Default	Description
searchTerms	array of strings	["Python"] (prefill)	Keywords to search. Empty = browse nationwide
regionCode	string	empty	Trudvsem region code; when set, the per-region endpoint is used
modifiedFrom	string	empty	Only vacancies created or updated on or after this UTC date-time (ISO 8601)
maxItems	integer	100	Maximum vacancies across all pages (0 = no cap). The API is read 100 vacancies per page automatically
proxyConfiguration	object	Apify Residential, country RU	Proxy settings. Russia is recommended for stable access

Example input:

{
  "searchTerms": ["Python"],
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "RU"
  }
}

Output example

Values below are illustrative.

{
  "vacancy_id": "00000000-0000-0000-0000-000000000001",
  "job_title": "Программист",
  "job_url": "https://trudvsem.ru/vacancy/card/0000000000000/00000000-0000-0000-0000-000000000001",
  "source": "Вакансия работодателя",
  "company_name": "ООО «Пример»",
  "company_code": "0000000000000",
  "company_inn": "0000000000",
  "company_kpp": "000000000",
  "company_ogrn": "0000000000000",
  "company_email": "hr@example.com",
  "company_url": "https://trudvsem.ru/company/0000000000000",
  "is_hr_agency": false,
  "region": "Москва",
  "region_code": "7700000000000",
  "address": "г Москва, ул Примерная, 1",
  "latitude": 55.75,
  "longitude": 37.61,
  "addresses": [{ "location": "г Москва, ул Примерная, 1", "latitude": 55.75, "longitude": 37.61 }],
  "salary_text": "от 90000",
  "salary_min": 90000,
  "salary_max": 140000,
  "currency": "«руб.»",
  "employment_type": "Полная занятость",
  "schedule": "Полный рабочий день",
  "shift": [],
  "term": null,
  "conditions": "Оптимальные",
  "work_places": 2,
  "training_days": 0,
  "typical_position": null,
  "work_place_type": { "workPlaceOrdinary": true, "workPlaceQuota": false },
  "specialisation": "Информационные технологии",
  "profession_code": "000000",
  "qualification": null,
  "education": "Высшее образование",
  "experience_years": 3,
  "requirements": "Опыт работы с Python от 3 лет.",
  "duties": "Разработка и поддержка внутренних сервисов.",
  "skills": [],
  "social_protected": null,
  "contact_person": "Иванова Анна",
  "contacts": [{ "type": "Телефон", "value": "+7(495) 000-00-00" }],
  "created_date": "2026-09-20",
  "modified_at": "2026-10-01T10:00:00+0300",
  "query": "Python",
  "scraped_at": "2026-10-02T09:30:00Z",
  "parse_confidence": 1.0,
  "warnings": []
}

Use cases

• Labour-market analytics: salary ranges, experience and education requirements by region and profession.
• Job aggregation: add official Russian vacancies to a job board or alert service.
• Incremental feeds: schedule runs with modifiedFrom to pull only new and changed vacancies.
• Regional research: compare demand across regions using region_code.

FAQ

Do I need an API key or my own proxy? No. The source is an open-data API that needs no key or login, and the residential proxy (Russia) is built in.

How is it priced? Pay per result. See the Pricing tab for the current price per vacancy.

How do I get only new vacancies? Set modifiedFrom to the time of your previous run. Only vacancies created or updated on or after that moment are returned.

Is there a limit for free-plan runs? Runs on a free Apify plan return a preview of up to 25 results. Paid plans have no preview limit.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.