Complete Guide: How to Scrape robota.ua Jobs Using Python
Run the robota.ua Scraper Apify Actor from Python and turn robota.ua keyword searches into structured vacancy rows with optional full descriptions.

This complete guide shows how to scrape Ukrainian job vacancies from robota.ua using Python and the robota.ua Scraper Apify Actor (reventadata/robota-ua-scraper), returning one structured row per vacancy with title, employer, city, stated salary bounds, skills, schedule, contacts and posting timestamp.
robota.ua is a Ukrainian job board. Running the Actor on Apify handles pagination for you.
By the end of this guide you will know every input field, how post-fetch filters behave, what the 42 output fields contain, how to handle zero-row or partial runs via the API, and how to schedule recurring runs. Prerequisites are minimal: Python 3.11 or newer, an Apify account and an API token. Every output line and sample row comes from a real 20-row run on 14 November 2026.
TL;DR
Drive reventadata/robota-ua-scraper from Python with apify-client, send a search (searchQueries, maxItems, maxPages, includeDetails and optional filters), and read structured vacancy rows from the default dataset. See the robota.ua Scraper Store page.
Prerequisites and setup
You need Python 3.11 or newer, a free Apify account and your personal API token. Apify accounts can be created with an email address or a GitHub login. Apify Console is the web workspace where you manage Actors, runs, schedules and datasets; copy your API token from Settings > API & Integrations.
Install the official 3.x Python client and export your token in your shell:
pip install -U "apify-client~=3.0"
export APIFY_API_TOKEN="your_apify_token_here"
The client reference lives in the Apify API client for Python docs. You do not need any local setup: all requests execute inside the cloud Actor run.
Understanding robota.ua Scraper
The Actor reads robota.ua's public vacancy listings, and the vacancy details when includeDetails is enabled, walking pages of 20 vacancies per keyword.
Each saved row has 42 fields: 24 list and run metadata fields (id, url, title, company, location, salaryFrom, salaryTo, snippet, postedText, publicationType, benefits, applyUrl and more) plus 18 detail fields (postedAt, plain-text description, address, district, metro, coordinates, category, schedules, isRemote, skills, published contacts and company mini-profile fields).
Key limitations to know up front: city, salary bounds and keyword filters are applied to the fetched vacancies, so strict filters drop rows without reducing page fetches. The API returns no currency field on salaries, and robota.ua's terms forbid unlawful personal-data collection or interfering with normal site operation.
Step-by-step walkthrough
Step 1: Open the Actor
Go to the robota.ua Scraper page on Apify Store and click Try for free to open the input form in Apify Console, or reference reventadata/robota-ua-scraper directly in Python.
Step 2: Configure input parameters
Console and API share these JSON keys:
| Field | Type | Behaviour |
|---|---|---|
searchQueries |
array | Job titles or keywords, one search per term. Empty lists the site's default-ranked vacancies across all topics. |
maxItems |
integer | Total vacancies saved across all queries (default 100, minimum 1). |
maxPages |
integer | Pages walked per query, 20 items each (default 10, range 1–500). |
includeDetails |
boolean | Opens each kept vacancy page for the 18 detail fields (default false). |
city |
string | Case- and accent-insensitive substring match against location. |
minSalary, maxSalary, onlyWithSalary |
integer / boolean | Filters on salaryFrom and salaryTo; drops vacancies with no stated salary. |
includeKeywords, excludeKeywords |
array | Case- and accent-insensitive substring matches across title, company and snippet (for example, "python" also matches "pythonista"). |
proxyConfiguration |
object | Apify Proxy enabled by default. |
Example multi-term Kyiv search requiring a stated minimum salary of 60000:
{
"searchQueries": ["python", "data engineer"],
"city": "Київ",
"onlyWithSalary": true,
"minSalary": 60000,
"maxItems": 40,
"maxPages": 3
}
Step 3: Run the Actor from Python
Call reventadata/robota-ua-scraper for "python" with details enabled:
import os
from apify_client import ApifyClient
# 1. Initialise the client with your token from the environment
client = ApifyClient(os.environ["APIFY_API_TOKEN"])
# 2. Describe the search: "python" vacancies with full detail pages
run_input = {
"searchQueries": ["python"],
"maxItems": 20,
"maxPages": 2,
"includeDetails": True,
}
# 3. Start the Actor and wait for it to finish
run = client.actor("reventadata/robota-ua-scraper").call(run_input=run_input)
if run is None or run.status != "SUCCEEDED":
status = run.status if run else "unknown"
raise SystemExit(f"Run did not succeed (status: {status}).")
# 4. Read the rows from the run's default dataset
items = client.dataset(run.default_dataset_id).list_items().items
print(f"Retrieved {len(items)} vacancies.\n")
# 5. Print two lines per vacancy
for item in items:
salary_from, salary_to = item.get("salaryFrom"), item.get("salaryTo")
if salary_from is not None and salary_to is not None:
salary = f"{salary_from}-{salary_to}"
elif salary_from is not None:
salary = f"from {salary_from}"
elif salary_to is not None:
salary = f"up to {salary_to}"
else:
salary = "not stated"
remote = "remote" if item.get("isRemote") else "on-site/hybrid"
print(f"{item['title']} | {item.get('company') or 'anonymous'} | {item.get('location')} | salary: {salary} | {remote}")
print(f" category: {item.get('category')}, posted: {item.get('postedText')}")
Step 4: Examine the printed output
The cited 14 November 2026 run finished in 11.5 seconds and saved 20 vacancies (18 from page 1 and 2 from page 2). Here are the first five entries printed by the script:
ВІ аналітик | Дарниця, Фармацевтична компанія | Київ | salary: not stated | on-site/hybrid
category: Фармацевтика, posted: 3 години тому
AppSec Engineer (Application Security Engineer) | robota.ua | Київ | salary: not stated | remote
category: IT, posted: 23 години тому
Middle QA Engineer (ML / AI & Data) | robota.ua | Київ | salary: not stated | remote
category: IT, posted: 1 день тому
Провідний фахівець з HR-систем, автоматизації та аналітики | UNIQA, Страхова компанія | Київ | salary: not stated | on-site/hybrid
category: Страхування, posted: 1 день тому
Менеджер/Менеджерка з моделювання та планування продуктів зі зниженим ризиком / Бізнес-аналітик | JTI / Japan Tobacco International | Київ | salary: not stated | on-site/hybrid
category: FMCG, posted: 1 день тому
Notice that company can be null on anonymous listings (1 of the 20 rows), so the script uses item.get("company") or "anonymous" to keep formatting clean.
Step 5: Inspect a complete row
Here is one full 42-field row copied verbatim from that 14 November 2026 run:
{
"id": "11400591",
"url": "https://robota.ua/company15469395/vacancy11400591",
"title": "Data Scientist (LLM/AI)",
"company": "NDA Recruitment",
"companyId": "15469395",
"companyLogo": "https://company-logo-frankfurt.rabota.ua/15469395_20250619204422.png",
"location": "Київ",
"cityId": "1",
"scheduleIds": [
"8",
"1"
],
"salaryFrom": 121500,
"salaryTo": 150000,
"salaryComment": null,
"snippet": "Про нас:Ми — одна з найбільших українських MilTech-компаній. Активно впроваджуємо AI-рішення для оптимізації та автоматизації внутрішніх бізнес-процесів. Розширюємо нашу LLM & AI команду і шукаємо людину, яка не просто запускає ChatGPT через API, а г...",
"postedText": "2 дні тому",
"isHot": false,
"isActive": true,
"isAnonymous": false,
"publicationType": "PROFESSIONAL",
"benefits": [
"Бронювання співробітників"
],
"applyUrl": null,
"matchedKeyword": "python",
"page": 1,
"detailFetched": true,
"postedAt": "2026-11-12T03:01:00.027000+02:00",
"description": "Про нас:\nМи — одна з найбільших українських MilTech-компаній. Активно впроваджуємо AI-рішення для оптимізації та автоматизації внутрішніх бізнес-процесів. Розширюємо нашу LLM & AI команду і шукаємо людину, яка не просто запускає ChatGPT через API, а готова створювати надійні продуктові ML-рішення.\nЩо треба буде робити:\n- Проєктувати промпти, структуру контексту та будувати нормальні RAG-системи (chunking, retrieval, reranking).\n- Розробляти агентні системи з tool use та валідацією виходів.\n- Будувати пайплайни evaluation (golden datasets, метрики, LLM-as-judge) перед релізом, щоб моделі не галюцинували в найвідповідальніший момент.\n- Проводити fine-tuning (за потреби), писати чистий production-код на Python та дбати про безпеку рішень (guardrails, injection-тести).\nНаші очікування від кандидата:\n- 3+ роки досвіду в DS/ML, з них від 1 року — практична робота з LLM у реальних продакшн-проєктах.\n- Досвід побудови RAG або агентних систем своїми руками (і розуміння, чому саме такі архітектурні рішення були обрані).\n- Практика evaluation: збір golden datasets, вибірка метрик і відстеження деградацій.\n- Впевнений Python (тести, рев'ю, структура сервісу) та вміння пояснити складні технічні речі нетехнічним стейкхолдерам.\nЧому варто долучитися:\nТут немає нудних пет-проєктів заради слайдів. Ваші рішення матимуть реальний вплив на внутрішні процеси та допоможуть наближати перемогу України.\nЗацікавила вакансія?",
"address": null,
"district": null,
"metro": null,
"latitude": 50.4500351,
"longitude": 30.5241356,
"category": "HR",
"schedules": [
"гібридна",
"повна зайнятість"
],
"isRemote": false,
"skills": [
"Мова програмування python",
"Machine Learning Engineer",
"Дата Саєнтист",
"Дата Майнинг",
"Середній розробник Python"
],
"contactName": "Вікторія Н.",
"contactPhones": [],
"contactSocials": [
"viktoriia.n@nda.in.ua"
],
"companyVerified": true,
"companyFoundedYear": null,
"companySize": "від 20 до 50",
"companyBenefits": [
"Їжа в офісі",
"Офіційне працевлаштування згідно КЗпП України",
"Повністю офіційна зарплата"
],
"scrapedAt": "2026-11-14T14:45:19+00:00"
}
Step 6: Export the dataset
Datasets export as JSON, CSV, XML, Excel, HTML table, RSS or JSONL from Apify Console or through the API with a format option (dataset docs). The dataset schema also defines an overview table showing title, company, location, salaryFrom, salaryTo, postedText, matchedKeyword and url.
Working with the API
The Python client returns a typed Run object from client.actor("reventadata/robota-ua-scraper").call(...), so read run.status and run.default_dataset_id as attributes rather than dictionary keys, and guard against run is None before reading dataset results. Store APIFY_API_TOKEN in your shell environment rather than hard-coding secrets inside source files, and use ApifyClientAsync when integrating the Actor into an asyncio service so your worker stays non-blocking.
For asynchronous pipelines, attach an Apify webhook on ACTOR.RUN.SUCCEEDED or ACTOR.RUN.FAILED. The webhook payload's resource object matches the response of the Get Actor run endpoint (webhook docs), so it includes defaultDatasetId and status, letting your downstream service fetch items through client.dataset(default_dataset_id).list_items().items without running polling loops.
For recurring sweeps, save your input JSON as an Apify task and attach a schedule using a standard cron expression, sizing maxPages to match how often vacancies appear. Always verify run.status before reading rows and inspect run logs in Apify Console when troubleshooting or auditing Skipped filter totals. Zero-row runs finish SUCCEEDED with a status message when pages load with zero matches, or FAILED when input bounds fail (maxItems < 1, maxPages < 1, minSalary > maxSalary) or pages fail or get blocked. On any non-zero partial run where retries run out of time, saved rows stay in the default dataset with a warning logged.
Advanced usage patterns
Multi-keyword deduplication. Pass a list of related terms in searchQueries (["python", "data engineer", "ml engineer"]). Each keyword walks up to maxPages, and vacancy id values already stored earlier in the run are skipped and tallied in the log so your dataset never contains duplicate entries. Because deduplication occurs only after a vacancy passes every filter and is pushed, a near-miss skipped by one keyword can still match a broader query later in the same run.
Two-pass enrichment. Run first with includeDetails: false to scan many pages quickly (one GraphQL request per 20 listings instead of 21 requests when full details are enabled), inspect salaryFrom, location, scheduleIds or snippet locally, and run includeDetails: true only on targeted searches where you need full description, postedAt, address, coordinates or skills.
Handling open-ended and missing salaries. In robota.ua, 0 means unset and becomes null in the dataset. An open-ended "from X" offer leaves salaryTo as null (75000 with salaryTo: null in the sample run), which passes any minSalary filter check because no upper ceiling is set.
Incremental tracking. Persist id and postedAt as your composite key in a database between scheduled runs to detect newly published, edited or republished vacancies reliably without parsing relative postedText labels.
Understanding your data
The 20 rows from the 14 November 2026 run show how real robota.ua listings populate the 42-field schema and why checking for null values matters before aggregating or filtering results:
- Salaries are sparse. Only 2 of 20 vacancies stated a salary (
121500–150000and75000open-ended), while 18 hadsalaryFrom,salaryToandsalaryCommentallnull. - Remote vs city. All 20 rows carried
location: "Київ", yet 5 hadisRemote: true(from"віддалена робота"inschedules) and 15 hadisRemote: false. - Anonymous and unverified employers. 1 of 20 rows was anonymous (
isAnonymous: true,company: null), and 17 of 20 hadcompanyVerified: true(3 hadcompanyVerified: false). - Contacts and categories.
contactNamewas present on 14 of 20 rows,contactSocialson 3 of 20 rows,contactPhoneson 1 of 20 rows and an externalapplyUrlon 1 of 20 rows. Categories spannedБанки(4),IT(3),HR(3),Фармацевтика(2),Страхування(2),Оборонна промисловість(2),Фінансові послуги(2),FMCG(1) andПромисловість та Виробництво(1).
Troubleshooting guide
Run succeeded with zero rows. robota.ua responded with totalCount: 0 or post-fetch filters dropped every candidate. Check the status message and the Skipped N: reason summary lines in client.log(run.id).get(), then broaden searchQueries, widen city, raise maxPages or remove onlyWithSalary.
Run failed with zero rows. Either maxItems or maxPages was below 1, minSalary exceeded maxSalary, or every list page was blocked or returned an unexpected JSON shape. If a run stopped after saving some rows, the Actor keeps those partial rows and logs a warning instead of failing. When blocked, check proxyConfiguration.
Detail fields are null on a row. Either includeDetails was false, the vacancy disappeared before its detail page was fetched, or its detail request failed after retries; the Actor keeps the 24 list fields rather than dropping the row.
Support. Inspect the run log in Apify Console or fetch it via client.log(run.id).get(), and reach out through the Actor's Store page if a site layout change triggers repeated block errors.
Best practices
Keep test runs small (maxPages: 1 or 2, maxItems: 20) while verifying your downstream parser, and keep includeDetails off when list fields suffice because enabling it adds one HTTP request per saved vacancy. Never treat null salary, company or address fields as empty zeros, store id as a string primary key for deduplication across runs, and keep in mind that city, salary bounds and keyword filters run post-fetch after list pages are downloaded.
For automated pipelines, export JSONL streams or read items via list_items().items, check run.status before consuming rows, and ensure your collection and storage of published contact fields comply with robota.ua's terms and data-protection law.
Conclusion and next steps
You now have a tested Python workflow to run reventadata/robota-ua-scraper, inspect its 42-field rows, handle sparse fields, and schedule updates. Share what you build!
For current pricing and details, see the Store page.
Resources
- robota.ua Scraper on Apify Store
- Apify API client for Python
- Apify datasets
- Apify schedules
- Apify webhooks
About the author: reventadata builds and publishes data extraction Actors on the Apify Store.
About the author
- Hi, I'm the engineer behind ReventaData. I build pay-per-event Apify Actors that turn public marketplace, classifieds, jobs and real-estate sites into clean, reliable datasets. Here on Hashnode, I share practical tutorials on collecting structured web data with Python and Apify, and on putting it to work: price tracking, lead lists and market analysis. Explore our turnkey scrapers: https://apify.com/reventadata
Comments
Join the discussionNo comments yet. Be the first to comment.




