OLX Ukraine Classifieds Scraper

Extracts published classifieds from public OLX.ua search, category, and listing pages. The runner uses bounded browser-compatible HTTP with current card and JSON-LD parsing; it does not use login, private APIs, or CAPTCHA bypasses.

Input

• startUrls: optional HTTPS URLs on olx.ua or a public subdomain. If omitted, query and location build a Ukrainian public search URL.
• query, location: optional search terms.
• maxItems, timeoutMs, maxBytes: result and request safety limits.
• maxPages, requestDelayMs, maxRequestRetries: bounded pagination and retry controls.
• fixturePath: optional checked-in local QA fixture; it never silently replaces a live request.
• userAgent, acceptLanguage: transparent HTTP preferences.
• proxyConfiguration: optional standard Apify Proxy settings. Direct requests are the default; enabled runs reuse one valid session ID, and proxy credentials never enter datasets or summaries.

Each listing record includes the public listing ID, title, description, price/currency, category, location, seller metadata, images, timestamps, attributes, and access metadata. Challenged, failed, or empty responses produce an olx-diagnostic record rather than being treated as successful data.

Local verification

npm ci --ignore-scripts --no-audit --no-fund
npm run check
apify run --purge --input-file .actor/input.json

The checked-in input performs a bounded live OLX.ua laptop search; validate-datasets.js validates all local dataset rows and checks the OUTPUT summary counts.

maxPages bounds supplied and source-discovered OLX.ua pages. Only HTTPS pagination links that remain on OLX.ua are followed, records are deduplicated across pages, and redundant raw source payloads are not emitted.

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. Public listing rows retain classified-listing fields and provenance, while access failures are emitted as minimal diagnostics.