# Blinkit Product Details by Pincode (`ikmal_suzali_atr/blinkit-details`) Actor

Blinkit product details for any product id or URL at any Indian pincode: price, MRP, discount, pack size, live inventory and sold-out state, images, breadcrumb, attributes, seller, sibling pack sizes, dark store id. One row per product × pincode.

- **URL**: https://apify.com/ikmal\_suzali\_atr/blinkit-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

## Blinkit Product Details by Pincode

Reads the full Blinkit product page for any product id or product URL, at any Indian pincode, and returns one row per product and pincode. Blinkit prices and stocks per dark store, so the same product comes back at a different price, inventory count and store depending on the pincode you ask for.

### What you get

- Price economics per store: `price`, `original_price`, `discount_percent` and the promotional `offer` text.
- Live inventory depth: `stock_quantity` is the unit count Blinkit reports, with `in_stock`, `is_sold_out` and `availability` alongside it.
- Store, delivery and page content: `store_id`, `merchant_id`, `delivery`, `name`, `brand`, `unit`, `category_path`, `description`, `highlights`, `specifications`, `images` and sibling pack sizes in `variants`.
- Seller data from the expanded product panel: `seller` and `seller_fssai`. Every row also carries `pincode`, `lat`, `lon` and `location_label`.
- No input is ever dropped: rows with `found: false` carry a `reason` of `invalid_id`, `pincode_unresolved`, `not_serviceable`, `not_found`, `blocked` or `failed`.

### Input

Both `productIds` and `pincodes` are required. Every product is fetched at every pincode.

```json
{
  "productIds": [
    "530158",
    "https://blinkit.com/prn/amul-gold-full-cream-milk/prid/12872",
    "999999999"
  ],
  "pincodes": ["122002", "560001"],
  "maxConcurrency": 2,
  "delayMs": 400,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "IN"
  }
}
```

- `productIds`: Blinkit product ids such as `530158`, or product URLs in the `/prn/<slug>/prid/<id>` form.
- `pincodes`: 6-digit Indian pincodes. Each one becomes its own store binding.
- `maxConcurrency`: product fetches in flight per pincode, 1 to 4. Two is safe.
- `proxyConfiguration`: residential country IN is the default.

### Output

One row per product and pincode. The input above produced 6 rows: 4 fetched and 2 marked not found for the invented id.

```json
{
  "requested": "12872",
  "product_id": "12872",
  "pincode": "122002",
  "location_label": "Gurgaon, Gurugram",
  "found": true,
  "name": "Amul Gold Full Cream Milk",
  "brand": null,
  "price": 36,
  "original_price": 36,
  "discount_percent": 0,
  "unit": "500 ml",
  "in_stock": true,
  "stock_quantity": 12,
  "offer": null,
  "store_id": "43483",
  "product_url": "https://blinkit.com/prn/p/prid/12872",
  "fetched_at": "2026-09-11T09:20:40.690Z"
}
```

`rating`, `rating_count`, `review_count` and `seller_rating` are always null: the Blinkit product page carries no ratings. `offer` is null when nothing is running, and `brand` is null when the brand sits inside `name`.

### Use cases

- City-by-city price comparison for a fixed SKU list, using `price` and `original_price`.
- Inventory depth monitoring with `stock_quantity`, which thins out long before `in_stock` flips.
- Serviceability mapping: run a wide pincode list and read the `not_serviceable` rows as your coverage map.
- Pack-ladder analysis from `variants`, which lists sibling pack sizes with their own price and stock.

### Notes and limits

- Blinkit sits behind Cloudflare and refuses non-Indian, datacenter and flagged exits. Use a residential proxy in India, the default here.
- Each minted session is pinned to one exit IP, so use sticky sessions. In custom `proxyUrls`, put `{session}` where your provider takes a session id.
- The first session is plain HTTP. If the exit is refused, a browser session is minted on a fresh exit and retried, so one bad IP does not kill the run.
- An unknown product id returns an empty page rather than an error, recorded as `reason: not_found` instead of failing the run.
- These rows carry no sponsored or ad flag. The Blinkit product page exposes no paid-placement signal.

### FAQ

**Do I need a proxy?** Yes for anything beyond a few calls. Use a residential proxy in India with sticky sessions. It is already the default.

**How many results can I get?** One row per product and pincode pair, with no cap on either list. A session serves up to 200 fetches before it re-mints.

**Does it need login or an API key?** No. No Blinkit account or key of your own is required.

**How does a pincode pick a store?** The pincode is resolved to coordinates sent with the product request, so Blinkit itself chooses the dark store. Without them the site returns a placeholder store at zero price, which is why the pincode is mandatory.

# Actor input Schema

## `productIds` (type: `array`):

Blinkit product ids (e.g. 530158) or product URLs (https://blinkit.com/prn/<slug>/prid/<id>). One row is produced per product for every pincode.

## `pincodes` (type: `array`):

Indian 6-digit pincodes, e.g. 122002. Each is resolved to coordinates and the app picks the dark store serving it; prices, stock and ETA are for that store. Unresolvable pincodes and pincodes with no store are reported per row (reason pincode\_unresolved / not\_serviceable), never silently skipped.

## `maxConcurrency` (type: `integer`):

Product fetches in flight per pincode (1–4). Sessions are rate-limited per IP; 2 is safe.

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

Pause between product fetches on one session.

## `proxyUrls` (type: `array`):

Optional: your own proxy URLs (http://user:pass@host:port). Put `{session}` where the provider takes a session id so every minted session keeps one exit IP. Overrides the proxy block below.

## `useApifyProxy` (type: `boolean`):

Apify platform only: route through Apify residential proxy (country IN). Ignored on ATR servers, where our own residential proxy is used.

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

Blinkit sits behind Cloudflare and rejects non-Indian, datacenter and flagged IPs with an "Error Page". Use Apify residential proxy, country IN. Sessions are pinned to one exit IP (put `{session}` in custom proxy URLs).

## Actor input object example

```json
{
  "productIds": [
    "530158"
  ],
  "pincodes": [
    "122002"
  ],
  "maxConcurrency": 2,
  "delayMs": 400,
  "proxyUrls": [],
  "useApifyProxy": true,
  "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 = {
    "productIds": [
        "530158"
    ],
    "pincodes": [
        "122002"
    ],
    "proxyUrls": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("ikmal_suzali_atr/blinkit-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 = {
    "productIds": ["530158"],
    "pincodes": ["122002"],
    "proxyUrls": [],
}

# Run the Actor and wait for it to finish
run = client.actor("ikmal_suzali_atr/blinkit-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 '{
  "productIds": [
    "530158"
  ],
  "pincodes": [
    "122002"
  ],
  "proxyUrls": []
}' |
apify call ikmal_suzali_atr/blinkit-details --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ikmal_suzali_atr/blinkit-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/iFVlN6yTapdiaUHJS/builds/kt74dn4YvLfzEl0TD/openapi.json