Amazon India Catalogue by Category

Pulls every product Amazon shows on an amazon.in browse-node listing, page by page. One row is one product card in the order shoppers see it. Use it to rebuild a category's assortment in India, track MRP and selling price daily, and measure how much of a shelf your competitors buy with ads.

What you get

• Every card on the listing with page and position, so shelf order is preserved.
• is_sponsored on every row, taken from the card's own Sponsored label, so paid slots stay separable from organic ones.
• Pricing: price, the struck-through original_price and currency (INR).
• Demand signals: rating, rating_count, badges such as "Amazon's Choice", and the delivery promise on the card.
• Identity per product: asin, name, brand, image_url and product_url.
• Category context on every row: category, category_title, parent_category and breadcrumbs.
• Optional subcategory crawl: set expandSubcategories and each node's children are crawled too.

Input

Give it one or more browse-node ids or listing URLs.

{
  "categories": ["1389401031"],
  "locale": "in",
  "maxPages": 2,
  "expandSubcategories": false,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "IN" },
  "delayMs": 1500
}

• categories (required): node ids such as "1389401031" (Beauty), a https://www.amazon.in/b?node=... link or an /s?rh=n%3A... listing URL.
• locale: in for amazon.in, the only storefront this actor covers.
• maxPages: pages per node, 0 means every page.
• proxyConfiguration: residential proxy in India, already the default.

Output

One row per product card on one listing page.

{
  "platform": "amazon-in",
  "locale": "in",
  "category": "1389401031",
  "breadcrumbs": "Category",
  "page": 1,
  "position": 1,
  "asin": "B0CHX1W1XY",
  "name": "Product title as printed on the card",
  "brand": null,
  "price": 349,
  "original_price": 499,
  "currency": "INR",
  "rating": 4.2,
  "rating_count": 1820,
  "in_stock": true,
  "is_sponsored": true,
  "badges": [],
  "delivery": "FREE delivery Mon, 15 Sep",
  "product_url": "https://www.amazon.in/dp/B0CHX1W1XY",
  "fetched_at": "2026-09-12T09:21:44.118Z"
}

seller is always null on listing rows, Amazon does not print it on a category card. brand is null for most products: today's Amazon cards carry no brand line, and the brand is part of name. It is filled for books and media, where the card prints a byline. For a reliable brand per product, pass the ASINs to the matching Amazon product details actor. original_price is null when nothing is struck through.

Use cases

• Daily price and MRP tracking across a category, using price, original_price and rating_count.
• Share of shelf: match your products by asin or name and count them against the category total per page and position.
• Ad-slot share: is_sponsored shows which competitors buy the top of each page.
• Assortment and availability gaps: in_stock plus delivery shows what is listed and what ships late.

Notes and limits

• A listing page carries roughly 48 to 60 cards. Browse-node listings go up to about 400 pages per node.
• Keyword search is capped by Amazon at 7 pages. This actor reads browse nodes, so it is not affected.
• A residential proxy in India is needed. Datacentre and non-Indian addresses get a captcha or a bot check.
• amazon.in is challenged more often than the other Amazon storefronts. The actor re-mints the session and falls back to a browser for that page, so the run still completes.
• A category id that cannot be resolved is skipped and counted in failed_categories instead of failing the run.
• Live run: the Beauty node with subcategories returned 198 products across 6 nodes, 54 of them sponsored, in about two minutes.

FAQ

Do I need a proxy? Yes, residential in India. The actor already defaults to residential IN, and anything outside India is reliably challenged.

How many results can I get? About 48 to 60 products a page and up to roughly 400 pages per node, so a large node runs into tens of thousands of rows. Cap it with maxPages.

Does it need a login or an API key? No. Public listing pages only, no Amazon account and no seller credentials.

How are sponsored placements detected? From the Sponsored label Amazon prints on the card, so is_sponsored matches what an Indian shopper sees at that moment.

Do prices here reflect my pincode? No. Listing pages use the storefront default location. For pincode-accurate price, seller and delivery, use the Amazon India Product Details actor.