# Flipkart Product Details (`ikmal_suzali_atr/flipkart-details`) Actor

Full Flipkart product details by FSN or URL — title, brand, price, MRP, discount, rating and review counts, seller and seller rating, stock, serviceability and delivery for a pincode, category path, highlights, specifications, description, images, variants and offers. Also Flipkart Grocery and Minut

- **URL**: https://apify.com/ikmal\_suzali\_atr/flipkart-details.md
- **Developed by:** [AtTheRate AI](https://apify.com/ikmal_suzali_atr) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $7.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Flipkart Product Details

Returns the complete Flipkart product page for any FSN or product URL as one flat row: title, brand, price, MRP, discount, ratings and review counts, the buybox seller and its rating, stock, specifications, images, variants and offers. Add a pincode and you also get serviceability, the delivery promise and the local seller. Grocery and Minutes use the same call.

### What you get

- Price economics: `price`, `original_price`, `discount_percent`, plus `nep_price` and `xtra_saver_price` where shown.
- Ratings in full: `rating`, `rating_count`, `review_count` and the 1 to 5 `rating_histogram`.
- Buybox intelligence: `seller`, `seller_id`, `seller_rating` and the `fbf` fulfilment flag.
- Location answers: `serviceable`, `unserviceability_reason`, `delivery`, `sla` and, on Minutes, `dark_store_id`.
- Page content: `category_path`, `highlights`, `specifications`, `description`, `images`, `variants`, `offers`, `policies`, plus `in_stock` and `availability_status`.
- Nothing is dropped: an unknown FSN returns a `found: false` row carrying the `error` text instead of failing the run.

### Input

`products` is required. A pincode is optional for Flipkart and mandatory for Grocery and Minutes.

```json
{
  "products": [
    "PSLGFSY3FKSMGZVZ",
    "https://www.flipkart.com/product/p/itm?pid=MOBHQFDZTHKKVGKG"
  ],
  "marketplace": "FLIPKART",
  "pincode": "122002",
  "concurrency": 2,
  "delayMs": 250,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "IN"
  }
}
```

- `products`: 16-character FSNs or product URLs. `marketplace` is `FLIPKART`, `GROCERY` or `HYPERLOCAL`; the last two require `pincode`.
- `pincode`: unlocks serviceability, the delivery promise and the local seller and price.
- `proxyConfiguration`: residential country IN is the default.

### Output

One row per requested product.

```json
{
  "requested": "PSLGFSY3FKSMGZVZ",
  "id": "PSLGFSY3FKSMGZVZ",
  "found": true,
  "pincode": "122002",
  "name": "MUSCLEBLAZE Biozyme Performance Whey Protein",
  "brand": "MUSCLEBLAZE",
  "price": 3999,
  "original_price": 4999,
  "discount_percent": 20,
  "rating": null,
  "rating_count": null,
  "review_count": null,
  "in_stock": true,
  "serviceable": true,
  "seller": null,
  "seller_rating": null,
  "marketplace": "FLIPKART",
  "fetched_at": "2026-09-11T08:57:51.443Z"
}
```

`rating`, `rating_count`, `review_count`, `seller` and `seller_rating` are null when Flipkart does not publish them, as above; on reviewed products they fill in with `rating_histogram`. `stock_quantity` is always null: Flipkart publishes no unit count. `serviceable`, `sla` and `dark_store_id` stay null unless you pass a pincode, and `dark_store_id` only fills in on Minutes.

### Use cases

- Buybox monitoring: watch `seller`, `seller_id` and `seller_rating` shift by pincode and over time.
- Price tracking on `price` and `discount_percent`, with `offers` for the bank and exchange deals that move the effective price.
- Serviceability mapping from `serviceable`, `unserviceability_reason` and `sla`, and review velocity from `rating_count` and `rating_histogram`.
- Content and compliance audits against `specifications`, `highlights`, `images` and `policies`.

### Notes and limits

- One call per product and no browser, so throughput is high. `concurrency` caps at 4 and a session serves up to 500 fetches.
- An invalid `pincode` is rejected before the run starts, so no compute is billed.
- `GROCERY` or `HYPERLOCAL` without a pincode is rejected up front: those surfaces only exist for a resolved location.
- An unknown or delisted FSN produces a `found: false` row with the reason, verified on a deliberately invented FSN.
- These rows carry no sponsored or ad flag: a product page is not an ad surface.

### FAQ

**Do I need a proxy?** A residential proxy in India is recommended and is the default. Flipkart answers without one at low volume, but a proxy avoids throttling at scale.

**How many results can I get?** One row per product, with no cap on the product list. Fetches run up to 4 in parallel.

**Does it need login or an API key?** No Flipkart account, cookie or key is required.

**What exactly does the pincode change?** It sets the delivery location before the product is read, so stock, the delivery promise and the buybox seller reflect that area. On Minutes it also exposes the dark store serving you.

# Actor input Schema

## `products` (type: `array`):

Flipkart FSNs (16 chars, e.g. PSLGFSY3FKSMGZVZ) or product URLs.

## `marketplace` (type: `string`):

Grocery and Minutes need a pincode.

## `pincode` (type: `string`):

Optional Indian pincode: unlocks serviceability, delivery promise and the local seller/price. Required for Grocery and Minutes.

## `concurrency` (type: `integer`):

1–4.

## `delayMs` (type: `integer`):

Pause between fetches.

## `proxyConfiguration` (type: `object`):

On the Apify platform this decides egress; a residential proxy in India is recommended. On our own servers it is ignored and our residential proxy is used.

## Actor input object example

```json
{
  "products": [
    "PSLGFSY3FKSMGZVZ"
  ],
  "marketplace": "FLIPKART",
  "concurrency": 2,
  "delayMs": 250,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "IN"
  }
}
```

# Actor output Schema

## `results` (type: `string`):

One row per product.

## `summary` (type: `string`):

Counts for the run: what was requested, captured, skipped and failed.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "products": [
        "PSLGFSY3FKSMGZVZ"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ikmal_suzali_atr/flipkart-details").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "products": ["PSLGFSY3FKSMGZVZ"] }

# Run the Actor and wait for it to finish
run = client.actor("ikmal_suzali_atr/flipkart-details").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "products": [
    "PSLGFSY3FKSMGZVZ"
  ]
}' |
apify call ikmal_suzali_atr/flipkart-details --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ikmal_suzali_atr/flipkart-details"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/G8M1v0VNOvM2rpkc8/builds/Af0zkNPDE2Xgj1s8S/openapi.json