Allegro Listings Scraper avatar

Allegro Listings Scraper

Pricing

$2.50 / 1,000 products

Go to Apify Store
Allegro Listings Scraper

Allegro Listings Scraper

The Allegro Listings Scraper enables quick and efficient data extraction from allegro.pl, allegro.cz, and allegro.sk. It gathers information from listing pages on one of Europe’s leading e-commerce marketplaces, providing valuable insights for market analysis and price monitoring.

Pricing

$2.50 / 1,000 products

Rating

5.0

(2)

Developer

FalconScrape

FalconScrape

Maintained by Community

Actor stats

3

Bookmarked

66

Total users

5

Monthly active users

a day ago

Last modified

Share

Collect prices, seller information and product demand signals from Allegro search results, category pages and seller catalogs. Use offer IDs and timestamps to compare repeated runs across Poland, Czechia and Slovakia.

Quick start

  1. Open an Allegro search, category or seller page and apply the filters you need.
  2. Paste its URL into Search URLs.
  3. Set Max items per URL and optionally Maximum total records.
  4. Run the actor and export the dataset as JSON, CSV or Excel.

Product/offer detail URLs are not supported. This actor extracts listing cards; it does not visit every product page for descriptions, EAN codes or stock.

Seller catalog sample

{
"searchUrls": ["https://allegro.pl/uzytkownik/X-KOM_PL"],
"maxItemsPerUrl": 100,
"maxItems": 100
}

Search and category research

{
"searchUrls": [
"https://allegro.pl/listing?string=iphone",
"https://allegro.pl/kategoria/komputery"
],
"maxItemsPerUrl": 50,
"maxItems": 100
}

Czech and Slovak listings

{
"searchUrls": [
"https://allegro.cz/vyhledavani?string=iphone",
"https://allegro.sk/vyhladavanie?string=iphone"
],
"maxItemsPerUrl": 50
}

Data you receive

Existing field names (label, link, price, etc.) are retained. Optional missing information is null, not zero or false. Cards without a valid offer ID, title, URL, price or currency are rejected and reported as an incomplete extraction.

FieldsMeaning
offerId, productIdOffer identity and, where supplied, Allegro catalog product identity. They are not interchangeable.
label, link, mainThumbnailListing title, resolved destination URL and thumbnail.
price, currencyDisplayed price and source currency. No currency conversion.
deliveryCost, priceWithDeliveryListing delivery cost and total including delivery, where supplied.
sellerId, sellerName, sellerRatingSeller ID, login and positive-feedback percentage. If a storefront card omits the login, it is derived from the input seller URL.
isSuperSeller, isFreeDeliverySource flags; free delivery does not imply Smart! membership.
isPromoted, isSponsoredSource advertising flags.
purchases, purchasesLabel, purchasesDescription, purchasesScopeParsed recent-buyer count plus original label and explanatory tooltip. See scope below.
ratingAverage, ratingCountProduct review score and count, where supplied.
productOffersCountNumber of offers for the catalog product, where supplied.
marketplace, inputUrlOffer destination marketplace and input listing URL. Allegro Lokalnie cards embedded in Allegro results are retained; direct Lokalnie crawling is not supported.
scrapedAt, page, positionUTC observation time, source page number and one-based product-card position on that page.

Purchase counts are not necessarily sales by the displayed seller. Allegro can report recent buyers across many sellers of the same catalog product. purchasesScope is product when the source explanation explicitly identifies that scope; otherwise it is unknown. Always retain the label and description when interpreting the count. Abbreviated or absent counts return null. Ratings can also apply to the catalog product rather than the individual offer.

Limits, duplicates and failures

  • maxItemsPerUrl: maximum valid, unique records per source; defaults to 50.
  • maxItems: optional total record cap across all sources. The Apify paid-result cap also applies.
  • maxPagesPerUrl: safety limit on fetched pages per source; defaults to 100, maximum 10,000. A URL with p=101 starts at page 101; this does not bypass limits imposed by Allegro.
  • maxConcurrency: simultaneous source URLs; defaults to 3, maximum 5. Pages for one source are fetched in order. Already-running requests may finish after the global cap is reached, but their extra rows are not saved.
  • Repeated offer IDs are removed within each input URL. Different source URLs retain separate observations so keyword/category context is preserved. Repeated identical input URLs are collapsed.
  • Results are saved after each page. If a later page fails, earlier dataset rows remain available and the run is marked FAILED. Check RUN-SUMMARY in the default key-value store for the affected URL/page and reason. A partial dataset is not a complete catalog.
  • Hitting an explicit item/page cap is reported as limited in the summary, not as full coverage. Allegro's final available page also may represent only a capped subset of a category.
  • A valid empty listing can finish successfully. A missing listing payload or completely invalid product payload fails instead of silently returning an empty dataset.
  • There is no automatic cross-run resume or price-history database. nextPage in the summary is diagnostic; repeating a partly saved page requires deduplication against the previous dataset.

Daily price monitoring

Create an Apify task using your listing URLs and schedule it daily. Export or append each run's dataset to your spreadsheet or database. Join observations using marketplace + offerId, retaining scrapedAt and inputUrl. Compare priceWithDelivery only when currencies and shipping context match. Do not mark an offer unavailable just because it is absent from a failed, filtered or capped crawl.

Pricing and diagnostics

The actor's Pricing tab is authoritative for current customer charges. The actor records provider request counts, known Scrapfly credits, requests whose cost is unknown, saved records and per-source completion in RUN-SUMMARY. A credits-per-1,000-records figure is available only when all request costs are known and records were saved. It measures provider credits, not dollars or your invoice.

Local development

Requires Node.js 20+ and a maintainer-provided SCRAPFLY_API_KEY environment variable. Customers using the hosted actor do not supply this key.

npm ci
npm run build
npm test

Run a bounded live benchmark with five cases, at most two pages per case and no retries:

npm run benchmark -- --env-file=/absolute/path/to/test.env

The benchmark reads only SCRAPFLY_API_KEY from that file. Results and sample rows are written under ignored storage/benchmark/. Use --case=pl-search (or pl-category, pl-seller, cz-search, sk-search) for a single case. Benchmarks consume Scrapfly credits. The dated cost analysis is in docs/reliability-and-costs.md.

Need more detail for the products you discover? Pass the offer URLs in link to the Allegro Product Scraper to extract product specifications, stock, images, shipping, seller ratings and variant links across Poland, Czechia and Slovakia.

Need to compare sellers for the same product? Use the Allegro Price Comparison Scraper with an Allegro Poland product or offer URL, or an EAN, to compare seller offers, prices, delivery costs, condition and Smart! status.