Flipkart Seller Scraper

What does Flipkart Seller Scraper do?

Flipkart Seller Scraper collects public seller-offer snapshots from Flipkart All Sellers comparison pages. It is a public-page Flipkart API alternative for seller names, ratings, prices, delivery, policies, offers, optional product detail, and bounded media/link evidence. It does not access private seller accounts, private APIs, authenticated sessions, or protected data.

The Actor uses visible browser DOM evidence. If Flipkart shows CAPTCHA, login, paywall, geofence, rate-limit, device, WAF, or another access barrier, the Actor stops and writes an exact four-field diagnostic record: url, error, errorCode, and scrapedAt.

Generated by: OpenAI Codex with GPT-5.6

Why use Flipkart Seller Scraper?

Use the results for public price comparison, seller monitoring, catalog research, offer analysis, and delivery-policy checks. The Actor supports product URLs, direct sellers-page URLs, public search queries, and public search URLs. It includes bounded retries, pacing, concurrency controls, optional filters, and optional detail, media, and rating collection.

Apify provides scheduling, API access, dataset exports, integrations, monitoring, and runtime proxy configuration. Proxy settings are honored only in an Apify runtime that supports them; they are not used to bypass a visible access barrier.

What data can Flipkart Seller Scraper extract?

Field	Type	Description
sellerName	string	Public seller name.
sellerRating	number	Visible seller rating.
productName	string	Public product name.
priceAmount / price	number / string	Numeric and display seller price.
originalPrice / discount	string	Public MRP and discount display.
returnPolicy	string	Public return or replacement policy.
deliveryTime	string	Public delivery estimate.
allOffers	string[]	Bounded visible offer text.
productImages / productLinks	object[]	Optional public media and links.
error, errorCode	string	Exact fail-closed diagnostic fields when data is blocked or unavailable.

The dataset schema contains the complete emitted business-field contract, including public inventory, fulfillment, badges, ratings/reviews, location/contact details only when disclosed, source metadata, timestamps, and bounded raw public objects. Run outcomes and transport metadata are stored in OUTPUT_SUMMARY.

How to scrape Flipkart seller offers

1. Open the Input tab and choose productUrl, sellersPageUrl, searchQuery, or searchUrl mode.
2. Supply HTTPS Flipkart URLs, a query, or an array of queries.
3. Set maxPages, maxItems, concurrency, pacing, retries, timeouts, and optional filters.
4. Choose whether to include product detail, public media/links, and visible ratings.
5. Click Start and inspect the dataset or diagnostic rows.

For programmatic workflows, use the API tab or the dataset API link in the Output tab. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

How much does it cost to scrape Flipkart?

This Actor uses browser compute units, so cost depends on the number of public pages, browser concurrency, optional product-detail pages, retries, and pacing. Start with one URL, maxPages: 1, and a small maxItems value. Larger runs can use scheduling and higher concurrency within Flipkart’s limits. The Actor does not promise a fixed number of results when the public site presents an access barrier.

Input

See the input tab for full configuration options. Important fields include productUrls, sellersPageUrls, query, queries, searchUrls, maxPages, maxItems, maxConcurrency, minDelayMs, maxDelayMs, maxRetries, navigationTimeoutSecs, selectorTimeoutSecs, postNavigationWaitMs, includeDetail, includeMedia, includeRatings, filters, pincode, and proxyConfiguration.

filters supports minimum seller/product ratings, minimum discount, Flipkart Assured requirement, and case-insensitive exact seller names. A missing public value does not pass a filter that requires it.

Example input

{
  "mode": "productUrl",
  "productUrls": [
    "https://www.flipkart.com/example-product/p/itm00000000000000"
  ],
  "maxItems": 20,
  "includeDetail": true,
  "includeRatings": true
}

Output

Seller rows contain public seller-offer business fields. Blocked, empty, failed, or filtered tasks remain visible as exact diagnostics instead of being represented as successful seller data.

{
  "recordType": "Flipkart seller offer",
  "sellerName": "Example Seller",
  "sellerRating": 4.2,
  "productName": "Example wireless headset",
  "price": "₹1,999",
  "deliveryTime": "3 days"
}

{
  "url": "https://www.flipkart.com/sellers?pid=EXAMPLEPID123",
  "error": "A public-page access barrier was observed.",
  "errorCode": "ACCESS_BARRIER",
  "scrapedAt": "2026-09-08T00:00:00.000Z"
}

Key-value store

The Actor writes OUTPUT_SUMMARY to the default key-value store with status, mode, seller-row and diagnostic counts, provenance, transport, browser context, and completion time. OUTPUT is a compatibility alias. Dataset rows remain seller-offer business records or exact diagnostics.

Tips and advanced options

Use includeDetail: false and includeMedia: false when seller-only output is sufficient. The browser uses a consistent Chromium profile (en-IN, Asia/Kolkata, 1365×768), keeps cookies across product-to-seller navigation within one attempt, and rotates the browser/proxy session only between retries. Retries use exponential backoff with jitter. Increase minDelayMs and keep maxConcurrency low when the site is busy. Access barriers are fail-closed and are never bypassed.

For bounded local validation, run the direct test input and inspect the generated dataset:

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

After confirming the exact owned remote Actor mapping, deploy and run the cloud input with a bounded timeout and memory allocation:

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

Always inspect the cloud dataset itself. A terminal run status alone does not prove that public seller records were extracted.

FAQ, disclaimers, and support

Does this Actor scrape private seller data?

No. It only reports what the public Flipkart surface discloses. Seller location or contact fields remain empty unless the public seller surface explicitly shows them.

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.

Respect Flipkart’s terms, robots guidance, applicable laws, and rate limits. For feedback or a public-page change, use the Issues tab. Use the API tab for programmatic access.