eMAG Scraper — Romania, Bulgaria, Hungary E-commerce avatar

eMAG Scraper — Romania, Bulgaria, Hungary E-commerce

Pricing

from $2.50 / 1,000 results

Go to Apify Store
eMAG Scraper — Romania, Bulgaria, Hungary E-commerce

eMAG Scraper — Romania, Bulgaria, Hungary E-commerce

Scrape eMAG, the top e-commerce marketplace in Romania, Bulgaria and Hungary: product title, price in local currency (RON, BGN, HUF), rating, review count, SKU and image. Category browse or keyword search across all three markets. Keyless.

Pricing

from $2.50 / 1,000 results

Rating

0.0

(0)

Developer

Logiover

Logiover

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

Apify Actor No API key Pay per result Export

Scrape eMAG, the top e-commerce marketplace in Romania, Bulgaria and Hungary: product title, price in local currency (RON, BGN, HUF), rating, review count, SKU and image. Category browse or keyword search across all three markets. Keyless.


What does the eMAG Scraper do?

This Actor turns eMAG into a structured dataset you can actually work with. You give it a search, it walks the result pages, and it writes one clean row per record into your dataset — ready to export as JSON, CSV or Excel, or to pull straight from the Apify API.

It runs on plain HTTP with no browser and no login, which keeps it fast and cheap, and it works the same on a free account as on a paid one. Every field documented below came from a real verification run of this Actor, so what you read here is what you get.

The current build returns 12 populated fields per record, of which 12 are present on virtually every row.

Who is it for?

  • Analysts who need eMAG data as a spreadsheet instead of a browser tab.
  • Operations and research teams tracking how eMAG listings change over time.
  • Developers wiring a live data feed into an internal tool or database.
  • Growth and sales teams building prospect and market lists from public data.
  • AI teams assembling structured training or grounding data.

Use cases

  • Export a full eMAG search into a spreadsheet for analysis.
  • Track how prices, volumes or availability move week over week by scheduling the run.
  • Feed a dashboard or internal database with a repeatable, structured source.
  • Build a market map by running several searches in one job.
  • Enrich an existing list by matching on the identifiers in the output.

Why use this eMAG Scraper?

  • 🔑 No API key and no login — nothing to authenticate, nothing to expire.
  • 📦 12 verified fields — every column below was confirmed against live output.
  • 📄 Real pagination — it walks the result set instead of returning the first screen.
  • 🎯 Bounded runs — caps in the input stop the job exactly where you want, so the bill is predictable.
  • 💸 Tiered pay-per-result — you pay per row, and higher Apify plans pay less per row.
  • 📊 Export anywhere — JSON, CSV, Excel, HTML, the API, or any Apify integration.

What data can you extract?

One row per record. These columns come from a live run, with the share of rows that carried a value:

FieldTypeTypically filledDescription
countrynumber100%Country
currencystring100%Currency
imageUrlstring100%Image url
priceAmountnumber100%Price amount
priceLabelnumber100%Price label
productUrlstring100%Product url
ratingnumber93%Rating
reviewCountnumber98%Review count
scrapedAtstring100%Scraped at
skustring100%Sku
sourcestring100%Source
titlestring100%Title

Output example

{
"country": "Romania",
"currency": "RON",
"imageUrl": "https://s13emagst.akamaized.net/products/82689/82688535/images/res_ffaa49e8b92eb9bd1f1324cd76e5c482.jpg?width=720&height=720&hash=7A6B57835C40363E50DBD90C7FA93EA5",
"priceAmount": 109.99,
"priceLabel": "109,99 Lei",
"productUrl": "https://www.emag.ro/telefon-mobil-nokia-105-2024-dual-sim-black-sp01z07z2068y/pd/D3K4J6YBM/",
"rating": 4.1,
"reviewCount": 81,
"scrapedAt": "2026-09-11T09:48:07.856Z",
"sku": "D3K4J6YBM",
"source": "emag",
"title": "Telefon mobil Nokia 105 (2024), Dual SIM, Black"
}

