ASOS Scraper

ASOS Scraper at a glance

ASOS Scraper is a ready-to-run Apify actor from abotapi for collecting web data. Its documented output includes id, rowtype, product, brand and colour, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $2.00 per 1,000 results on the Apify Free plan and from $1.70 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: $2.00 per 1,000 results (Free plan), from $1.70 on paid plans
Output: Documented below · JSON, CSV, Excel
Inputs: 22 options

Scrape ASOS by keyword, category or URL. Every row carries the selling price and the original price, the discount, brand, colour and selling-fast flags. Sizes, per-size stock and reviews are one toggle away. Recurring change tracking is first-class.

What ASOS Scraper can do

Two ways to find products. Search by keyword, or paste a product, search or category link; a pasted link decides its own scope.
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.
Store demand signals included. New in, selling fast and restocking soon flags come straight off the listing card.
Size and stock on demand. Turn on Fetch product details for the complete size list, brand size, SKU, EAN and per-size stock, including low-stock and restocking flags.
Customer reviews on demand. Rating count, average rating, Fit and Quality scores and the reviews themselves, one toggle away.
Friendly brand and colour filters. Type names such as "Bershka" or "Black"; the actor resolves them against the store's own live list and fails loud on a typo instead of silently widening the search.

Choose what to collect

These inputs let you configure ASOS Scraper - Fashion, Prices, Discounts & Stock. Open the actor on Apify to enter your values and review the current options.

Supported input fields
Input	What it controls
`mode`string · required	How to start the scrape. 'search' runs store searches. 'url' processes the store URLs you paste: a product URL is fetched as a single product, and a search or category URL is paged like a search, its own query or category 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. Choices: search, url
`searchTerms`array	One or more things to search ASOS for, for example 'midi dress', 'slim jeans', 'white trainers'. 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 with only the filters applied.
`urls`array	Paste product URLs (https://www.asos.com/brand/product-name/prd/0000001, the short https://www.asos.com/prd/0000001 form works too), search URLs (https://www.asos.com/search/?q=midi+dress) or category URLs (https://www.asos.com/women/dresses/cat/?cid=8799). A pasted URL decides its own scope. Add &page=3 (search URLs) or &offset=48 (category URLs) to start the walk further in; a product URL ignores paging and returns that one product in full. The filters below narrow what the walks read: the brand, colour and ordering filters are sent to the store with every page, and the price bounds and Discounted rows only are applied to the rows this run reads.
`brandIds`array	Only these brands. Type brand NAMES (e.g. "Bershka", "Nike", "ASOS DESIGN"), the actor matches them against the store's own brand list and resolves the ids itself; unknown names fail the run with the available options listed. Numeric store ids (e.g. 15370) also work and pass through unchanged. Multiple values return the union. Applies in BOTH search mode and URL mode.
`baseColourIds`array	Only these base colours. Type colour NAMES (e.g. "Black", "Brown", "Multi"), the actor matches them against the store's own colour list and resolves the ids itself; unknown names fail the run with the available options listed. Numeric store ids (e.g. 4) also work and pass through unchanged. Multiple values return the union. Applies in BOTH search mode and URL mode.
`sortBy`string	The store's own server-side ordering, sent with every page of every 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. Choices: relevance, freshness, priceasc, pricedesc
`minPrice`integer	Only keep rows whose selling price is at least this many pounds. 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 15 more inputs

More input fields
Input	What it controls
`maxPrice`integer	Only keep rows whose selling price is at most this many pounds. 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.
`onSaleOnly`boolean	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.
`fetchDetails`boolean	Fetch each item's product page for the description, the full size list (brand size and store size), and per-size stock availability including low-stock and restocking flags. Slower, and charged once per record. Leave off for a fast crawl: identity, prices, discount, brand and colour are included either way, without a stock state (the store does not serve one on its listing cards).
`fetchReviews`boolean	Fetch each item's customer reviews: the rating summary (average, count and the Fit/Quality score breakdown) and the most recent reviews up to Max reviews per product. Slower, and charged once per record under the same details surcharge (never twice, even with Fetch product details also on). Leave off by default.
`maxReviewsPerProduct`integer	Cap on review rows returned per product when Fetch reviews is on. The store serves one reviews page per product to automated readers, so this is a cap, not a pagination promise: rows beyond it are not fetched.
`maxItems`integer	The single cap on this run: stop after collecting this many records across all search terms and URLs. Set 0 for unlimited.
`maxPages`integer	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.
`resumeFromRunId`string	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.
`incrementalMode`boolean	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 and stock changes ARE reported as UPDATED: on a store they are the signal, not noise. 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.
`stateKey`string	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.
`emitUnchanged`boolean	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.
`emitExpired`boolean	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.
`mcpConnectors`array	Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify, Settings, API & 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).
`notionParentPageUrl`string	URL or id of the Notion page under which record pages are created. Required to enable the Notion export; ignored by other connectors.
`maxNotifyListings`integer	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.

