# eMAG Scraper - Products, Prices, Sellers & Stock (`abotapi/emag-com-scraper`) Actor

Scrape eMAG products across Romania, Hungary, Bulgaria and Poland by keyword or URL. Extract product names, prices, discounts, sellers and stock availability. Optional enrichment adds descriptions, specifications and customer ratings.

- **URL**: https://apify.com/abotapi/emag-com-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Stats:** 3 total users, 2 monthly users, 33.3% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.60 / 1,000 product records

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## eMAG Scraper: Products, Prices and Stock

eMAG Scraper turns eMAG, the biggest marketplace in Romania with stores in Hungary, Bulgaria and Poland, into a clean product feed. Search by keyword, or paste any eMAG product or search link and the actor reads the storefront's own listing pages directly: current price and original price with the discount computed, category, seller and stock state, on every row without a second request. Turn on one toggle for the description, brand, specifications, image gallery, seller rating, rating summary, the full offer board of every other seller with their prices, financing plans, variant families and review texts. Export to JSON, CSV or Excel, or pull results straight into your app through the API.

### Why This Scraper?

- **Four stores in one actor.** Search Romania, Hungary, Bulgaria or Poland from one picker, with each row priced in that store's currency, so cross-country price gaps are one run away.
- **Two ways to find products.** Search by keyword, or paste a product or search link; a pasted link decides its own scope, including its own store.
- **The full price story on every row.** Selling price, original price and the discount percentage arrive from the listing itself, with no second request and no toggle required.
- **Seller and stock on every row.** Seller name, stock state and badge flags come straight off the listing card.
- **Details on demand.** Turn on Fetch product details for the description, brand, specifications, image gallery, seller rating, stock state, rating summary, review texts, the other sellers' offer board and prices, financing instalments and the variant family picker.
- **Built for monitoring.** Incremental mode returns only new, changed and reappeared products on recurring runs, and a refused run fails loudly instead of returning an empty dataset.

### Use Cases

- **Cross-country price tracking:** run the same search on all four stores and compare what the same product costs in each currency.
- **Pricing and promo tracking:** monitor a search for price cuts and new discounts over time.
- **Assortment and availability research:** get notified when a product appears, disappears, or changes stock state.
- **Seller research:** track which sellers list a product and how their ratings move.

### Data You Get

> Sample shape: values are illustrative placeholders, not from a live record.

