# Blinkit Catalogue by Location (`ikmal_suzali_atr/blinkit-catalog`) Actor

Every Blinkit product for a delivery location: category → subcategory → products with price, MRP, discount, live inventory count and sold-out state. Give it lat/lon (or pincode centroids) and get the whole store.

- **URL**: https://apify.com/ikmal\_suzali\_atr/blinkit-catalog.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 $2.50 / 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 Catalogue by Location

Pulls the whole Blinkit storefront as a shopper at an Indian pincode sees it: every category, every subcategory, every product, with price, MRP, discount and the live inventory count the app shows. Blinkit runs on dark stores, so assortment and price differ street by street. Give it pincodes and get one complete catalogue per store.

### What you get

- Full tree walk: `category`, `subcategory` and their ids, with `page` and `position` so shelf order survives.
- Real price economics per product: `price`, `mrp`, `discount_percent` and the promotional `offer` text.
- Live stock depth, not just a boolean: `inventory` is the unit count Blinkit reports, alongside `is_sold_out` and `product_state`.
- Store context on every row: `merchant` (the dark store name), `merchant_id` and `locality`.
- Location honesty: a pincode with no store nearby is reported as a failed location and produces zero rows, never another city's catalogue relabelled.

### Input

Give one or more Indian pincodes. Everything else narrows the crawl.

```json
{
  "pincodes": ["122002"],
  "categoryFilter": ["milk"],
  "maxSubcategoriesPerLocation": 1,
  "delayMs": 2200,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "IN"
  },
  "chainId": 1383
}
```

- `pincodes`: 6-digit Indian pincodes, for example `122002`.
- `categoryFilter`: only top-level categories whose name contains one of these strings, case-insensitive. Empty means all.
- `maxSubcategoriesPerLocation`: 0 means all. A Blinkit store carries around 350 subcategories.
- `proxyConfiguration`: off by default. Residential country IN is recommended for more than one location per run.

### Output

One row per product, per subcategory, per location. The run above returned 30 rows from a single subcategory.

```json
{
  "location_label": "Gurgaon-DLF",
  "merchant": "Super Store Gurgaon Sector 12 ES174",
  "merchant_id": "43483",
  "category": "Dairy & Breakfast",
  "subcategory": "Milk",
  "position": 1,
  "product_id": "12872",
  "name": "Amul Gold Full Cream Milk",
  "brand": null,
  "variant": "500 ml",
  "price": 36,
  "mrp": 36,
  "discount_percent": 0,
  "inventory": 12,
  "is_sold_out": false,
  "product_state": "available",
  "offer": null,
  "fetched_at": "2026-09-11T09:20:40.690Z"
}
```

`brand` is often null: Blinkit publishes no separate brand field on listing tiles, so the brand sits inside `name`. `offer` is null when no promotion is running.

### Use cases

- Track price and discount per dark store using `price`, `mrp` and `discount_percent` across many pincodes.
- Measure real availability with `inventory` and `is_sold_out`, spotting stores running thin before they hit zero.
- Map assortment gaps: compare the `product_id` set for your category across cities.
- Promotion and shelf tracking from `offer`, `page`, `position` and `variant`.

### Notes and limits

- Blinkit rate-limits per IP. Around 6 requests per second triggers 429 within 30 calls, while one call every 2 to 3 seconds ran 100 or more calls with no 429. That is why `delayMs` defaults to 2200. Lower it only behind a rotating residential proxy.
- Blinkit sits behind Cloudflare and residential Indian IPs work. Each session is pinned to one exit IP, so a per-request rotating gateway breaks sessions within a few calls.
- A store with an empty category tree is reported with a warning and zero rows, for example a rural point that is served but stocks nothing.
- An unresolvable pincode ends the run with a clear message rather than scraping a default location.
- These rows carry no sponsored or ad flag. Blinkit's listing payload does not mark paid placements.
- Exact coordinates can be supplied instead of pincodes through the advanced `locations` field.

### FAQ

**Do I need a proxy?** For a single location, no. For more than one location per run, use a residential proxy in India.

**How many results can I get?** A whole store, roughly 350 subcategories, paged in full. Cap it with `maxSubcategoriesPerLocation` or `categoryFilter`.

**Does it need login or an API key?** No. No Blinkit account or key is involved.

**How does a pincode pick a store?** The pincode is resolved to a point and Blinkit itself chooses the dark store serving it. That store is stamped on every row as `merchant` and `merchant_id`, so you always know which catalogue you are reading.

# Actor input Schema

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

Indian 6-digit pincodes to scrape, e.g. 122002. Each is resolved to the pincode's centre and the platform picks the store serving it. Pincodes with no store nearby are reported as failed locations, never as another city's data.

## `categoryFilter` (type: `array`):

Optional: only scrape top-level categories whose name contains one of these strings (case-insensitive), e.g. `["Munchies", "Cold Drinks"]`. Empty = all categories.

## `subcategories` (type: `array`):

Only scrape these subcategories (case-insensitive name match, or the subcategory id). Empty = all subcategories in the selected categories.

## `maxSubcategoriesPerLocation` (type: `integer`):

0 = all (a Blinkit store has ~350 subcategories).

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

Blinkit rate-limits per IP: ~6 requests/s triggers 429 within 30 calls, while one call every 2–3 s ran 100+ calls with zero 429s. Lower this only when using a rotating residential proxy.

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

Blinkit is behind Cloudflare; residential IPs work. Apify residential proxy (country IN) recommended for more than one location per run. Each minted session is pinned to one proxy exit IP (Apify Proxy sessions; for custom proxy URLs put `{session}` where your provider takes a session id) — the site binds its anti-bot state to the minting IP, so a per-request rotating gateway kills sessions within a few calls.

## `chainId` (type: `integer`):

Merchant chain used for the category tree (1383 = Blinkit).

## `locations` (type: `array`):

Optional instead of pincodes: exact coordinates, e.g. \[{"lat":28.4595,"lon":77.0266,"label":"Gurgaon DLF"}].

## Actor input object example

```json
{
  "pincodes": [
    "122002"
  ],
  "subcategories": [],
  "maxSubcategoriesPerLocation": 0,
  "delayMs": 2200,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "chainId": 1383
}
```

# 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 = {
    "pincodes": [
        "122002"
    ],
    "subcategories": []
};

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

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

```

## MCP server setup

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

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/ZUm7zdMwhdyKYx5Av/builds/X4odAAitGYrsWiUax/openapi.json