The price, MRP and stock of any Zepto product at any Indian address
Zepto serves every delivery location from one dark store, so its range, prices and stock change from one neighbourhood to the next.
3 active endpoints, on 2 and 3 credit tiers.
- POST/zepto/v1/search
- POST/zepto/v1/product
- POST/zepto/v1/store
What Zepto endpoints does ReefAPI ship?
3 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Zepto 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 Zepto API works
Zepto 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 Zepto delivers, search with that location, then read the products that matter.
Where the PIN code resolves, whether Zepto delivers there, the dark stores serving it and whether they are open now.
Products with price, MRP, discount, pack size, live stock, order limit, store id and a sponsored flag, plus Zepto's own total.
That product at the same store: carried or not, price, order limit, description, manufacturer, FSSAI licence, shelf life and images.
A location-specific quick-commerce price and stock feed with pack sizes and product facts.
curl -X POST https://api.reefapi.com/zepto/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"atta","pincode":"400020"}'{
"ok": true,
"data": { … },
"meta": {
"api": "zepto",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What a Zepto field actually contains
Fields that read differently from how they look. Every row was measured against live Zepto 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 Zepto's place search resolved it to. There is no location-free shelf; the API never picks one for you. "atta" counted 246 products near Dadar in Mumbai, 260 in central Delhi and 261 in central Bengaluru. |
| store_id, stores | The dark store that serves the location (and a secondary store where Zepto has one). The same 1 kg Aashirvaad atta cost 63 rupees (MRP 68) at the Mumbai store and 65 rupees (MRP 75) at the Bengaluru store; 8 of 8 products sold in both had a different price or stock. |
| price, mrp, discount_percent, discount_amount | Selling price and maximum retail price in rupees (Zepto sends paise; the API converts). discount_percent is Zepto's own figure, which rounds down: 86 to 69 rupees is printed as 19 percent. |
| inventory, orderable_quantity, max_order_quantity | inventory is the live stock count at that store. orderable_quantity is what one order can take, which is the stock count capped by Zepto's per-order limit (19 in stock, limit 12, orderable 12). |
| available_at_store | false when the store serving the location does not carry the product. Zepto then answers from another store; the API returns no price for your location and names that other store in fallback_store_id. |
| sponsored, repeated_in_results | true for paid placements. Zepto can show the same product twice on a page, once sponsored and once in its normal place; the second copy is flagged. A sponsored product's normal place can also be on the next page. |
| status, eta_minutes | From the store call: whether the store is delivering right now (for example CLOSED with the reason) and the promised minutes when it is open, with the store's opening and closing time. |
Once the location is fixed the answer is the same for every caller: the same Mumbai store read twice in the same minute returned identical prices and stock.
Zepto coverage, measured
Every number below was read from live Zepto responses on 2026-10-15, across 12 searches in 6 cities, 14 products read at their store, and the location checks.
Mumbai, Delhi, Bengaluru, Gurugram, Kolkata and Hyderabad all served; a desert point in Rajasthan and a point at sea answered as not served.
"atta": 246 products near Dadar (Mumbai), 240 at PIN code 400020 (another Mumbai store), 260 in central Delhi, 261 in central Bengaluru. 1 kg Aashirvaad atta: 63 rupees in Mumbai, 65 in Bengaluru.
Search row and product call agreed on price, MRP, discount, order limit, pack size, store and brand for 14 of 14 products read both ways.
Up to half of a first page can be sponsored (15 of 30 for "atta"); every such row is flagged, and duplicate copies are marked.
One location per call; 18-30 rows per page, up to 10 pages; no filters or sort orders yet; no review text; no member-only prices.
What people build with Zepto
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.
Check whether Zepto is delivering to a list of PIN codes or coordinates right now.
Watch sponsored placements for a search term by location.
What Zepto 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/zepto/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/zepto/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 Zepto.
Get a free key →Do I need a Zepto account?▾
No. Everything is read logged out: the prices and stock are the ones Zepto shows any visitor who sets that location.
Why is a location required?▾
Because every Zepto location is served by one dark store with its own range, prices and stock. The API never substitutes a default location: 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 through Zepto's own place search and accepted only when the place found is that postal code. A PIN code stands for one point of the area, while lat and lon pick the store of a specific address.
What happens where Zepto does not deliver?▾
The answer says serviceable: false with no rows and a note.
How many products per page?▾
Zepto decides: 18 to 30 per page in our measurements. Up to 10 pages per search; past the last page the answer is an empty page with a note.
What if a product is not carried near me?▾
The product call still answers, with available_at_store: false and no price, because the price Zepto shows then belongs to another store.
Are filters and sort orders supported?▾
Not yet. The API returns Zepto'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 Zepto live; nothing is cached. Stock counts and store status move during the day.
What is the Zepto API?▾
Zepto API is a ReefAPI endpoint group for dark-store prices, mrp, discounts and live stock from zepto for any indian pin code or gps point. It returns live JSON through POST requests under /zepto/v1.
Is the Zepto API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Zepto calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Zepto login or account?▾
No login to Zepto 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 Zepto 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 Zepto API use?▾
Zepto 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 Zepto from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call zepto 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 Zepto, 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.