Blinkit Search Scraper

Search Blinkit by keyword and export product listings—prices, MRP, stock, ratings, and images—for any delivery address in India. Use it for price monitoring, assortment checks, and market research across cities.

Prices and availability depend on where you order from. Set latitude and longitude to match the delivery pin you care about (e.g. Bangalore vs Delhi).

Input

Field	Type	Required	Default	Description
queries	array	Yes	—	Search terms, one per line (e.g. milk, amul butter, bread).
latitude	number	Yes	28.6139	Delivery location latitude (decimal degrees).
longitude	number	Yes	77.209	Delivery location longitude (decimal degrees).
maxItems	integer	No	50	Maximum total products saved across all queries.
maxItemsPerQuery	integer	No	50	Maximum products per search term (also limited by maxItems).
proxyConfiguration	object	No	Residential proxy on	Apify residential proxy (recommended on Apify cloud).

Output

Results are saved to the run dataset—one JSON object per product (including separate rows for size/variant options when Blinkit lists them).

Each item includes:

Field	Description
searchQuery	Keyword that found this product
rank	Position in results for that query (1 = first)
name, brand, quantity	Product title, brand, pack size
price, mrp, currency	Selling price and MRP in INR
inStock, inventory	Availability
rating, ratingCount	Customer rating when shown
discountText	Offer label on the card, if any
imageUrl, images	Product image(s)
productUrl	Link to the product on Blinkit
productId, variantId	Blinkit identifiers
latitude, longitude	Location used for this run
scrapedAt	When the row was collected (ISO time)

Download as JSON, CSV, or Excel from the dataset tab, or connect via API / integrations (Google Sheets, webhooks, etc.).

Pricing Structure

Pay per usage — you are charged for Apify compute (runtime, memory) for each run. Proxy traffic for reliable access to Blinkit is included in the actor setup; factor run time and dataset size into your estimates.

Examples

Example 1: Single product search in Delhi

Input:

{
  "queries": ["milk"],
  "latitude": 28.6139,
  "longitude": 77.209,
  "maxItems": 20
}

Output (sample row):

{
  "searchQuery": "milk",
  "rank": 1,
  "name": "Amul Taaza Toned Milk",
  "brand": "Amul",
  "quantity": "500 ml",
  "price": 30,
  "mrp": 30,
  "currency": "INR",
  "inStock": true,
  "rating": 4.6,
  "productUrl": "https://blinkit.com/prn/amul-taaza-toned-milk/prid/19512",
  "latitude": 28.6139,
  "longitude": 77.209,
  "scrapedAt": "2026-05-26T19:30:35.969Z"
}

Example 2: Multiple keywords in Bangalore

Input:

{
  "queries": ["milk", "bread", "eggs"],
  "latitude": 12.9716,
  "longitude": 77.5946,
  "maxItems": 60,
  "maxItemsPerQuery": 25
}

Output: Up to 25 products per query, stopping at 60 total. Each row has searchQuery set to the matching keyword.

Example 3: Tight limit for a quick price check

Input:

{
  "queries": ["dairy milk chocolate"],
  "latitude": 19.076,
  "longitude": 72.8777,
  "maxItems": 10,
  "maxItemsPerQuery": 10
}

Output: Up to 10 products for that search at the Mumbai-area coordinates you provided.

Best Practices

1. Use accurate coordinates — In Google Maps, right-click the delivery point and copy latitude/longitude. Wrong coordinates show prices for a different area.
2. Start small — Run one query with maxItems of 10–20 to check results and cost before scaling up.
3. Split large lists — For many keywords, run in batches or lower maxItemsPerQuery so each run stays within your budget.
4. Same location, comparable data — Keep latitude/longitude fixed when comparing prices over time for one city or store zone.
5. Category browsing — To scrape category shelves instead of search, use the Blinkit Category Scraper actor.