Flipkart Product Scraper & Price Monitor

Search Flipkart by keyword or feed it product URLs and get one flat row per product: price, MRP, discount, rating, rating and review counts, stock, image, category, and — when you ask for details — the full specification table, highlights, seller and delivery date. No login, no cookies, India exit by default so prices are the real INR prices Flipkart shows a shopper in India.

What you get

One row per product (id = Flipkart product id, so the same item from a search and from a product URL is a single row):

id, productId, url, title, brand, price, mrp, currency, discountPercent, rating, ratingCount, reviewCount, inStock, imageUrl, category, highlights, specs, seller, sellerRating, delivery, query, rank, page, source, scrapedAt.

Example output

Real rows from the example dataset.

Search row (searches: ["headphones"], rank 1):

Field	Value
productId	ACCESZCHHGX9YFBN
title	Skullcandy Crusher Bluetooth Headset with Mic
brand	Skullcandy
price / mrp / discountPercent	6999 / 39999 / 82
rating / ratingCount / reviewCount	4.4 / 1098 / 209
inStock	true
category	Audio & Video > Headset > Headphones
url	https://www.flipkart.com/skullcandy-crusher-bluetooth-headset-mic/p/itmcb06279c54724?pid=ACCESZCHHGX9YFBN

The same product with fetchDetails: true adds:

Field	Value
seller / sellerRating	SuperComNet / 4.1
delivery	Delivery by Wednesday, 16 Sep
highlights	["Up to 40 hrs of Battery Life", "With Deep Bass", "Bluetooth Connectivity"]
specs	{"Brand": "Skullcandy", "Model ID": "SCCRW", "Headphone Type": "On the Ear", "Color": "Black", ...} (22 keys on this product)
category	Audio & Video > Headset > Headphones > Wireless Headphones > Skullcandy Wireless Headphones

Use cases

• Price tracking. Run a saved task in monitor mode on a list of product URLs or a keyword; you get rows only when price, stock or rating changed, plus a webhook or Telegram message.
• Competitor and catalogue research. Pull 120+ products for a keyword with MRP, discount and rating counts and see where a category really prices.
• Assortment and spec sheets. fetchDetails gives the full specification table as a dictionary, ready for a spreadsheet.

Input

Field	Meaning	Default
searches	Keywords or full Flipkart search URLs	["headphones"]
productUrls	Product URLs or bare product ids	empty
maxPagesPerSearch	Result pages per keyword, 40 products each (1-50)	3
fetchDetails	Open each product page for specs, highlights, seller, delivery	false
minPrice, maxPrice	Keep only products inside this INR range	empty
strictQueryMatch	Skip result pages Flipkart fills with unrelated products	true
maxItems	Stop after this many rows	100
mode	scrape, or monitor for only new/changed rows	scrape
monitorKey, webhookUrl, telegramBotToken, telegramChatId	Monitor-mode state key and alert targets	empty

Pricing

Event	Price
result	$0.0015 per product ($1.50 per 1,000)
monitor-check	$0.005 per monitor run
change	$0.0015 per new/changed product

You are charged only for rows actually pushed. A run that finds nothing charges no result events.

Why this actor

• Half the price per product of the other Flipkart scrapers on the Store.
• Search rows are already rich: price, MRP, discount, rating, both counts, stock and image come from the search page itself, so a 120-product sweep is 3 requests, not 123.
• Built-in monitor mode with webhook and Telegram alerts — price, stock and rating are the change fingerprint.
• The exit is pinned to India, so prices are INR and availability is the one Indian shoppers see.

Limits (read these)

• Flipkart never returns an empty search page. A keyword that matches nothing gets a generic catalogue page of unrelated products. With strictQueryMatch on (the default) the actor recognises such a page — no breadcrumb category, and none of the first five titles containing a word of your keyword — skips it, stops paging that keyword and charges you nothing. A run like that ends with zero rows and no_matches in the run summary. Broad keywords whose products really do match (birthday gift) are kept.
• Flipkart repeats a card or two inside a page and between pages; rows are de-duplicated by product id, so a 3-page sweep usually yields a little under 120 rows. rank is the position Flipkart gave the card on the page, so it skips the numbers of the removed duplicates and is not a dense 1..N counter.
• seller, sellerRating, delivery, specs and highlights exist only on rows fetched with fetchDetails or from productUrls.
• delivery is the date Flipkart quotes for a generic Indian address, without a pincode; the exact date for your pincode can differ.
• Prices exclude bank/card offers and exchange discounts. price is the selling price, mrp the struck-through maximum retail price.
• No buyer reviews, no reviewer names, no seller contact details — only aggregate rating, ratingCount and reviewCount.

FAQ

Do I need a Flipkart account or cookies? No. Every request is made as a logged-out visitor.

Why are some prices different from what I see? Flipkart personalises by location and shows bank-offer prices on the page; this actor returns the plain selling price from an Indian exit, without offers.

My keyword returned nothing at all — is the actor broken? No. Flipkart answers an unmatchable keyword with a page of unrelated products instead of an empty page; the actor drops that page rather than billing you for 40 irrelevant rows. Check your spelling, or set strictQueryMatch: false to see exactly what Flipkart returned.

What happens when a product URL is dead? Flipkart answers 200 with an empty shell. The row is skipped, not charged, and the run summary says why.

How do I track prices? Save the actor as a task with mode: monitor and your product URLs or keyword, schedule it, and set webhookUrl or the Telegram fields. Rows come back only when price, inStock or rating changed.

Changelog

• 0.1: initial release — keyword search with 40 products per page, product-page details (specs, highlights, seller, delivery), price range filter, unrelated-result pages skipped and unbilled, monitor mode.

---

If this actor saved you time, a short review on its Store page genuinely helps other people find it. Found a bug or need a field that is missing? Open a ticket on the Issues tab.