eMAG Scraper at a glance
eMAG Scraper is a ready-to-run Apify actor from abotapi for collecting web data. Its documented output includes record id, title, url, store and price, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $1.80 per 1,000 results on the Apify Free plan and from $1.60 on paid plans, with smaller per-run or optional feature charges listed on Apify.
- Runs on
- Apify cloud: console, API, schedules and integrations
- Data type
- Web data
- Pricing
- $1.80 per 1,000 results (Free plan), from $1.60 on paid plans
- Output
- Documented below · JSON, CSV, Excel
- Inputs
- 19 options
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.
What eMAG Scraper can do
- 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.
Choose what to collect
These inputs let you configure eMAG Scraper - Products, Prices, Sellers & Stock. Open the actor on Apify to enter your values and review the current options.
| Input | What it controls |
|---|---|
modestring · required | 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. |
searchTermsarray | 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. |
storestring | 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. |
sortBystring | 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. |
minPriceinteger | 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. |
maxPriceinteger | 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. |
onSaleOnlyboolean | 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. |
Show 12 more inputs
| Input | What it controls |
|---|---|
fetchDetailsboolean | 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. |
maxItemsinteger | The single cap on this run: stop after collecting this many records across all search terms and URLs. Set 0 for unlimited. |
maxPagesinteger | 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. |
maxReviewsinteger | 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. |
resumeFromRunIdstring | 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. |
incrementalModeboolean | 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. |
stateKeystring | 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. |
emitUnchangedboolean | 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. |
emitExpiredboolean | 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. |
mcpConnectorsarray | 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). |
notionParentPageUrlstring | URL or id of the Notion page under which record pages are created. Required to enable the Notion export; ignored by other connectors. |
maxNotifyListingsinteger | Cap on records written to each connector per run. Does not affect the dataset. |
Fields in the output
The documented dataset includes the fields below. Availability can depend on the source page and selected mode.
recordIdRecord IDtitleTitleurlurlstorestorepricePricepriceTextpriceTextcurrencycurrencyoriginalPriceoriginalPricediscountPercentdiscountPercentonSaleonSalebrandbrandcategorycategoryShow 64 more fields
sellerNameSelleravailabilityTextavailabilityTextaverageRatingaverageRatingreviewCountreviewCountimageUrlimageUrlhasGeniushasGeniusisMarketplaceisMarketplacescrapedAtscrapedAtpositionpositionsearchTermsearchTermmpnmpninStockinStockoffersCountoffersCountminPriceOffersminPriceOffersmaxPriceOffersmaxPriceOffersfulfilledByEmagfulfilledByEmaghasFreeDeliveryhasFreeDeliverybadgesbadgesisFamilyisFamilypnkpnkproductIdproductIdofferIdofferIdmanufacturermanufacturercategoryTrailcategoryTraildescriptiondescriptionspecificationsspecificationsskuskueaneanimageUrlsimageUrlssellerRatingsellerRatingsellerPositiveSharesellerPositiveShareavailabilityavailabilityitemConditionitemConditionkeywordskeywordsbreadcrumbUrlsbreadcrumbUrlssellerIdsellerIdsellerSefsellerSefvendorTypevendorTypequestionCountquestionCountratingDistributionratingDistributionreviewsreviewspriceNetpriceNetrecommendedRetailPricerecommendedRetailPricelowestPrice30DayslowestPrice30DaysmultipleOffersCountmultipleOffersCountusedOffersCountusedOffersCountusedMinPriceusedMinPriceoffersoffersfamilyVariantsfamilyVariantshasPickuphasPickuphasVideohasVideohasImage360hasImage360hasEcredithasEcreditecreditInstallmentsecreditInstallmentsecreditProvidersecreditProvidersproductNumericIdproductNumericIdcategoryIdcategoryIdfamilyIdfamilyIdisBfPriceisBfPricerecommendationRaterecommendationRatechangeTypechangeTypechangedFieldschangedFieldsfirstSeenAtfirstSeenAtlastSeenAtlastSeenAtExample output
An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.
{
"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,
"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": {
"1": 3,
"2": 2,
"3": 3,
"4": 5,
"5": 87
},
"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"
}Ways to use this data
- 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.
Before you run
Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.
Questions about this actor
What data does eMAG Scraper return?
The documented output for eMAG Scraper includes record id, title, url, store, price, pricetext, currency and originalprice. Availability of each field depends on the source page and the selected mode.
How much does eMAG Scraper cost?
It costs $1.80 per 1,000 results on the Apify Free plan and from $1.60 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.
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.
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.
