Zepto Product Details by Pincode avatar

Zepto Product Details by Pincode

Pricing

from $7.00 / 1,000 results

Go to Apify Store
Zepto Product Details by Pincode

Zepto Product Details by Pincode

Zepto product details for any product-variant id or URL at any Indian pincode: price, MRP, discount, pack size, available quantity, rating, seller, images, attributes, dark store id. One row per product × pincode, priced by the store serving that pincode.

Pricing

from $7.00 / 1,000 results

Rating

0.0

(0)

Developer

AtTheRate AI

AtTheRate AI

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Share

Reads the full Zepto product page for any product-variant id or URL, at any Indian pincode, one row per product and pincode. Zepto prices and stocks per dark store, so the same variant comes back at a different price and availability depending on the pincode you ask for.

What you get

  • Price economics per store: price, original_price, discount_percent, discount_amount and super_saver_price.
  • Stock depth, not just a flag: stock_quantity and max_quantity alongside in_stock and availability.
  • Pack detail: unit, pack_size, unit_of_measure and weight_grams, plus seller, seller_license and seller_address.
  • A sponsored marker: is_sponsored_listing is true when the listing carries Zepto's sponsored tag.
  • Page content: name, brand, description, highlights, specifications, images, tags and sibling packs in variants.
  • Nothing is dropped: found: false rows carry a reason of invalid_id, pincode_unresolved, not_serviceable, not_found, blocked or failed.

Input

Both productIds and pincodes are required. Every product is fetched at every pincode.

{
"productIds": [
"5f54bb83-f3e0-4d8d-89b0-6339f3312089",
"00000000-0000-0000-0000-000000000000"
],
"pincodes": ["122002", "560001"],
"maxConcurrency": 2,
"delayMs": 300,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"],
"apifyProxyCountry": "IN"
}
}
  • productIds: Zepto product-variant ids (pvid UUIDs), or product URLs of the /pn/<slug>/pvid/<uuid> form.
  • pincodes: 6-digit Indian pincodes, each with its own store binding.
  • maxConcurrency: fetches in flight per pincode, 1 to 4.
  • proxyConfiguration: residential country IN is the default and is required in practice.

Output

One row per product and pincode. The input above produced 4 rows: 2 fetched and 2 marked not found for the invented UUID.

{
"requested": "5f54bb83-f3e0-4d8d-89b0-6339f3312089",
"product_id": "5f54bb83-f3e0-4d8d-89b0-6339f3312089",
"pincode": "122002",
"location_label": "Gurgaon, Gurugram",
"found": true,
"name": "Onion",
"brand": "Unbranded",
"price": 62,
"original_price": 126,
"discount_percent": 50,
"unit": "900 g - 1 kg",
"in_stock": true,
"stock_quantity": 5,
"is_sponsored_listing": false,
"store_id": "d8c4ab04-68f0-483f-82be-8b9fb18d17ae",
"fetched_at": "2026-09-11T08:59:34.879Z"
}

Null by design: review_count, seller_rating and delivery are always null, because the Zepto product payload carries no review count and no delivery estimate. category_path is empty; use category_id and subcategory_id instead.

Use cases

  • City-by-city price comparison for a fixed variant list from price and discount_percent.
  • Serviceability mapping: run a wide pincode list and read not_serviceable rows as your coverage map.
  • Stock-depth monitoring with stock_quantity, and seller auditing through seller, seller_license and seller_address.
  • Pack-ladder and price-per-unit analysis from variants, pack_size and weight_grams.

Notes and limits

  • Zepto blocks an IP after a few automated page loads and refuses datacenter and non-Indian exits with HTTP 202 or 429. A residential Indian proxy is required and is the default.
  • Each session is pinned to one exit IP. In custom proxyUrls, put {session} where your provider takes a session id.
  • One browser mint per pincode opens the session, then every product is a single fast call. A session serves up to 150 fetches before re-minting.
  • An unknown or unlisted variant returns a page with no product widget, recorded as reason: not_found.
  • Storefront renders can time out on a bad exit. The actor retries on fresh exits three times, then reports the block.

FAQ

Do I need a proxy? Yes. Use a residential proxy in India with sticky sessions, which is the default. Runs without one get blocked within a few calls.

How many results can I get? One row per product and pincode pair, with no cap on either list. Sessions rotate every 150 fetches.

Does it need login or an API key? No Zepto account or key of your own is required.

What is the difference between not_found and not_serviceable? not_found means Zepto has no product widget for that variant at that store. not_serviceable means the store itself is closed or out of area, so nothing at that pincode could be priced.