# Rozetka Products Scraper (`scrapyx/rozetka-products-scraper`) Actor

Product listings from Rozetka, Ukraine's largest online retailer: title, brand, price in UAH with its validity date, stock status, rating and review count. Reads the category page's own structured data, so recommendation rails are excluded rather than scraped as results.

- **URL**: https://apify.com/scrapyx/rozetka-products-scraper.md
- **Developed by:** [Ibnu Adzim](https://apify.com/scrapyx) (community)
- **Categories:** E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.56 / 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

## Rozetka Products Scraper (Ukraine)

Product listings from **Rozetka**, Ukraine's largest online retailer — as
structured rows: title, brand, price in UAH with its validity date, stock
status, rating and review count.

***

### The two things that quietly break a Rozetka crawl

**Past page 100 it re-serves, it does not stop.** Measured by comparing each
page's product ids against the page before it:

| Page | Result |
| --- | --- |
| 98, 99, 100 | 60 products, all new |
| 101, 105, 120, 200 | 60 products, **identical to page 100** |

No 404, no empty page, no flag. A crawler that treats "a full page means there
is more" will run to whatever `maxPages` it was given, collect the same 60
products over and over, and report a large successful run. This Actor caps at
page 100 *and* deduplicates by product id, so a page that adds nothing new ends
the run with `stoppedReason: no_new_products`.

**The page links to more products than it lists.** A category page carries 60
structured `ItemList` entries but **73–95 distinct `/p<id>/` links**, and the
surplus changes from page to page. Those extras are cross-sell and
recommendation rails carrying products from *other categories entirely*.
Sweeping links would contaminate a category dataset by a varying amount per
page. Rows come from the structured list only.

***

### What you get

One `CATEGORY_SUMMARY` row per category, then one `PRODUCT` row per item.

| Group | Fields |
| --- | --- |
| Identity | `productId`, `productUrl`, `title`, `description`, `brand` |
| Price | `price`, `currency`, `priceValidUntil` |
| Availability | `availability`, `inStock` |
| Reception | `ratingValue`, `reviewCount` |
| Media | `imageUrls` |
| Provenance | `_input`, `_source`, `_scrapedAt`, `pageFound`, `positionInPage`, `raw` |

**`priceValidUntil`** is Rozetka's own published price-validity date, which is
genuinely useful when comparing one run against a later one.

The summary row reports **`upstreamCategoryTotal`** beside
**`reachableCeiling`**. The notebooks category announces 211,766 products;
paging reaches 6,000 of them. The count is not a lie about the catalogue — it
is a lie about what you can retrieve, by a factor of about 35. To get more,
narrow to a sub-category or a producer rather than paging deeper.

***

### Example input

```json
{
  "categoryUrls": [
    "https://rozetka.com.ua/notebooks/c80004/",
    "https://rozetka.com.ua/mobile-phones/c80003/"
  ],
  "maxPages": 50
}
```

Paste category URLs straight from the site. Producer-filtered category URLs
work too, because Rozetka expresses those as path segments.

***

### Why there is no keyword search or sort input

That is a policy decision, not an omission. Rozetka's `robots.txt` says:

```
Disallow: /*?*          any URL with a query string
Disallow: */search/     keyword search
Disallow: /*sort=*      re-sorting
Allow:    /api/*/*
```

So keyword search and sorting are closed, and nothing may carry a query
string. Category browsing works because Rozetka paginates and filters through
**path** segments (`/notebooks/c80004/page=2/`, `/producer=asus/`), which are
allowed. Any URL you pass carrying a query string, a `/search/` path or a
`sort=` segment is refused **before a request is made** rather than sent and
regretted.

***

### How it works

HTTP-only. No browser, no login, no API key.

Category pages are server-rendered with their results published as schema.org
JSON-LD, which is where every field above comes from.

The TLS profile pool is an **allowlist**, not a preference: on the same URL in
the same minute, five fingerprints receive a 1.45 MB page and `edge101`
receives a 5 KB `403`. Only verified-passing profiles are in the rotation, so a
retry can never rotate into a guaranteed block.

# Actor input Schema

## `categoryUrls` (type: `array`):

Rozetka category pages, e.g. https://rozetka.com.ua/notebooks/c80004/ . Each runs separately with its own summary row. Producer-filtered category URLs work too, since Rozetka expresses those as path segments. URLs carrying a query string, a /search/ path or a sort= segment are refused before any request - Rozetka's robots.txt disallows all three.

## `maxPages` (type: `integer`):

Pages of 60 products. Capped at 100 because past that Rozetka re-serves page 100 verbatim rather than stopping - a higher value would collect the same products repeatedly and report a large successful run.

## `maxItems` (type: `integer`):

Optional overall cap on product rows. Summary rows are always emitted and do not count against it.

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

Parallel requests across categories.

## `minRequestInterval` (type: `integer`):

Spacing between request starts, to stay polite.

## `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
{
  "categoryUrls": [
    "https://rozetka.com.ua/notebooks/c80004/"
  ],
  "maxPages": 5,
  "maxConcurrency": 2,
  "minRequestInterval": 2,
  "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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/rozetka-products-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/rozetka-products-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 '{}' |
apify call scrapyx/rozetka-products-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapyx/rozetka-products-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/ZeUsdfbFlUDWIMQhb/builds/0zaaBpJ9es9byNbIs/openapi.json