Hepsiburada Product Scraper

Point it at Hepsiburada category pages, or let it find them itself. Get back every product with its price, brand, stock status, shipping cost, return window and the position it held in the category listing. 31 fields per product, as JSON, CSV or Excel.

Three things that are different here

1. You pay only for records that contain data. A page that comes back blocked, failed or empty is written to a free skipped-pages list with the reason, and then dropped. It never reaches your dataset and never reaches your bill.

2. Every skipped page tells you why it was skipped. ROBOTS_DISALLOW, HTTP_403, NO_STRUCTURED_DATA, NO_PRODUCT_LIST, NETWORK_ERROR. If you hand it 500 categories and get 430 back, the remaining 70 are listed by URL with a reason code, free of charge. You never have to guess what happened to the difference.

3. It reads the structured data the site publishes for search engines. Not a rendered browser, not a private endpoint. Hepsiburada embeds schema.org product data in every category page for Google, and that is what this Actor parses. One page request returned a median of 36 complete products in the measured run, which is why it costs almost nothing to run.

What you get

Product Name, stock keeping unit, product URL, brand, colour, description, and up to ten image URLs with a count.

Price and availability Price, currency, stock status and item condition, exactly as the merchant publishes them.

Shipping and returns Shipping cost and currency, destination country, return window in days, whether returns are free, and the country the return policy applies to.

Category context Which category the product was listed in, the full breadcrumb path, the position it held in the listing, plus that category's average rating, rating count, lowest and highest price and total offer count. This lets you see not just what a product costs, but where it sits among its competitors.

Provenance sourceUrl, fetchedAt, httpStatus and filledFieldCount travel with every record.

Typical uses

Price monitoring across a competitor's catalogue. Tracking which brands dominate a category and at what price points. Watching stock status on products you resell. Building a price index for a product segment. Checking where your own listing ranks inside a category page.

Example record (trimmed)

{
  "name": "Philips 7500 Series Azur Steam Iron 3200W",
  "sku": "HBCV00003XBZIS",
  "brand": "Philips",
  "color": "Black",
  "price": 3299,
  "currency": "TRY",
  "availability": "InStock",
  "itemCondition": "NewCondition",
  "shippingCost": 49.99,
  "shippingCurrency": "TRY",
  "returnDays": 14,
  "returnFees": "FreeReturn",
  "imageCount": 4,
  "listPosition": 2,
  "categoryName": "Home Electronics",
  "categoryRatingValue": 4.27,
  "categoryRatingCount": 85409,
  "categoryLowPrice": 2,
  "categoryHighPrice": 8051987.59,
  "categoryOfferCount": 10000,
  "filledFieldCount": 29,
  "httpStatus": 200,
  "fetchedAt": "2026-09-17T09:14:02.118Z",
  "sourceUrl": "https://www.hepsiburada.com/ev-elektronik-urunleri-c-2147483638"
}

Input

Paste category URLs one per line, or leave the field empty and the Actor starts from the homepage and finds categories itself. Paths and full URLs both work.

maxItems caps how many products are written so a long run cannot produce an unexpected charge. maxPages caps how many pages are fetched. followSubcategories turns discovery off when you want only the URLs you listed.

Failures are loud

The run fails with an explanation rather than finishing quietly with less data than you expected. If the page structure changes, you get a parse error naming the affected pages, not an empty dataset. Counters are reconciled at the end of every run: pages fetched, products written, robots-blocked, HTTP failures, parse failures, empty pages. The full breakdown is written to the RUN_STATS key, and every skipped page to SKIPPED.

Transient gateway errors are retried up to three times before a page is given up on.

Limits and compliance

robots.txt is checked before every request and a disallowed path is never fetched. If robots.txt itself cannot be read, the run stops before making a single data request rather than guessing.

No personal data is collected. The output is built from an explicit list of known fields, so nothing outside that list can reach your dataset. Product listings, prices, shipping terms and return policies are commercial data, not personal data.

Prices change constantly. Every record carries fetchedAt so you always know when the figure was true.

Pricing

$0.50 per 1,000 products, everything included. No start fee, no minimum charge per run, and no separate platform usage line on your bill. The number on this page is the number you pay.

Paid Apify plans pay less, automatically — there is nothing to apply for: Bronze $0.45, Silver $0.40, Gold and above $0.35 per 1,000 products. The Free plan price is unchanged at $0.50.

You are charged per record written, and a record is only written when it contains data. Pages skipped by robots.txt, failed after three retries, or carrying no product list are reported in the run statistics and in the free SKIPPED list, and cost you nothing.

Measured performance

Run on 16 September 2026 from Apify's own network, no proxy:

Category pages fetched	400
Pages returning HTTP 200	400
Pages blocked	0
Products extracted	13,734
Median products per page request	36
Average response time	2.3 seconds
Categories discovered while crawling	2,056

Four hundred requests over seventeen minutes, not one blocked.