eMAG Seller Scraper – Vendors, Contacts & Categories
Under maintenancePricing
from $6.50 / 1,000 full seller profiles
eMAG Seller Scraper – Vendors, Contacts & Categories
Under maintenanceDiscover and enrich public eMAG marketplace seller profiles across Romania, Bulgaria, and Hungary, including company details, public contacts, categories, and resumable exports. Proxy support improves routing but does not guarantee access.
Pricing
from $6.50 / 1,000 full seller profiles
Rating
0.0
(0)
Developer
Sergiu Adrian
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 days ago
Last modified
Categories
Security
Limited permissionsShare
Discover eMAG marketplace sellers and export public company profiles, contact details, and category relationships across Romania, Bulgaria, and Hungary.
Use it for marketplace research, seller intelligence, lead qualification, category analysis, and competitive mapping. Runs are resumable, country-aware, and designed to minimize duplicate requests.
What you can extract
- Seller name, seller ID, slug, and public profile URL
- Company name, tax ID, VAT ID, trade-register number, and status
- Registered and fiscal addresses, country, CAEN, bank, and IBAN when publicly displayed
- Public phone number and email, with full, masked, or availability-only output
- Seller rating, positive-rating percentage, and product counts when available
- Seller-to-category relationships in a separate export
- Run report with progress, blocked URLs, retries, billing events, and checkpoint data
Three data packages
Seller discovery
Find unique seller identities from official category sitemaps, category filters, search pages, and product pages. Best for building a low-cost seller directory.
Full seller database
Discover sellers and visit each public seller page to add company, registration, address, rating, phone, and email fields.
Marketplace intelligence
Includes full seller profiles plus a separate seller-category dataset for category coverage and assortment analysis.
Supported marketplaces
| Country | Domain | Proxy region |
|---|---|---|
| Romania | emag.ro | Romania |
| Bulgaria | emag.bg | Bulgaria |
| Hungary | emag.hu | Hungary |
Choose one country or All countries. Multi-country runs process marketplaces sequentially so every request uses the matching regional proxy configuration.
Quick start
- Select a data package.
- Choose Romania, Bulgaria, Hungary, or All countries.
- Leave start URLs empty to use the official category sitemap, or provide category, search, product, seller, or sitemap URLs.
- Set a maximum charge and seller limit.
- Start the run and export sellers as JSON, CSV, Excel, XML, or JSONL.
Recommended full Romania run
{"operation": "FULL","targetCountry": "RO","startUrls": [{ "url": "https://www.emag.ro/sitemaps/categories-index.xml" }],"contactMode": "full","maxVendors": 25000,"maxListingPages": 2500,"maxVendorFilterPages": 2500,"maxConcurrency": 3,"delaySeconds": 4,"followProducts": false,"followPagination": false}
Output
Sellers dataset
The default dataset contains either discovery records or enriched seller profiles. Important fields include:
{"marketplace": "ro","seller_name": "Example Seller","company_name": "EXAMPLE COMPANY SRL","cui": "12345678","vat_id": "RO12345678","reg_com": "J40/1234/2024","registered_address": "București, Romania","country": "Romania","phone": "+40...","email": "contact@example.ro","seller_url": "https://www.emag.ro/example/123456/v"}
Fields not displayed publicly by eMAG are returned as null, never invented.
Seller categories dataset
Marketplace Intelligence runs also provide one row per seller-category relationship with seller ID, category URL, category name, and category-level product count when available.
Run report
RUN_REPORT records progress, retries, access challenges, recovery usage, output counts, pricing-event counts, and resume information.
Reliable long runs
- Stable proxy sessions keep cookies and browser fingerprints together.
- A proxy-pool circuit breaker checkpoints and stops the run after repeated tunnel failures across several endpoints, preventing hours of compute without progress.
- Requests are rate-limited per session, not only globally.
- Retries are limited to transient network and server errors.
- Access challenges are logged, checkpointed, and skipped; proxy use does not guarantee access.
- Optional recovery fetching is disabled by default, capped when enabled, and does not solve CAPTCHA.
- Checkpoints persist discovered sellers, completed categories, pending work, and output IDs.
resumeFromRunIdcontinues unfinished work, copies each prior seller only once, prefers the richest duplicate record, and does not requeue completed profiles.- Spending-limit responses stop the crawler cleanly after saving progress.
Pricing
This Actor uses pay-per-event pricing so small tests remain inexpensive and full marketplace databases scale predictably.
| Event | Suggested price |
|---|---|
| Actor start | Apify default |
| Vendor discovered | $0.0025 |
| Full profile extracted | $0.0065 |
| Seller-category relationship | $0.0005 |
A full profile run with about 16,000 unique sellers is approximately $104, while discovery-only is approximately $40. Marketplace Intelligence adds seller-category events. Always set a maximum run charge in Apify Console.
Data responsibility
This Actor extracts information displayed on public marketplace pages. It does not log into seller accounts, send messages, or solve CAPTCHA. Availability depends on eMAG, regional access, and site changes.
Public contact details can still be personal data, especially for sole traders. Users are responsible for a lawful purpose, data minimization, retention, applicable privacy law, eMAG terms, and electronic-marketing consent rules. Do not use extracted contacts for unsolicited outreach without the required legal basis and consent.
Local tests
npm installnpm test
The test suite covers seller discovery, company/contact parsing, masking, proxy-session selection, transient retries, proxy-outage stopping, blocked-page detection, recovery limits, deduplicated resume behavior, pricing events, and Actor schemas.
Support
When reporting an issue, include the run ID, marketplace country, operation, and affected public URL. Never include proxy credentials or API tokens.