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.

{
  "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.

{
  "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.