# Zepto Product Details by Pincode (`ikmal_suzali_atr/zepto-details`) Actor

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.

- **URL**: https://apify.com/ikmal\_suzali\_atr/zepto-details.md
- **Developed by:** [AtTheRate AI](https://apify.com/ikmal_suzali_atr) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $7.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Zepto Product Details by Pincode

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.

```json
{
  "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.

```json
{
  "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.

# Actor input Schema

## `productIds` (type: `array`):

Zepto product-variant ids (pvid, a UUID such as 5f54bb83-f3e0-4d8d-89b0-6339f3312089) or product URLs (https://www.zepto.com/pn/<slug>/pvid/<uuid>). One row is produced per product for every pincode.

## `pincodes` (type: `array`):

Indian 6-digit pincodes, e.g. 122002. Each is resolved to coordinates and the app picks the dark store serving it; prices, stock and ETA are for that store. Unresolvable pincodes and pincodes with no store are reported per row (reason pincode\_unresolved / not\_serviceable), never silently skipped.

## `maxConcurrency` (type: `integer`):

Product fetches in flight per pincode (1–4). Sessions are rate-limited per IP; 2 is safe.

## `delayMs` (type: `integer`):

Pause between product fetches on one session.

## `proxyUrls` (type: `array`):

Optional: your own proxy URLs (http://user:pass@host:port). Put `{session}` where the provider takes a session id so every minted session keeps one exit IP. Overrides the proxy block below.

## `useApifyProxy` (type: `boolean`):

Apify platform only: route through Apify residential proxy (country IN). Ignored on ATR servers, where our own residential proxy is used.

## `proxyConfiguration` (type: `object`):

REQUIRED in practice: Zepto's AWS WAF blocks an IP after a few automated page loads and refuses datacenter/non-Indian exits (HTTP 202/429). Use Apify residential proxy, country IN. Sessions are pinned to one exit IP (put `{session}` in custom proxy URLs).

## Actor input object example

```json
{
  "productIds": [
    "5f54bb83-f3e0-4d8d-89b0-6339f3312089"
  ],
  "pincodes": [
    "122002"
  ],
  "maxConcurrency": 2,
  "delayMs": 300,
  "proxyUrls": [],
  "useApifyProxy": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "IN"
  }
}
```

# Actor output Schema

## `results` (type: `string`):

One row per product.

## `summary` (type: `string`):

Counts for the run: what was requested, captured, skipped and failed.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "productIds": [
        "5f54bb83-f3e0-4d8d-89b0-6339f3312089"
    ],
    "pincodes": [
        "122002"
    ],
    "proxyUrls": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("ikmal_suzali_atr/zepto-details").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "productIds": ["5f54bb83-f3e0-4d8d-89b0-6339f3312089"],
    "pincodes": ["122002"],
    "proxyUrls": [],
}

# Run the Actor and wait for it to finish
run = client.actor("ikmal_suzali_atr/zepto-details").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "productIds": [
    "5f54bb83-f3e0-4d8d-89b0-6339f3312089"
  ],
  "pincodes": [
    "122002"
  ],
  "proxyUrls": []
}' |
apify call ikmal_suzali_atr/zepto-details --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ikmal_suzali_atr/zepto-details"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/td53E9sTpCs38odca/builds/mc5GC4EtddYhFNGds/openapi.json