Flipkart Scraper

What does Flipkart Scraper do?

Flipkart Scraper is a public Flipkart product data API alternative for bounded search, category, and product-page extraction. It reads only public HTML and the public structured state exposed by Flipkart; it does not log in, reuse protected sessions, call private APIs, bypass CAPTCHAs, or evade access controls.

Why use Flipkart Scraper?

Use it to build product catalogs, price-monitoring datasets, assortment research, marketplace analysis, and public availability snapshots. The Actor can enrich result cards with product-page metadata such as Schema.org offers, descriptions, seller signals, specifications, ratings, delivery and return-policy objects, media links, badges, and bounded raw public objects.

Apify provides scheduling, API access, dataset downloads, monitoring, and integrations around each run. Keep requests small and paced: Flipkart may change public page structure or stop serving a page because of traffic, region, device, login, CAPTCHA, WAF, or other access controls.

What data can it extract?

Field	Type	Description
productId, sku, listingId	string	Public product and listing identifiers.
title, description, brand, category	string	Public catalog and product-page text.
price, mrp, discountPercent, currency	number/string	Observed price signals.
rating, ratingCount, reviewCount	number	Public review signals.
seller, availability, shipping, returnPolicy	object/string	Public seller and fulfillment signals.
keySpecs, specifications, variants, offers	array/object	Public product attributes and commercial signals.
images, videos, url	array/string	Public media and product links.
sourceMetadata, rawPublic	object	Provenance and bounded raw public state.

How to scrape Flipkart

1. Select search, byCategory, or byUrl in the Input tab.
2. Provide a search phrase, a public Flipkart category URL, or public product URLs.
3. Set maxItems, page bounds, filters, enrichment toggles, pacing, retries, and timeout values.
4. Start the Actor and download the dataset as JSON, CSV, Excel, HTML, or another supported format.

includeDetails is enabled by default and uses a small worker pool to fetch public product pages. includeMedia, includeRatings, includeOffers, includeVariants, and includeRawPublic control optional fields. Direct HTTP remains the default. The standard proxyConfiguration input can route bounded requests through Apify Proxy when direct cloud traffic is unavailable; requested proxy configuration fails closed if unavailable.

How much does it cost?

Cost depends on request count, response size, detail enrichment, and Actor runtime. Search-only runs use listing pages; detail enrichment adds one bounded public request per selected product. Start with a small maxItems, then increase it after checking runtime and access behavior. Apify platform compute and storage pricing is shown in the Console for your account and plan.

Input

See the Input tab for every configuration option. mode is required. byUrl accepts only public Flipkart URLs. The Actor enforces bounded values for pages, items, concurrency, pacing, retries, and timeouts. It does not accept credentials, cookies, session tokens, or non-Flipkart URLs.

Output

Product rows contain public product business fields. If one of several requested URLs is blocked or fails, successful product rows are preserved and the dataset also receives an exact four-field diagnostic record: url, error, errorCode, and scrapedAt. If no usable row is available, the dataset receives only the diagnostic. Run status, counts, request metrics, and barrier state are stored in OUTPUT_SUMMARY (OUTPUT remains a compatibility alias); no run-summary row is appended to the dataset. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

{
  "recordType": "product",
  "productId": "EXAMPLEPID123",
  "title": "Example Intel Core Laptop",
  "price": 49999,
  "currency": "INR",
  "url": "https://www.flipkart.com/example-product/p/itmexample123?pid=EXAMPLEPID123"
}

Tips and advanced options

Use includeDetails: false for a faster listing-only run. Use maxPages and maxItems together to cap work. Increase pacingMs when making repeated runs. Retries apply only to transient network and server failures; CAPTCHA, login, paywall, geofence, rate, device, WAF, and access barriers are detected and stopped without bypass attempts.

For local development, place a bounded JSON input in the normal local store or pass a file directly:

apify run --purge --input-file ../qa-inputs/flipkart-scraper/cloud-validation.json
npm run validate

After the Actor is mapped to the correct Actor in your authenticated Apify account, deploy and run the same bounded input with:

apify push --wait-for-finish 600 --json
apify call --input-file ../qa-inputs/flipkart-scraper/cloud-validation.json --memory 512 --timeout 300 --json

Inspect the cloud run's default dataset before treating the run as successful. Cloud validation is not a substitute for the local dataset checks, and neither workflow changes public Store visibility or pricing.

FAQ, disclaimers, and support

Why did I receive a diagnostic record?

Flipkart may return an access barrier, a changed public state shape, an empty result, or a transient failure. Read the exact diagnostic errorCode and error, then inspect OUTPUT_SUMMARY for barrier and request outcome fields. On multi-URL runs, any successful public product rows remain available beside the diagnostic; no placeholder product rows are generated.

Is this Actor allowed to scrape Flipkart?

Our Actors are ethical and do not extract any private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. We therefore believe that our Actors, when used for ethical purposes by Apify users, are safe. However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers. You are responsible for following Flipkart’s terms, robots guidance, and applicable law.

For programmatic access, use the API tab. For feedback or changed fields, use the Issues tab.