E-commerce & Quick Commerce

Blinkit Scraper API

Blinkit dark-store prices, availability and delivery ETAs - hyper-local quick-commerce intelligence.

From $15/mo · 1,000 free API calls to start · see pricing

BOOK A SCOPING CALL ALL READY APIS
scrapeguys · blinkit · sample response
{ "source": "blinkit", "query": "amul butter 500g", "pincode": "110016", "price": 285, "mrp": 305, "in_stock": true, "eta_min": 8 }
What you can extract

Structured, ready to use

  • Prices & offers
  • Dark-store availability by postcode
  • Delivery ETAs
  • Catalog & pack sizes
  • Category rankings
  • Surge & serviceability
Example schema
FieldTypeExample
sourcestring"blinkit"
querystring"amul butter 500g"
pincodestring"110016"
pricenumber285
mrpnumber305
in_stockbooleantrue
eta_minnumber8

The full schema is customized to your workflow on the scoping call.

example request · async jobs API
curl -X POST https://api.scrapeguys.com/v1/jobs \
  -H "X-API-Key: $SCRAPEGUYS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"target": "blinkit", "params": {"query": "amul butter 500g", "pincode": "400053"}}'

Illustrative request - field names and params for your deployment are fixed on the scoping call and documented in your workspace. Full request/response reference: API docs.

Platform notes

What makes Blinkit data different

The pincode is the market

Blinkit serves from dark stores, so there is no single Blinkit price or stock answer - only answers per pincode per hour. Our collection runs on a pincode panel you define, returning price, MRP, availability and delivery ETA per location, which is the only shape in which Blinkit data is actually true.

Availability decays in hours

A quick-commerce SKU can sell out and restock within a morning, so stale availability is wrong availability. Priority SKUs run intraday; the response carries the check timestamp and the dark-store context, so replenishment alerts fire on data minutes old, not yesterday's sweep.

Assortment is a zero-sum shelf

Dark stores carry a fraction of a supermarket's range, so what is listed matters as much as what it costs. The feed covers catalog presence per zone - which of your SKUs and which competitor SKUs are stocked where - the number distribution teams fight over city by city.

Blinkit-specific coverage

Dark-store catchment mapping per pincode, hourly stock snapshots, surge and express delivery-fee capture, category share-of-shelf per store, and new-SKU detection within hours of listing - fields that only make sense on Blinkit's dark-store model.

Use cases

What teams build on this

Pincode-level monitoring

Dark-store availability and delivery ETAs by pincode.

Price & promo tracking

Discounts, bundles and surge behaviour across zones.

Quick-commerce share

Catalog and ranking movement across the QC platforms.

Guides & answers: Quick commerce data Q&A · What is a web scraping API?

How it works

Scoped, built and operated for you

1

Scoping call

Fields, cadence, geography - shaped to your workflow. Docs & samples shared here.

2

We operate it

Anti-bot, proxies, parsing, monitoring - managed and SLA-backed on our side.

3

Clean JSON in

Async job API, BI feed, dashboard or MCP - one schema, your stack.

FAQ

Frequently asked questions

How many pincodes can you cover?
As many as your markets need - panels typically run from a few dozen priority pincodes to several hundred across cities. Coverage, cadence and SKU count are the three dials scoped on the call.
Can you alert on stock-outs?
Yes - availability transitions per SKU per pincode can be pushed as alerts or webhooks within the refresh cycle, which for priority SKUs is intraday.
Do you also cover Zepto and Instamart?
Yes - the three quick-commerce platforms are normalized into one schema on the same pincode panel, which is how most clients consume them.
Can you track prices at pincode or dark-store level?
Yes. Price, stock, offers and delivery promise are captured per pincode and dark store, on your cadence - the same SKU is often live in one zone and out of stock in the next, and the feed shows exactly that. Most clients run priority SKUs intraday and the long tail daily.
Do you capture the final payable price including fees?
Yes. Item price, MRP, discounts plus delivery, small-cart and surge fees where shown - the checkout total is the real comparison between quick-commerce apps, not the item price.
How fast can quick-commerce data be refreshed?
Hourly where it matters. Quick-commerce availability decays in hours, so priority SKUs are typically checked multiple times a day; full-catalog sweeps run daily.
How do I get the API documentation and a data sample?
API documentation is public at scrapeguys.com/docs - request format, response schemas, status codes and worked examples. For a sample dataset on your exact targets, book a short scoping call: each deployment is customized to your schema, fields and volumes, and most teams have a sample in hand within a day.
How fast can this go live for us?
A scoped deployment typically goes live as a production API in 48-72 hours. That includes the scraper itself, a wrapper API shaped to your workflow, custom fields added to the response, monitoring and alerting on our side, and a staging key so your team can validate the schema before production traffic starts.
How is the data delivered - do we have to integrate an API?
An API is one option, not a requirement. The same data layer ships as REST JSON APIs with async jobs and webhooks, scheduled exports into Power BI, Looker, Snowflake, BigQuery or Google Sheets, a white-label dashboard your team signs into with zero integration, or MCP tools your AI agents call live. You can mix channels - API for engineering, dashboard for the commercial team - on one deployment.
What happens when the target site changes or a scrape fails?
That is our problem, not yours. Every source is monitored around the clock - layout changes, anti-bot updates and success-rate drops page our engineers before they page you, and your field names stay stable through redesigns because we absorb the change behind the schema. Failed requests are retried automatically, and anything that still fails is not billed: pricing is success-based.

Need Blinkit data in production?

A 20-minute scoping call gets you documentation, samples and a timeline - most deployments are live in 48-72 hours.

BOOK A CALL SEND YOUR TARGETS