recordIdID (text)

rowTyperowType

titleProduct (text)

brandBrand (text)

colourColour (text)

pricePrice (number)

priceTextPrice (as shown) (text)

originalPriceOriginal price (number)

onSaleOn sale (text)

discountPercentDiscount % (number)

currencyCurrency (text)

isNewNew in (text)

Show 13 more fields

isSellingFastSelling fast (text)

inStockIn stock (text)

sellerSeller (text)

productTypeProduct type (text)

descriptionDescription (text)

sizesSizes (array)

reviewsReviews (text)

imageUrlImage (image)

urlURL (link)

changeTypeChange type (incremental mode) (text)

changedFieldsChanged fields (incremental mode) (array)

firstSeenAtFirst seen (incremental mode) (date)

lastSeenAtLast seen (incremental mode) (date)

Example output

An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.

{
  "recordId": "10000001",
  "rowType": "product",
  "productId": "10000001",
  "url": "https://www.asos.com/sample-brand/sample-name-tiered-midi-dress/prd/10000001",
  "title": "Sample Name Tiered Midi Dress",
  "brand": "Sample Brand",
  "brandId": "15370",
  "colour": "Navy",
  "colourWayId": "10000005",
  "price": 45,
  "priceText": "£45.00",
  "originalPrice": 60,
  "onSale": true,
  "discountPercent": 25,
  "currency": "GBP",
  "isNew": false,
  "isSellingFast": true,
  "isRestockingSoon": false,
  "isPromotion": false,
  "hasMultipleColours": false,
  "imageUrl": "https://images.example.com/products/sample-dress/10000001-1.jpg",
  "productCode": "2000001",
  "productType": "Dresses",
  "description": "A tiered midi dress in a relaxed fit, with a round neck and long sleeves.",
  "sizes": [
    {
      "size": "UK 8",
      "brandSize": "S",
      "sku": "0000001",
      "ean": "0000000000000",
      "available": true,
      "inStock": true,
      "isLowInStock": false,
      "isRestockingSoon": false,
      "seller": "SAMPLE BRAND LTD"
    }
  ],
  "inStock": true,
  "seller": "SAMPLE BRAND LTD",
  "reviews": {
    "ratingCount": 120,
    "averageRating": 4.3,
    "averageFromPage": true,
    "fitScore": 3.9,
    "qualityScore": 4.1,
    "reviews": [
      {
        "id": "1",
        "rating": 5,
        "title": "Great fit",
        "text": "Fits true to size and the fabric feels good.",
        "submittedAt": "2026-01-01T00:00:00Z",
        "recommended": true,
        "colour": "Navy"
      }
    ]
  },
  "detailCarriedForward": null,
  "scrapedAt": "2026-01-01T00:00:00Z"
}

Ways to use this data

Pricing and promo tracking: monitor a search or category for price cuts, new discounts and demand flags over time.
Assortment and stock research: get notified when a product goes selling fast, runs low on a size, or comes back in stock.
Trend and competitor research: track which brands and colours dominate a category or a search term.
Review and quality research: pull rating counts, Fit and Quality scores and the reviews themselves for supplier or QA scoring.

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 ASOS Scraper return?

The documented output for ASOS Scraper includes id, rowtype, product, brand, colour, price, price (as shown) and original price. Availability of each field depends on the source page and the selected mode.

How much does ASOS Scraper cost?

It costs $2.00 per 1,000 results on the Apify Free plan and from $1.70 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.