How to use

  1. Open the Actor and fill in the search fields — the defaults below are a working example.
  2. Set the result cap so the run stops where you want it.
  3. Click Start, then export from the Output tab or pull the dataset through the API.
{
"market": "ro",
"searchQuery": "telefoane mobile",
"maxResults": 500,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": [
"RESIDENTIAL"
]
}
}

Input parameters

ParameterTypeDefaultDescription
marketstringroWhich eMAG country site to scrape.
categoryPathstringeMAG category slug from the URL, e.g.
searchQuerystringKeyword to search across the whole store.
maxResultsinteger500Stop after this many products.
proxyConfigurationobject{"useApifyProxy": true, "aeMAG blocks datacenter traffic, so residential proxy pinned to the market is required and preselected.

Tips for best results

  • Broad searches return the deepest result sets; very narrow ones run out after a page or two.
  • Use the result cap rather than the page cap when you want a predictable bill.
  • Schedule the same input daily or weekly to build a history instead of a one-off snapshot.
  • Lower the concurrency if you see retries — the source rate-limits aggressive crawling.
  • Run several searches in one job instead of one search with a huge page count.
  • Empty optional fields are normal; filter on the columns that matter to you after export.
  • Deduplicate on the identifier column if you merge several runs together.
  • Keep the proxy setting on the default unless the source blocks your region.

Integrations

Push results straight into Google Sheets, Slack, Zapier, Make, Airtable or any Webhook. You can also schedule the Actor and have each run append to the same dataset, which is how you turn a single export into a time series.

API usage

Replace <YOUR_TOKEN> with your Apify API token.

cURL

curl -X POST "https://api.apify.com/v2/acts/logiover~emag-scraper/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"market": "ro", "searchQuery": "telefoane mobile", "maxResults": 500, "proxyConfiguration": {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]}}'

Python

from apify_client import ApifyClient
client = ApifyClient('<YOUR_TOKEN>')
run = client.actor('logiover/emag-scraper').call(run_input={"market": "ro", "searchQuery": "telefoane mobile", "maxResults": 500, "proxyConfiguration": {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]}})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
print(item)

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_TOKEN>' });
const run = await client.actor('logiover/emag-scraper').call({"market": "ro", "searchQuery": "telefoane mobile", "maxResults": 500, "proxyConfiguration": {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]}});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Use with AI agents (MCP)

This Actor is reachable through the Apify MCP server, so an AI agent can call it as a tool. Point the agent at https://mcp.apify.com and ask it something like "pull the first 200 products from eMAG and summarise them" — it receives the same structured rows you would get from the UI.

FAQ

Do I need a eMAG account or API key?

No. The Actor reads publicly available pages only. There is nothing to authenticate and no credentials to rotate.

Does it work on the free plan?

Yes. Every feature is available on a free Apify account — nothing is gated behind a paid tier. Pricing is per result, and higher plans simply pay less per row.

How many products can I get in one run?

As many as the search exposes. Raise the page and result caps together; the run stops at whichever limit it reaches first.

Why did I get fewer rows than I asked for?

The search ran out of records. That is normal for narrow queries — broaden the search or add more searches to one run.

Why are some fields empty?

eMAG does not publish every attribute for every record. The table above shows how often each field is filled in practice.

What export formats are supported?

JSON, CSV, Excel, HTML and RSS from the Output tab, plus the Apify API and any integration you connect.

How fast is it?

It is pure HTTP with no browser, so a page of results typically takes a second or two.

Can I schedule it?

Yes. Use the Apify scheduler to run it on any interval and append each run to the same dataset.

Does it use a proxy?

It routes through Apify Proxy by default. You can switch groups or supply your own proxies in the input.

Is the output schema stable?

Yes. Field names and types are fixed, so downstream pipelines will not break between runs.

How often is the data refreshed?

Every run reads the live source. There is no cache, so the data is as current as the website itself.

What if the site changes its layout?

Open an issue on the Issues tab and it gets fixed — the Actor is actively maintained.

This Actor reads only publicly available pages on eMAG — the same content any visitor sees without logging in. It does not bypass authentication and does not collect private data. You remain responsible for how you use the output: respect the source's terms of service, applicable copyright, and data-protection law such as GDPR where personal data is involved.

Browse the full collection at apify.com/logiover — Ecommerce tools and more.