| Field | Example |
| --- | --- |
| `recordId` / `pnk` / `rowType` | `"ro:ABC12XY34"` / `"ABC12XY34"` / `"product"` (the store's own stable product code) |
| `store` / `currency` / `position` / `searchTerm` | `"ro"` / `"Lei"` / `3` / `"telefon"` (store, price currency, search rank and the term that produced the row) |
| `title` | `"Sample Phone Model X, 256GB, 5G"` |
| `price` / `priceText` | `6399.99` / `"6.399,99 Lei"` (the current selling price, as a number and as shown) |
| `originalPrice` / `onSale` / `discountPercent` | `7999.99` / `true` / `20.0` |
| `category` / `categoryTrail` / `categoryId` | `"Telefoane Mobile"` / the full breadcrumb trail / the category id |
| `sellerName` / `availabilityText` | `"Sample Seller"` / `"In stock"` |
| `hasGenius` / `isMarketplace` | `true` / `false` (badge flags off the listing card) |
| `imageUrl` / `imageUrls` / `url` | product image, the full gallery and the product page link (gallery with Fetch product details on) |
| `description` / `brand` / `manufacturer` / `specifications` | with Fetch product details on: the text, the maker and label-to-value pairs off the spec table |
| `sku` / `mpn` / `ean` | with Fetch product details on: the store's code, the manufacturer part number and the barcode (the barcode only when the store lists one) |
| `sellerId` / `sellerSef` / `vendorType` / `sellerRating` / `sellerPositiveShare` | with Fetch product details on: the seller's id, slug, vendor class and rating record |
| `availability` / `inStock` | with Fetch product details on: the stock state code and the orderable flag |
| `offersCount` / `multipleOffersCount` / `usedOffersCount` | with Fetch product details on: how many offers the product has, new and used |
| `offers` / `minPriceOffers` / `maxPriceOffers` / `usedMinPrice` | with Fetch product details on: up to 20 other sellers with their asking prices, plus the price span |
| `priceNet` / `recommendedRetailPrice` / `lowestPrice30Days` | with Fetch product details on: the VAT-exclusive price, the maker's recommended price and the pre-discount 30-day low, each when the store discloses it |
| `averageRating` / `reviewCount` / `ratingDistribution` / `recommendationRate` | with Fetch product details on: the rating summary, its per-star spread and the share of customers who recommend the product |
| `reviews` / `questionCount` | with Fetch product details on: up to Max reviews per product (default 20) review texts with rating, author and date, plus buyer questions. Reviews bill one details surcharge unit per started block of 10 |
| `badges` / `breadcrumbUrls` / `keywords` / `itemCondition` | with Fetch product details on |
| `fulfilledByEmag` / `hasFreeDelivery` / `hasPickup` / `hasVideo` / `hasImage360` / `hasEcredit` | with Fetch product details on: fulfilment, delivery, media and financing flags |
| `ecreditInstallments` / `ecreditProviders` | with Fetch product details on: the financing plan and the finance houses offering it |
| `isFamily` / `familyId` / `familyVariants` | with Fetch product details on: the variant family this listing belongs to and its option picker |
| `productNumericId` / `isBfPrice` | with Fetch product details on: the store's internal product id and the Black Friday pricing flag |
| `scrapedAt` / `detailCarriedForward` | `"2026-01-01T00:00:00Z"` / `true` only when a failed detail read was repaired from the previous run's snapshot |
| `changeType` / `changedFields` / `firstSeenAt` / `lastSeenAt` | incremental mode only: `"UPDATED"` / `["price"]` / when a record was first and most recently seen |

### How to Use

1. Pick a **mode**: `search` (by keyword) or `url` (paste a product or search link).
2. Fill in the field for that mode, pick the **store**, and narrow with the ordering and price filters; they apply in both modes, and a pasted product link is the one exception, it returns that single product in full.
3. Turn on **Fetch product details** if you need the description, specs, gallery, seller rating or rating summary.
4. Set **Max items** to control run size and cost, then click **Start**.

**Search by keyword:**

```json
{
  "mode": "search",
  "searchTerms": ["telefon"],
  "maxItems": 20
}
```

**Search another store, cheapest first:**

```json
{
  "mode": "search",
  "searchTerms": ["telefon"],
  "store": "hu",
  "sortBy": "priceasc",
  "maxItems": 50
}
```

**Paste a search link, with details on:**

```json
{
  "mode": "url",
  "urls": ["https://www.emag.ro/search/telefon"],
  "fetchDetails": true,
  "maxItems": 100
}
```

**Paste a single product link:**

```json
{
  "mode": "url",
  "urls": ["https://www.emag.ro/telefon-mobil-sample-x-256gb-5g/pd/ABC12XY34/"]
}
```

#### Run it from your code

Python:

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("abotapi/emag-com-scraper").call(run_input={"mode": "search", "searchTerms": ["telefon"], "maxItems": 20})
for product in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(product["title"], product["price"], product["originalPrice"])
```

JavaScript:

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('abotapi/emag-com-scraper').call({ mode: 'search', searchTerms: ['telefon'], maxItems: 20 });
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

Or connect it to Make, Zapier, n8n, Google Sheets or webhooks from the **Integrations** tab.

#### How Max items and Max pages shape a run

**Max items** is the single cap on a run, across every search term and URL; set it to `0` for unlimited. With more than one search term or URL, the cap is shared out evenly up front: each source gets at most its equal share (for example 20 each for two sources and Max items 40), and a share one source does not use is not handed to the others. **Max pages** is an optional safety bound per source, on top of that cap. The store serves 60 products per page: when a page holds more fresh candidates than the budget left for that source, only the first candidates on that page, in the store's own order, are read this run, and the run's log names how many of that page were kept. The rest of that page is not read this run, and a product cut off this way is also skipped if a later search term or URL in the same run lists it, so overlapping search terms can return fewer rows than Max items allows.

This matters most with **Incremental mode** on a small, recurring **Max items**. The budget counts returned rows across pages (an unchanged row that is suppressed does not use it up, so the walk moves on to the next page), but within one page it is a cut by position: the candidates after the first N on a page are never classified at all this run, even when the first N all turn out unchanged and nothing is returned. A genuine price or stock change on one of them is missed, and the run's summary message does not say it was capped (a run where every candidate it did classify was unchanged reports "N product(s) scanned, nothing changed", the same message a fully complete, unchanged scan produces). Because every run starts from the top of the results again, a later run with the same Max items cuts the page at the same place, so while the products ranked ahead of it stay unchanged, that change can stay unreported run after run. For a recurring, monitored search or URL, set **Max items** to `0` or to at least the size of the tracked scope so a page is never sliced mid-way.

#### Resume and recurring updates

- **Resume** (`resumeFromRunId`) continues one interrupted or capped run: paste its run or dataset ID and the actor skips everything already collected there, so you don't pay twice.
- **Incremental mode** (`incrementalMode`) is for running the same search or URL again and again (for example daily) and getting only what changed. Each record classifies `NEW`, `UPDATED` (with `changedFields`; a price move, a stock change or a new rating on a storefront IS reported as UPDATED, since that is exactly what a monitor watches for), `UNCHANGED` (suppressed and not billed unless `emitUnchanged` is on), `REAPPEARED`, or `EXPIRED` (only after a run that scanned the whole tracked scope: never when Max items or Max pages capped the walk short, never with Resume, and never after a refusal). Image URLs never mark a row UPDATED on their own. `stateKey` names or shares the stored state, so two differently configured searches never mix their history.

### Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step **after** the scrape: the Apify dataset is never changed.

**What gets written to the connector:** a condensed, human-readable **summary** of each record, not the full JSON. Each item becomes one entry with a **title** and its key fields flattened to plain text. The **complete record always stays in the Apify dataset**.

1. Authorize a connector once under **Apify → Settings → Integrations** (Notion, Linear, Airtable, or Apify).
2. Select it in the **"Pipe results into your apps"** input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For **Notion**, also set `notionParentPageUrl` to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

### Input Parameters

| Parameter | Type | Default | Description |
| --- | --- | --- | --- |
| `mode` | string | `search` | `search` (by keyword) or `url` (paste store links). |
| `searchTerms` | array | `["telefon"]` | Search mode: one or more terms to search for, each scraped independently. |
| `urls` | array | sample | URL mode: product or search links; each pasted URL decides its own scope, including its own store. |
| `store` | string | `ro` | Which country store to search in search mode: `ro`, `hu`, `bg` or `pl`. Rows are priced in that store's currency. |
| `sortBy` | string | `relevance` | The store's own server-side ordering: `relevance`, `priceasc`, `pricedesc`, `reviewsdesc`, `discountdesc` or `popularity`. |
| `minPrice` | integer | (none) | Only keep rows whose selling price is at least this much, in the store's currency. |
| `maxPrice` | integer | (none) | Only keep rows whose selling price is at most this much, in the store's currency. |
| `onSaleOnly` | boolean | `false` | Only keep rows with a discount (selling price below the original price). |
| `fetchDetails` | boolean | `false` | Fetch each item's product page: description, brand, specs, gallery, seller rating, stock state and rating summary. Charged once per record. |
| `maxItems` | integer | `20` | The single cap on this run, across all search terms and URLs. `0` = unlimited. |
| `maxPages` | integer | `0` | Safety bound on result pages walked per search term or URL. `0` = no page limit (Max items still applies). |
| `maxReviews` | integer | `20` | How many reviews to keep per product record, with Fetch product details on. Reviews are read from the product page already fetched for the details, so the cap adds no page read; every started block of 10 reviews bills one extra details surcharge unit. `0` = skip reviews. |
| `ignoreFieldsForChanges` | array | (none) | Incremental mode only: extra field names to keep out of the change fingerprint. Price, stock and rating fields are never ignored. |
| `resumeFromRunId` | string | (none) | Continue one interrupted run without returning or charging for records it already collected. |
| `incrementalMode` | boolean | `false` | Turn on for recurring monitoring of the same search or URL: later runs return only new, changed and reappeared records. |
| `stateKey` | string | (none) | Name or share an incremental-mode monitoring campaign's stored state. |
| `emitUnchanged` | boolean | `false` | Also return (and bill) records that have not changed since the last run. |
| `emitExpired` | boolean | `false` | Also return (and bill) records that were tracked before but are no longer found, once a run fully scans the tracked scope. |
| `ignoreFieldsForChanges` | array | (none) | Incremental mode only: extra field names to keep out of the change fingerprint. Price, stock and rating fields are never ignored. |
| `mcpConnectors` | array | (none) | Optional: send a summary of each record to apps you authorized under Integrations. |
| `notionParentPageUrl` | string | (none) | Notion connector only: page under which record pages are created. |
| `maxNotifyListings` | integer | `50` | Cap on records written to each connector per run. |
| `proxy` | object | Apify Proxy | Connection settings. Residential is recommended for the most reliable results. |

### Output Example

> Sample shape: values are illustrative placeholders, not from a live record.

```json
{
  "recordId": "ro:ABC12XY34",
  "rowType": "product",
  "store": "ro",
  "pnk": "ABC12XY34",
  "productId": "100000001",
  "offerId": "200000001",
  "url": "https://www.emag.ro/telefon-mobil-sample-x-256gb-5g/pd/ABC12XY34/",
  "title": "Sample Phone Model X, 256GB, 5G",
  "brand": "Sample Brand",
  "manufacturer": "Sample Brand",
  "category": "Telefoane Mobile",
  "categoryTrail": "Laptop, Tablete and Telefoane/Telefoane Mobile",
  "price": 6399.99,
  "priceText": "6.399,99 Lei",
  "currency": "Lei",
  "originalPrice": 7999.99,
  "onSale": true,
  "discountPercent": 20.0,
  "sku": "SKU-ABC12XY34",
  "mpn": "MPN-XYZ-90",
  "ean": "6000000000000",
  "itemCondition": "NewCondition",
  "description": "A sample phone with a large display and a long lasting battery.",
  "specifications": {
    "Memorie interna": "256 GB",
    "Memorie RAM": "8 GB"
  },
  "imageUrl": "https://images.example.com/products/sample-phone/ABC12XY34-1.jpg",
  "imageUrls": [
    "https://images.example.com/products/sample-phone/ABC12XY34-1.jpg",
    "https://images.example.com/products/sample-phone/ABC12XY34-2.jpg"
  ],
  "sellerName": "Sample Seller",
  "sellerId": 12345,
  "sellerSef": "sample-seller",
  "sellerRating": 4.8,
  "sellerPositiveShare": 96,
  "vendorType": 2,
  "availability": "in_stock",
  "availabilityText": "In stock",
  "inStock": true,
  "offersCount": 8,
  "multipleOffersCount": 7,
  "usedOffersCount": 0,
  "minPriceOffers": 6199.99,
  "maxPriceOffers": 7249.99,
  "offers": [
    {"offerId": 300000001, "vendor": "Other Shop", "vendorSef": "other-shop", "price": 6199.99, "type": 1}
  ],
  "priceNet": 5289.25,
  "averageRating": 4.8,
  "reviewCount": 303,
  "ratingDistribution": {"5": 87, "4": 5, "3": 3, "2": 2, "1": 3},
  "recommendationRate": 92,
  "questionCount": 11,
  "badges": ["badge-genius", "commercial-badge"],
  "fulfilledByEmag": false,
  "hasFreeDelivery": false,
  "hasPickup": true,
  "hasVideo": false,
  "hasImage360": false,
  "hasEcredit": true,
  "ecreditInstallments": {"count": 24, "value": 322},
  "ecreditProviders": ["Sample Finance"],
  "isFamily": false,
  "familyVariants": [{"name": "Memorie interna", "options": ["256 GB", "512 GB"]}],
  "position": 3,
  "searchTerm": "telefon",
  "productNumericId": 100000001,
  "hasGenius": true,
  "isMarketplace": false,
  "detailCarriedForward": null,
  "scrapedAt": "2026-01-01T00:00:00Z"
}
```

With **Incremental mode** on, a row also carries `changeType`, `changedFields`, `firstSeenAt` and `lastSeenAt`.

### Plan Requirement

The default proxy setting works out of the box: residential is recommended for the most reliable results, since the storefront answers residential exits most consistently. The actor rotates connections automatically when one is refused; change the Proxy configuration only if a run reports it could not read any results. Fetch product details adds a paid surcharge: one unit per enriched record plus one unit per started block of 10 delivered reviews; the price pair, category, seller and stock state are on every row either way.

### FAQ

#### How much does it cost?

You pay per product record returned, plus an optional surcharge when Fetch product details is on: one unit per enriched record plus one unit per started block of 10 delivered reviews (a record with the default 20 reviews bills 2 surcharge units; `Max reviews: 0` bills 1). The **Pricing** tab shows the current rates. Use **Max items** to cap the cost of any run.

#### Is it legal to scrape eMAG?

This actor collects only publicly available product data. You are responsible for how you use it: follow the store's terms and the laws that apply to you, and get legal advice if you plan commercial redistribution. Product names, prices and stock levels are generally facts, but images and descriptions may be subject to third-party rights.

#### Can I get only new or changed products on a schedule?

Yes. Schedule the actor from the **Schedules** tab and turn on **Incremental mode**. Each run then returns only new, updated and reappeared records; unchanged ones are suppressed and not billed unless **Emit unchanged** is on.

#### Why did a run return fewer products than I expected?

**Max items** is the single cap on a run, across every search term and URL, and with several sources it is split evenly between them up front: with two search terms and Max items 40, each term returns at most 20, even if the other term finds nothing. When a page holds more fresh candidates than a source's remaining budget, only the first candidates on that page, in the store's own order, are read, and a product cut off that way is also skipped by any later search term in the same run that lists it. Raise Max items, or set it to `0`, to read further. With **Incremental mode** on for a recurring search, keep Max items at `0` or at least the size of the whole tracked scope: a candidate cut off mid-page is not classified at all that run, so a genuine change on it can be missed without the run looking capped from its own summary message, and later runs with the same Max items cut the page at the same place, so it can stay missed until the products ranked ahead of it change or Max items is raised.

#### Why did my run fail instead of returning an empty dataset?

If the store refuses every request, the run stops with a clear message so "nothing matched" is never confused with "nothing could be read". The storefront sometimes answers with a bot check in waves; run it again in a few minutes, or change the Proxy configuration. If only some search terms or URLs could be read, you still get what was found, and the run's log shows which source could not be read (when nothing at all was found, the status message also gives the count of sources that could not be read).

#### What's the difference between Resume and Incremental mode?

**Resume** (`resumeFromRunId`) continues ONE specific interrupted or capped run: paste its run or dataset ID and this run skips everything it already collected there. **Incremental mode** is for running the SAME search or URL again and again (for example daily) and getting only what changed; it keeps its own state per search, independent of any one run.

#### Can I use it with AI agents or MCP?

Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear or Airtable.

#### Why are category pages not supported?

Category pages on this storefront answer automated readers with a bot check even when search and product pages serve normally, so pasting one fails loudly instead of returning an empty dataset. Search for the same products by keyword, or paste a search link, and you get the same catalogue.

### 🔗 More scrapers you might like

Pair this actor with these related scrapers from the same team:

<table>
<tr><td>🧩 <a href="https://apify.com/abotapi/joom-com-scraper"><b>Joom Scraper</b></a><br>Scrape Joom products by keyword or URL. Extract product names, prices, discounts...</td><td>🧩 <a href="https://apify.com/abotapi/asos-com-scraper"><b>ASOS Scraper</b></a><br>Scrape ASOS by keyword, category or URL. Every row carries the selling price and the...</td></tr>
<tr><td>🧩 <a href="https://apify.com/abotapi/miravia-es-scraper"><b>Miravia Spain Scraper</b></a><br>Scrape Miravia Spain by keyword, seller store or URL. Every row carries the selling price...</td><td>🏷️ <a href="https://apify.com/abotapi/olx-scraper"><b>OLX Scraper</b></a><br>Fast OLX scraper across 9 countries, including Poland, Romania, Portugal, Ukraine...</td></tr>
<tr><td>🛒 <a href="https://apify.com/abotapi/americanas-com-br-scraper"><b>Americanas Brazil</b></a><br>Scrape Americanas Brazil (americanas.com.br) by keyword, department or pasted link...</td><td>🛒 <a href="https://apify.com/abotapi/thegioididong-scraper"><b>Thegioididong Scraper</b></a><br>Scrape thegioididong.com products with full specifications, current &amp; original price...</td></tr>
</table>

👉 [Browse all abotapi scrapers](https://apify.com/abotapi)

### 💬 Support

- 🐞 **Found a bug or a missing field?** Open a ticket on the [Issues tab](https://apify.com/abotapi/emag-com-scraper/issues/open). We usually reply within hours.
- 🛠️ **Need another site, extra fields or a private build?** Email <contact@abotapi.com>.
- ⭐ **Enjoying it?** A quick review on the actor page helps other users find it.

# Actor input Schema

## `mode` (type: `string`):

How to start the scrape. 'search' runs store searches on the picked store. 'url' processes the store URLs you paste: a product URL is fetched as a single product, and a search URL is paged like a search, its own query, store and page deciding the scope. The filters below apply to every walk in both modes; a pasted product URL is the one exception and returns that single product in full.

## `searchTerms` (type: `array`):

One or more things to search the store for, for example 'telefon', 'masina de spalat', 'laptop'. Each term is scraped independently. Search mode only: in URL mode the scope is read out of each pasted URL instead. Leave this empty and the run browses the current offers with only the filters applied.

## `urls` (type: `array`):

Paste product URLs (ending in /pd/XXXXXXX/) or search URLs (containing /search/). A search URL may carry /p3 to start the walk further in and /sort-priceasc to order it. A product URL ignores paging and returns that one product in full. Category pages (.../c) are not supported: the store answers them with a captcha.

## `store` (type: `string`):

Applies in BOTH search mode and URL mode. In search mode it picks which country store to search: Romania, Hungary, Bulgaria or Poland, with rows priced in that store's currency. In URL mode each pasted URL carries its own store, so this is only the fallback for search walks.

## `sortBy` (type: `string`):

The store's own server-side ordering, sent with every page of every search walk. This orders the walk itself (and therefore which rows a capped run keeps), not just the output. Applies in BOTH search mode and URL mode search walks; a pasted search URL with its own /sort- value keeps that instead.

## `minPrice` (type: `integer`):

Only keep rows whose selling price is at least this much, in the store's currency. The store has no parameter for this, so it is applied to the rows this run reads. Applies in BOTH search mode and URL mode.

## `maxPrice` (type: `integer`):

Only keep rows whose selling price is at most this much, in the store's currency. The store has no parameter for this, so it is applied to the rows this run reads. Applies in BOTH search mode and URL mode.

## `onSaleOnly` (type: `boolean`):

Only keep rows whose selling price is below the original price, that is rows with a discount. The store has no parameter for this, so it is applied to the rows this run reads. Applies in BOTH search mode and URL mode.

## `fetchDetails` (type: `boolean`):

Fetch each item's product page for the description, brand, specifications, image gallery, seller rating, stock state and rating summary. Slower, and billed one unit per enriched record plus one unit per started block of 10 delivered reviews. Leave off for a fast crawl: identity, prices, discount and category are included either way.

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

The single cap on this run: stop after collecting this many records across all search terms and URLs. Set 0 for unlimited.

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

Safety bound on how many result pages to walk per search term or URL. Leave empty (0) for no page limit: the run then stops at Max items, not here. Does not impose a separate cap below Max items.

## `maxReviews` (type: `integer`):

How many reviews to keep per product record, with Fetch product details on. Reviews are read from the product page already fetched for the details, so the cap adds no page read; every started block of 10 reviews bills one extra details surcharge unit. Set 0 to skip reviews entirely.

## `proxy` (type: `object`):

Leave the default for the most reliable run. Residential is recommended for the most reliable results: the storefront answers residential exits most consistently, and datacenter exits are refused more often. Change it only if a run reports that it could not read any results.

## `resumeFromRunId` (type: `string`):

Paste a previous run ID or dataset ID to continue a large crawl without returning or charging for records already collected there. Use this after an interrupted or capped run. For recurring monitoring of the same search, use Incremental mode below instead.

## `incrementalMode` (type: `boolean`):

Turn this on for daily or weekly recurring monitoring of the same search, for example a price watch. The first run returns everything matching as NEW. Later runs normally return only NEW, UPDATED and REAPPEARED records. Price moves, stock changes and new ratings ARE reported as UPDATED: on a store they are the signal, not noise. Image URLs never mark a row UPDATED on their own. Turn on Emit unchanged or Emit expired only when you also want those rows returned (and billed). State is kept separately per search, URL and filter setup; use State key to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.

## `stateKey` (type: `string`):

Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently configured runs. Leave empty to let the actor derive a key automatically from the search terms, URLs and filters, so two different searches never mix state.

## `emitUnchanged` (type: `boolean`):

Off by default. Turn on to also return records that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have, so leave it off unless you specifically want a full snapshot every run.

## `emitExpired` (type: `boolean`):

Off by default. Turn on to also return records that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search: not when Max items capped it, not when Resume was used, and not when the run was refused. This returns, and bills, extra synthetic rows, so leave it off unless you need expiry tracking.

## `ignoreFieldsForChanges` (type: `array`):

Incremental mode only. Extra field names to keep out of the change fingerprint, on top of the built-in image URL ignore list. Use this when a field moves on every run without the product changing. Price, stock and rating fields are never ignored: on a store they are the signal.

## `mcpConnectors` (type: `array`):

Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify, Settings, API and Integrations, then select it here. Notion gets a page per record; other connectors get a best-effort write or digest. Each connector receives a condensed summary per record, not the full record; the complete record always stays in the dataset. Leave empty to skip; this never changes the dataset output. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).

## `notionParentPageUrl` (type: `string`):

URL or id of the Notion page under which record pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on records written to each connector per run. Does not affect the dataset.

## Actor input object example

```json
{
  "mode": "search",
  "searchTerms": [
    "telefon"
  ],
  "urls": [
    "https://www.emag.ro/search/telefon",
    "https://www.emag.ro/telefon-mobil-apple-iphone-17-pro-256gb-5g-silver-mg8g4zd-a/pd/DN99FV3BM/",
    "https://www.emag.ro/search/telefon/sort-priceasc/p2",
    "https://www.emag.hu/search/telefon"
  ],
  "store": "ro",
  "sortBy": "relevance",
  "onSaleOnly": false,
  "fetchDetails": false,
  "maxItems": 20,
  "maxPages": 0,
  "maxReviews": 20,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "ignoreFieldsForChanges": [],
  "maxNotifyListings": 50
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `detail` (type: `string`):

No description

## `changes` (type: `string`):

No description

# 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 = {
    "mode": "search",
    "searchTerms": [
        "telefon"
    ],
    "urls": [
        "https://www.emag.ro/search/telefon",
        "https://www.emag.ro/telefon-mobil-apple-iphone-17-pro-256gb-5g-silver-mg8g4zd-a/pd/DN99FV3BM/",
        "https://www.emag.ro/search/telefon/sort-priceasc/p2",
        "https://www.emag.hu/search/telefon"
    ],
    "store": "ro",
    "fetchDetails": false,
    "maxItems": 20,
    "maxReviews": 20,
    "proxy": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    },
    "incrementalMode": false,
    "emitUnchanged": false,
    "emitExpired": false,
    "ignoreFieldsForChanges": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/emag-com-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 = {
    "mode": "search",
    "searchTerms": ["telefon"],
    "urls": [
        "https://www.emag.ro/search/telefon",
        "https://www.emag.ro/telefon-mobil-apple-iphone-17-pro-256gb-5g-silver-mg8g4zd-a/pd/DN99FV3BM/",
        "https://www.emag.ro/search/telefon/sort-priceasc/p2",
        "https://www.emag.hu/search/telefon",
    ],
    "store": "ro",
    "fetchDetails": False,
    "maxItems": 20,
    "maxReviews": 20,
    "proxy": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
    "incrementalMode": False,
    "emitUnchanged": False,
    "emitExpired": False,
    "ignoreFieldsForChanges": [],
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/emag-com-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 '{
  "mode": "search",
  "searchTerms": [
    "telefon"
  ],
  "urls": [
    "https://www.emag.ro/search/telefon",
    "https://www.emag.ro/telefon-mobil-apple-iphone-17-pro-256gb-5g-silver-mg8g4zd-a/pd/DN99FV3BM/",
    "https://www.emag.ro/search/telefon/sort-priceasc/p2",
    "https://www.emag.hu/search/telefon"
  ],
  "store": "ro",
  "fetchDetails": false,
  "maxItems": 20,
  "maxReviews": 20,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "ignoreFieldsForChanges": []
}' |
apify call abotapi/emag-com-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abotapi/emag-com-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/03pHBnd9olMzlLl4a/builds/nVft6qF8PyMP8MBt5/openapi.json