The price, MRP, stock and delivery time of any Blinkit product at any Indian address
Blinkit serves every delivery location from one dark store, so its catalogue, prices and stock change from one neighbourhood to the next.
3 active endpoints, on 2 and 3 credit tiers.
- POST/blinkit/v1/search
- POST/blinkit/v1/product
- POST/blinkit/v1/store
What Blinkit endpoints does ReefAPI ship?
3 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Blinkit API
4 of 3 endpoints, ready to run
Atta prices in Mumbai
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
How the Blinkit API works
Blinkit is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 549 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
From an address to a priced quick-commerce basket
Check that Blinkit delivers, search with that location, then read the product pages that matter.
Where the PIN code resolves, whether Blinkit delivers there, the promised minutes and the dark stores serving it.
Products with price, MRP, discount, pack sizes, stock count, store id, delivery minutes and a sponsored flag, plus Blinkit's own total.
The product page at that store: price, stock, every pack size, description, nutrition, shelf life, FSSAI licence and manufacturer.
A location-specific quick-commerce price, stock and delivery-time feed with pack sizes and product facts.
curl -X POST https://api.reefapi.com/blinkit/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"atta","pincode":"400020"}'{
"ok": true,
"data": { … },
"meta": {
"api": "blinkit",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What a Blinkit field actually contains
Fields that read differently from how they look. Every row was measured against live Blinkit responses on 2026-10-15.
| Field | What it holds |
|---|---|
| location | The PIN code or point the answer is for, with the address and postal code Blinkit resolved it to. There is no location-free shelf: Blinkit refuses a search without one. "atta" matched 140 products near Dadar in Mumbai, 137 in central Delhi and 116 in central Bengaluru, and the same 5 kg pack (product 344107) cost 272 rupees in Mumbai against 313 in Bengaluru. |
| merchant_id | The dark store that serves the location. Three cities, three different stores; two PIN codes inside Mumbai were served by two different stores (55 and 140 "atta" products). |
| price, mrp, discount_percent, discount_text | Selling price and maximum retail price in rupees as Blinkit's cart uses them; discount_percent is computed from the two and discount_text is Blinkit's own label, for example "19% OFF". price_text and mrp_text keep the printed figures, and price_text_matches says whether they agree with the numbers. |
| inventory, in_stock | The stock count Blinkit's cart allows at that store (for example 3, 10 or 35 units) and whether the product can be ordered now. |
| available_at_store | false when the store serving the location does not sell the product at all. Blinkit then answers with price 0; the API returns no price instead of a price of zero. |
| search_method, exact_match_count, similar_result | When Blinkit runs out of direct matches it switches to "similarity" and appends related items: "eggs" in Kolkata had 9 direct matches, and rows 10 to 12 were bread. Those rows carry similar_result: true; total counts every item Blinkit will page through (267 there). |
| eta_minutes | Blinkit's delivery promise for that store and service, for example 8 minutes in Mumbai and 9 in Delhi. |
| sponsored | true for paid placements, marked by Blinkit's ad badge: 15 of 60 rows in our first sample. |
Once the location is fixed the answer is the same for every caller: repeated reads of one point in the same minute returned byte-identical results.
Blinkit coverage, measured
Every number below was read from live Blinkit responses on 2026-10-15, across 12 searches in 6 cities, 12 product pages and the location checks.
Mumbai, Delhi, Bengaluru, Gurugram, Kolkata and Hyderabad all served; Agartala and Srinagar answered as not served.
"atta": 140 products near Dadar (Mumbai), 55 at PIN code 400020 (another Mumbai store), 137 in central Delhi, 116 in central Bengaluru. Product 344107: 272 rupees in Mumbai, 313 in Bengaluru.
Search row and product page agreed on price, MRP, stock count, pack size and store for every product read twice in the same run (see BUILD-LOG for the counts).
When direct matches run out Blinkit appends related items ("eggs" in Kolkata: 9 direct matches, then bread); each such row is flagged.
One location per call; about 12 rows per page, up to 5 pages; no filters or sort orders yet; no review text; no member-only prices.
What people build with Blinkit
The jobs this data is most often used for.
endpoints
credits per call
Compare quick-commerce prices and discounts across Indian neighbourhoods and cities.
Track live stock counts of a product at the dark store serving an address.
Monitor delivery promises in minutes for a list of PIN codes or coordinates.
Watch sponsored placements for a search term by location.
What Blinkit data costs
The cheapest call here is 2 credits, so $15/mo (Pro) buys 5,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 549 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/blinkit/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"atta","pincode":"400020"}'import requests
r = requests.post(
"https://api.reefapi.com/blinkit/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "atta",
"pincode": "400020"
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Blinkit.
Get a free key →Do I need a Blinkit account?▾
No. Everything is read logged out: prices, stock and delivery times are the ones Blinkit shows any visitor who sets that location.
Why is a location required?▾
Because every Blinkit location is served by one dark store with its own range, prices and stock. Blinkit itself refuses a search without a location, and the API never substitutes one: you pass a 6-digit PIN code or a latitude and longitude, and the answer echoes the address and postal code it resolved.
PIN code or latitude and longitude?▾
A PIN code is resolved to the place Blinkit's own location search gives for it, and is accepted only when that place's postal code is the PIN code you sent. A PIN code covers a whole area, while one point picks one store; use lat and lon to read the store of a specific address.
What happens where Blinkit does not deliver?▾
The answer says serviceable: false with no rows and a note. Agartala (799001) and Srinagar (190001) were not served when we measured.
How many products per page?▾
About 12 per page; Blinkit decides, and some pages carry a few more. Pages follow Blinkit's own next-page link. Up to 5 pages per search. After the direct matches Blinkit appends similar items and can repeat a product from an earlier page; both are flagged on the row.
What if a product is not sold near me?▾
The product call still answers, with available_at_store: false and no price. Blinkit itself shows such a product with a price of zero.
Are filters and sort orders supported?▾
Not yet. The API returns Blinkit's default order for the search term; filter by brand, price or stock on your side using the returned fields.
How fresh is the data?▾
Every call reads Blinkit live; nothing is cached. Stock counts move during the day.
What is the Blinkit API?▾
Blinkit API is a ReefAPI endpoint group for dark-store prices, mrp, discounts, live stock and delivery minutes from blinkit for any indian pin code or gps point. It returns live JSON through POST requests under /blinkit/v1.
Is the Blinkit API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Blinkit calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Blinkit login or account?▾
No login to Blinkit is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Blinkit data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Blinkit API use?▾
Blinkit actions currently cost 2-3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Blinkit from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call blinkit actions with the same key, credit pool and JSON envelope used by normal REST requests.
284 E-commerce & Marketplaces APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Blinkit, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 548 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-10-15.