This tutorial takes Python job vacancies from jobs.dou.ua, the Ukrainian IT jobs board, and turns them into structured rows you can read in Python. The tool is DOU.ua Jobs Scraper (reventadata/dou-ua-scraper), an Apify Actor built for this site. It reads public pages with no login.
The Actor is unofficial. It is not affiliated with, authorised by or endorsed by DOU.ua.
Every row carries the title, the company, the cities the list shows, the remote and relocation flags, a salary string when one is listed, and the date the list prints. The sample rows below come from a real run on 17 November 2026: the Python category, ten vacancies, copied as the Actor returned them.
Prerequisites
You need three things:
- Python 3 with
pip. - A free Apify account.
- Your Apify API token, stored in the
APIFY_API_TOKENenvironment variable.
Install the client:
pip install -U "apify-client~=3.0" No scraping code is needed on your side. The Actor does the fetching. Your token is read from the environment, so it never has to be typed into the script.
What you'll achieve
You will ask the Actor for ten Python vacancies, read the rows in Python and print a short summary for each one. The summary is two lines: the title, company, cities and remote flag, then the publication date as the list prints it and the salary text.
The site groups vacancies into 59 categories, from .NET to Військова справа. The same script works for any of them, and for keyword searches in searchQueries. Only the input changes. This tutorial uses no city, experience or salary filter, so every row is a Python vacancy that the list returned for that category.
Step 1: Open DOU.ua Jobs Scraper
Open the DOU.ua Jobs Scraper page on Apify Store. The Try for free button there opens the Actor in Apify Console. This tutorial calls the Actor from Python, so you only need its name, reventadata/dou-ua-scraper.
Step 2: Choose the search
The search is described by a few input fields:
-
category: optional. One of the site's 59 categories, spelled as the site spells it. Any other value is refused before the run starts. -
searchQueries: optional list of keywords. Each keyword is one search, and a vacancy found by two keywords is kept once. -
city: optional, written as the site writes it, in Ukrainian, for exampleКиїв. -
remoteandrelocation:truekeeps only the vacancies the site marks as remote, or as relocation abroad. -
experience: optional,1-3or5plus. Any other value is refused before the run starts. -
onlyWithSalary:truekeeps only vacancies that show a salary. The site cannot filter by salary, so the Actor reads each vacancy and drops the ones without one. -
fetchDetails:trueopens each vacancy's own page for the full description, the publication date with its year, the category and the keyword badges. That is one extra page per row, so the run is slower. -
maxItems: a hard cap on the number of rows.
This tutorial sets category to Python and maxItems to 10, and leaves the other flags off. The input is:
{ "category": "Python", "maxItems": 10 } Step 3: Run it from Python
This script starts the Actor, waits for it, reads the dataset and prints the vacancies:
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, ten rows run_input = { "category": "Python", "maxItems": 10, } # 3. Start the Actor and wait for it to finish run = client.actor("reventadata/dou-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: title, company, cities and remote flag, then date and salary for item in items: cities = ", ".join(item.get("cities") or []) or "no city listed" remote = "remote" if item.get("isRemote") else "not remote" print(f"{item.get('title')} | {item.get('companyName')} | {cities} | {remote}") print(f" published {item.get('publishedDateText')}, salary: {item.get('salaryText') or 'not listed'}") Keep maxItems small while you test, and raise it when the output looks right.
Step 4: Read the output
The dataset holds one row per vacancy. Two of the ten rows from this run are below, copied as the Actor returned them. The other eight have the same fields.
[ { "id": "379079", "url": "https://jobs.dou.ua/companies/newground/vacancies/379079/", "title": "AI Software Engineer — Quantum Computing Integration", "companyName": "NewGround", "companySlug": "newground", "companyUrl": "https://jobs.dou.ua/companies/newground/", "salaryText": null, "salaryFrom": null, "salaryTo": null, "salaryCurrency": null, "cities": [ "Київ" ], "isRemote": true, "isRelocation": true, "publishedDateText": "5 листопада", "isPromoted": true, "snippet": "Role Overview We are looking for a Python Developer with practical experience in AI agent development and a practical or academic background in Quantum Computing to support the integration and development of AI-driven solutions within the Quantum Computing ecosystem.", "hasSalary": false, "category": null, "categorySearched": "Python", "searchQuery": null, "publishedAt": null, "badges": null, "description": null, "detailFetched": false, "searchUrl": "https://jobs.dou.ua/vacancies/?category=Python", "scrapedAt": "2026-11-17T21:51:56Z" }, { "id": "359220", "url": "https://jobs.dou.ua/companies/solid-software/vacancies/359220/", "title": "Senior Python Developer", "companyName": "Solid Software", "companySlug": "solid-software", "companyUrl": "https://jobs.dou.ua/companies/solid-software/", "salaryText": null, "salaryFrom": null, "salaryTo": null, "salaryCurrency": null, "cities": [], "isRemote": true, "isRelocation": false, "publishedDateText": "30 жовтня", "isPromoted": true, "snippet": "We are looking for a Senior Python Developer who is ready to scale and grow with us. If you’re passionate about clean code, scalable backend architecture, and excited to build something impactful, we’d love to meet you! What will you do?", "hasSalary": false, "category": null, "categorySearched": "Python", "searchQuery": null, "publishedAt": null, "badges": null, "description": null, "detailFetched": false, "searchUrl": "https://jobs.dou.ua/vacancies/?category=Python", "scrapedAt": "2026-11-17T21:51:56Z" } ] The run ended with status SUCCEEDED after 3.6 seconds. Each row has 26 fields. In this run five of them are null on every row: category, publishedAt, badges, description and searchQuery. detailFetched is false on every row. In this run fetchDetails was off, and no keyword was set.
Understanding your results
Each row is one vacancy from the list:
-
idandurl: the vacancy number and its address on the site. -
title,companyName,companySlugandcompanyUrl: the vacancy title and the company as the list shows them. -
salaryText: the salary as the site shows it.salaryFrom,salaryToandsalaryCurrencyare filled only for dollar amounts. Any other format keeps the text and leaves the three fields empty. -
cities,isRemoteandisRelocation: the city names the card lists, and the two location flags. -
publishedDateText: the day and month as the list prints them, with no year. -
isPromoted:truewhen the card is marked as promoted. -
snippet: the short teaser text on the list card.
In this run, 8 of the 10 rows are marked remote, 2 are marked for relocation abroad and 6 are promoted. One row has a salary string. Four rows have an empty cities list.
Pro tips
- Start with
maxItemsat 10 or less, then raise it once the rows look right. - Set
categoryfor the site's own filter.city,remote,relocationandexperiencealso narrow the search, so only matching vacancies are read. - Add
searchQueriesfor keyword matches. A vacancy found by several keywords appears once in the dataset. - Turn on
fetchDetailswhen you need the description or the year of publication. Leave it off when the list fields are enough, because the run is faster. -
onlyWithSalaryremoves vacancies after they are read, so a salary-only run can read many vacancies before it reaches your row cap. - Read
publishedDateTextas text, not as a date. The list prints the day and month in Ukrainian and does not print the year. - Compare
citieswithisRemoterather than trusting either one alone. In this run three of the four rows with an emptycitieslist are marked remote.
Troubleshooting
- Zero rows and status
SUCCEEDED. A search that matches nothing ends the run as succeeded, with a message. City names must be written as the site writes them. - Status
FAILED. The input was refused, or the site refused the run. The run's log says which. - Rows stopped early. If the run clock ends the sweep after some rows, the rows already stored are kept, and the log says the sweep ended early.
- A
nullfield. Read the field list above.descriptionand the other detail fields staynullunlessfetchDetailsis on. - A salary you expected is missing. Nine of the ten rows in this run have no salary string. Check
hasSalarybefore you readsalaryFrom.
Next steps
Run the same script on a schedule with any scheduler you already use, and write each day's rows to your own store. To follow another category, change the category value in run_input.
For current pricing and details, see the Store page.
What would you search for first? Drop a comment!
About the author: reventadata builds and publishes data extraction Actors on the Apify Store.
