Blinkit scraper alternative: pin-code data without a scraper

The short answer

Yes. You can get Blinkit prices, MRP and stock by pin code without building a scraper. Rewalto reads Blinkit every day and sells the records, each with its pin code and the time it was read, through a dashboard, an API and an MCP server (preview). You pay credits only for records delivered. The live coverage is below.

What Rewalto holds for Blinkit today

These figures are read from the Rewalto data catalogue and the dark-store map, not typed into this page. If the catalogue cannot be read, the block says so instead of showing an old number.

The current pin codes, refresh and rate for Blinkit are read from the Rewalto data catalogue each time this page is served. The commerce data page lists them too.

Why teams build a Blinkit scraper in the first place

Most teams that start a Blinkit scraper want one of a few answers. A brand wants to know whether its products are listed and in stock in the cities it sells in. A category manager wants to see what a rival is charging this week. An analyst wants a price series to set beside a promotion. A developer building an AI agent wants a reliable way to answer “what does this cost on Blinkit near me”. None of these needs a scraper as such. Each needs dated records of what the app showed, at a known place.

Blinkit makes that harder than a normal online shop because the shelf depends on location. The same search returns different products, prices and stock states depending on which dark store serves the pin code. A reading with no pin code attached is not wrong, exactly, but it cannot be checked, and it cannot be compared with tomorrow’s reading from a different place. That is the part of the job that takes the most care, and it is the part a dataset can do once for everyone.

The work a scraper keeps asking for

Writing the first version of a scraper is the small part. The larger part is everything that comes after it, and it does not stop. We do not describe how to collect from Blinkit here; this is the list of jobs that remain once something is collecting.

• Choosing pin codes that represent your market, and keeping that list current as the app opens dark stores in new areas.
• Noticing when the app changes its pages, before a week of silently empty or wrong rows reaches a report.
• Telling a product that is out of stock apart from one that was simply not read, so a gap is never counted as a stockout.
• Matching the same product across days when its title, pack or image changes.
• Storing every reading with its time and place, so a number can be traced back when someone questions it.
• Keeping the collection within the terms of use of the sites it reads, and deciding who in your company owns that question.

Each of these is a standing task with an owner, not a one-off. A dataset moves them to the supplier. Your team keeps the part that is actually yours: deciding what the numbers mean for your products and what to do about them.

What a Blinkit record from Rewalto holds

Each price record is one product, at one pin code, at one moment: the selling price shown, the MRP, the discount between them, and whether the product could be added to a basket. The record names the pin code and the time of the reading. A product that was not read is absent rather than marked out of stock, so you never mistake a gap in reading for a gap on the shelf.

The same readings feed other Blinkit datasets you may want beside prices: search results for the words shoppers type, with sponsored places marked; each brand’s share of the shelf at a pin code; units left and units gone, a lower bound on sales; and the dark stores Blinkit runs, with the pin codes each one serves. Each has its own entry in the commerce data catalogue with its status, coverage and rate.

Held pin codes and fresh reads

There are two ways to get Blinkit data. The first is the held set: pin codes Rewalto reads every day, whose history you can read back from the day each began. This suits trend questions, such as how a price moved through a festive week, because every day was read the same way at the same places.

The second is a fresh read at a pin code that is not in the held set. For Blinkit the catalogue lists this as available at any pin code. A fresh read answers a question about now at a place you choose; it does not create history for the days before it. The rate for a fresh read is shown before it runs, and nothing is charged for a read that returns no records.

If the place you care about is not held and you need its history from now on, ask for it through the catalogue. Adding a pin code is a request with a reply, not a promise made on this page.

A worked example: a launch check across five cities

Say a snacks brand launched a new flavour on Blinkit last week and wants to know where it is actually buyable. With a scraper, the team would first decide which addresses stand for each city, then run the collection every day, then work out which rows mean “out of stock” and which mean “not found”. Each step is a decision someone has to make and defend.

With the dataset, the question is narrower and faster. Pick the five cities, look up which held pin codes fall in them, and read the brand’s price and stock records for those pin codes over the last seven days. Every row already says where and when it was read. A pin code where the product never appeared is a listing gap; a pin code where it appeared but could not be bought is a stock gap. Those are different conversations with a distributor, and the data keeps them apart.

If one city matters most and none of its pin codes is held, run a fresh read there for today, and ask for that pin code to be added so next week’s check has history behind it. The cost of each step is shown before it runs.

Five questions to settle before you choose

• Which decision will the data support, and who will read the result?
• Which cities and pin codes does that decision depend on, and are they in the held list?
• Do you need history, or only an answer about today?
• Which fields do you need: price, MRP, stock, search position, brand share or dark stores?
• How often must the answer be refreshed, and is once a day enough?

Answer these first and the choice between a dataset and your own collection usually makes itself.

How to get the data: dashboard, API, agent

Teams without developers read the data in the dashboard: choose Blinkit, the pin codes and the days, see the cost, and download the records. Developers call the Rewalto API with a key; the data API documentation lists every operation, its filters and the shape of a record. The command line and MCP server (preview) give the same records to a script or to an AI agent.

Whichever route you use, the rate is shown before a read runs, reading the same records again within seven days is free, and an empty answer costs nothing. That makes it safe to try a narrow question first, one brand at a handful of pin codes, before you commit to a wider pull.

When your own scraper is still the right call

A dataset is not always the answer. If you need a field Rewalto does not read, such as a detail that only appears on a product page Rewalto does not open, or an app Rewalto does not cover, your own collection may be the only way. The same is true if you need readings more often than daily at a fixed set of places, or if your contract requires that only your own systems touch the source.

Check the catalogue first. If the field, the pin codes and the refresh you need are listed, the dataset will usually be cheaper than the engineering time a scraper takes to keep healthy. If they are not, tell us what is missing; it helps decide what is read next, and you get a written answer rather than a guess.

What this data does not tell you

The records describe what Blinkit showed at the pin codes and times read. They are not Blinkit’s own figures, they are not sales, and they do not cover pin codes that were not read. A price is the one shown on the listing, before coupons, bank offers, membership prices and delivery fees. Rewalto has no relationship with Blinkit.

Read the guide to coverage and freshness before you build on any dataset, this one included, and keep the pin code and time beside every number you show to someone else.

Questions