# Ozon Search Scraper — Prices, Ratings & Reviews (`thenetaji/ozon-search-scraper`) Actor

Search Ozon, Russia's largest marketplace, for any product or brand. Every product returns its price, any discount, star rating and review count as numbers. Switch on enrichment and each one also carries the seller, the price paid without an Ozon card, the full spec table and every image.

- **URL**: https://apify.com/thenetaji/ozon-search-scraper.md
- **Developed by:** [The Netaji](https://apify.com/thenetaji) (community)
- **Categories:** E-commerce, Business, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

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

## Ozon Search Scraper

The Actor searches Ozon, Russia's largest marketplace, for a product name or brand and returns the
matching products as structured rows: `sku`, `title`, `url`, `image_url`, `price`, `original_price`,
`currency`, `on_sale`, `percent_discount`, `rating`, `review_count` and `is_adult`.

Prices and ratings arrive as numbers. Ozon renders them for a Russian storefront — `194 632 ₽`, with
a no-break space between the thousands and a currency glyph rather than a code — and those strings
are parsed before they reach the dataset, so `price` is `194632` and `currency` is `RUB`.

### Accepted input

`keyword` is required and is the product name or brand to search for. `maxItems` caps how many
products are saved and defaults to 100; setting it to `0` removes the cap and lets the run continue
to the end of the listing.

```json
{
  "keyword": "iphone",
  "maxItems": 24
}
```

### Response fields

```json
{
  "sku": 3755501937,
  "title": "Apple Смартфон iPhone 17 Pro Max Global 12/1 ТБ, темно-синий",
  "url": "https://www.ozon.ru/product/apple-smartfon-iphone-17-pro-max-3755501937/",
  "image_url": "https://ir.ozone.ru/s3/multimedia-1-4/8542532020.jpg",
  "price": 194632,
  "original_price": 1083750,
  "currency": "RUB",
  "on_sale": true,
  "percent_discount": 82,
  "rating": 4.7,
  "review_count": 128,
  "is_adult": false
}
```

Fields absent from the listing are returned as null rather than omitted, so every row has the same
shape. A product with no rating yet returns `rating: null` and `review_count: null`; a product that
is not discounted returns `original_price: null`, `percent_discount: null` and `on_sale: false`.

`sku` is Ozon's own product identifier and is the stable key for a product. `url` has Ozon's
per-response tracking token removed, so the same product produces the same link on every run and can
be de-duplicated across runs by either field.

### Behaviour on a search

Ozon does not answer a search with a result set. It picks the category that best matches the words
and serves that category's listing — so a search for `iphone` resolves to the Apple smartphones
category, and the products returned are that category's, ordered as Ozon orders them.

The resolved category is printed in the run log. Pasting it into
[Ozon Category Scraper](https://apify.com/thenetaji/ozon-category-scraper) skips the resolution step
on later runs and goes straight to the listing, which is the cheaper way to take the same products
repeatedly.

### Questions

**Why did the run return fewer products than `maxItems`?**
Because the listing ran out. Ozon serves the grid in pages of eight and the Actor keeps requesting
pages until the listing reports no more, so a narrow keyword resolves to a small category and stops
there. The ceiling is 300 pages, or 2,400 products, and a category larger than that is truncated at
the ceiling rather than continuing.

**Are the products the same as searching on ozon.ru?**
They are the listing Ozon resolves the keyword to, in Ozon's own order. Sponsored placements and the
banners, filter rails and menus that surround the grid on the website are not products and are not
returned.

**Why do two runs on the same keyword differ slightly?**
Ozon re-composes the grid per request and neighbouring pages sometimes overlap, repeating a handful
of products. Duplicates are removed within a run by product URL, but Ozon's own ordering and stock
change between runs, so consecutive runs are close rather than identical.

**What happens when a run is interrupted upstream?**
Ozon challenges a minority of new sessions. A challenged request is retried on a fresh session, and
a run that still cannot get past it ends with the products it has already collected rather than
failing outright — the dataset is short, not empty.

**Why is `price` lower than the price Ozon shows me?**
It is not — it is the price Ozon shows by default, which assumes payment with an
Ozon card. The standard price is higher and appears only on a product's own
page, so it is available as `list_price` when enrichment is on. Comparing the
two is the point of having both.

**Is the Actor limited to roubles?**
The prices come from `ozon.ru` and are quoted in roubles, so `currency` is `RUB`. The currency is
read from the symbol Ozon displayed rather than assumed, so a storefront quoting tenge or dram is
reported as such rather than silently mislabelled.

### Enriching with product details

`enrichProductDetails` opens each product's own page and merges what a listing
cannot show onto its row. It is off by default, costs one extra request per
product, and is billed per product enriched — only after the lookup succeeds.

Eleven fields are added: `seller_name`, `seller_url`, `seller_id`,
`list_price`, `brand`, `description`, `in_stock`, `images`, `characteristics`,
`category_path` and `variants`.

The seller is the reason most runs turn it on. Ozon is a marketplace, several
shops sell the same product, and a listing tile names none of them — so a
listing export alone cannot answer who is selling what.

**`list_price` is the other reason, and it is easy to miss.** Ozon quotes two
live prices: the discounted price for paying with an Ozon card, and the standard
price everyone else pays. Search and category listings show only the first, so
`price` on an unenriched row understates what most buyers are charged.
`list_price` is the standard price, and `price` is left untouched so the two can
be compared rather than one silently replacing the other.

`rating` and `review_count` are taken from the product page when it has them.
A listing tile rounds the review count and frequently omits it, so the product
page is the better source for the same two fields.

A product whose page cannot be reached, or that has been delisted, keeps its
listing row unchanged and is not billed for the enrichment.

### Related Actors

[Ozon Category Scraper](https://apify.com/thenetaji/ozon-category-scraper) takes a category link
directly and exports the whole listing. It is the better choice once the category is known, because
every request buys products instead of spending one working out where to look.

# Actor input Schema

## `keyword` (type: `string`):

Product name or brand to search Ozon for.

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

Maximum number of products to save. Set 0 for no limit.

## `enrichProductDetails` (type: `boolean`):

Open every product's own page and add what a listing cannot show: the seller and their storefront, the standard price paid without an Ozon card, the brand, the full description, stock status, every gallery image, the specification table, and the other sizes and colours of the same product. One extra request per product — slower, and billed per enriched product.

## Actor input object example

```json
{
  "keyword": "iphone",
  "maxItems": 24,
  "enrichProductDetails": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

All records scraped by this run

# 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 = {
    "keyword": "iphone",
    "maxItems": 24
};

// Run the Actor and wait for it to finish
const run = await client.actor("thenetaji/ozon-search-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 = {
    "keyword": "iphone",
    "maxItems": 24,
}

# Run the Actor and wait for it to finish
run = client.actor("thenetaji/ozon-search-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 '{
  "keyword": "iphone",
  "maxItems": 24
}' |
apify call thenetaji/ozon-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thenetaji/ozon-search-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/ua6ttOS28g6OxMGJN/builds/QS7gF0g4eOfLg29rc/openapi.json