# Zepto Catalogue by Location (`ikmal_suzali_atr/zepto-catalog`) Actor

Every Zepto product for a delivery location, category by category, with price, MRP, discount, live available quantity and out-of-stock state.

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

## Pricing

from $2.50 / 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 Catalogue by Location

Pulls the whole Zepto storefront for an Indian pincode, category by category, with price, MRP, discount, the available quantity the app reports and out-of-stock state. Zepto prices and stocks per dark store, so the same SKU differs between neighbourhoods.

### What you get

- Complete category walk: `category`, `subcategory`, their slugs and ids, plus `position` so shelf order survives.
- Price economics per product: `price`, `mrp` and `discount_percent`.
- Stock depth rather than a bare flag: `available_quantity` and `max_quantity` alongside `out_of_stock`.
- A sponsored flag: `is_ad` marks placements Zepto itself tags as sponsored.
- Store context on every row: `store_id` and `location_label`, plus `product_id`, `variant_id`, `name`, `brand`, `pack` and `image_url` for joining.
- Location honesty: a pincode Zepto does not serve is reported as a failed location with the reason, and returns zero rows instead of another city's data.

### Input

Give one or more Indian pincodes. Everything else narrows the crawl.

```json
{
  "pincodes": ["122002"],
  "categoryFilter": ["fruits"],
  "delayMs": 400,
  "maxPagesPerCategory": 0,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "IN"
  }
}
```

- `pincodes`: 6-digit Indian pincodes, for example `122002`.
- `categoryFilter`: only categories whose slug or name contains one of these strings, case-insensitive. Empty means all.
- `maxPagesPerCategory`: cap on pagination. 0 pages until Zepto reports the end.
- `delayMs`: pause between calls, 400 by default.
- `proxyConfiguration`: residential country IN is the default and is required in practice.

### Output

One row per product, per subcategory, per location. The run above returned 618 rows.

```json
{
  "location_label": "Gurgaon-DLF",
  "store_id": "d8c4ab04-68f0-483f-82be-8b9fb18d17ae",
  "category": "fruits-vegetables",
  "category_name": "Fruits & Vegetables",
  "subcategory_name": "Fresh Vegetables",
  "position": 1,
  "product_id": "d2a42dc1-1b5a-4925-9b66-28a24d2d8830",
  "name": "Onion",
  "brand": "Unbranded",
  "pack": "900 g - 1 kg",
  "price": 62,
  "mrp": 126,
  "discount_percent": 50,
  "available_quantity": 5,
  "out_of_stock": false,
  "max_quantity": 5,
  "is_ad": false,
  "fetched_at": "2026-09-11T08:59:34.879Z"
}
```

`brand` reads `Unbranded` for fresh produce, which is Zepto's own value, not a gap. `available_quantity` is capped by Zepto's per-order limit, so treat it as a floor on real depth.

### Use cases

- Per-store price and discount tracking from `price`, `mrp` and `discount_percent` across pincodes.
- Out-of-stock and low-stock monitoring from `out_of_stock` and `available_quantity`.
- Ad-slot share: count `is_ad` rows by brand within a subcategory.
- Assortment gap analysis by comparing the `product_id` set between cities.

### Notes and limits

- Zepto blocks an IP after roughly 5 automated page loads, answering with an HTTP 202 challenge. A residential Indian proxy is effectively required and is the default.
- Each minted session is pinned to one exit IP. A per-request rotating gateway kills sessions within a few calls, so use sticky sessions.
- An unserved point ends that location cleanly, for example `Zepto has no open store for 24.9,81.5 (serviceable=false)`, with zero rows and `failed_locations` incremented.
- `is_ad` comes from Zepto's own sponsored markers. Verified runs in fresh produce returned none, so ad density varies sharply by category.
- Exact coordinates can be supplied instead of pincodes through the advanced `locations` field.

### FAQ

**Do I need a proxy?** Yes, in practice. Use a residential proxy in India. It is already the default, and sessions must be sticky to one exit IP.

**How many results can I get?** A full store catalogue. One verified run returned 618 products from a single category filter.

**Does it need login or an API key?** No. No Zepto account, key or cookie of your own is needed.

**How does a pincode pick a store?** The pincode is resolved to a point and Zepto binds the session to the dark store serving it. That store's id is stamped on every row as `store_id`; if no store is open there, the location is skipped with the reason.

# Actor input Schema

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

Indian 6-digit pincodes to scrape, e.g. 122002. Each is resolved to the pincode's centre and the platform picks the store serving it. Pincodes with no store nearby are reported as failed locations, never as another city's data.

## `categoryFilter` (type: `array`):

Optional: only categories whose slug/name contains one of these strings (case-insensitive). Empty = all.

## `subcategories` (type: `array`):

Only scrape these subcategories (case-insensitive name match, or the subcategory id). Empty = all subcategories in the selected categories.

## `maxPagesPerCategory` (type: `integer`):

Safety cap on pagination per category (0 = until Zepto reports endOfPage).

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

Delay between API calls (ms).

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

REQUIRED in practice: Zepto blocks an IP after ~5 automated page loads (HTTP 202 WAF). Use Apify residential proxy, country IN. Each minted session is pinned to one proxy exit IP (Apify Proxy sessions; for custom proxy URLs put `{session}` where your provider takes a session id) — the site binds its anti-bot state to the minting IP, so a per-request rotating gateway kills sessions within a few calls.

## `locations` (type: `array`):

Optional instead of pincodes: exact coordinates, e.g. \[{"lat":28.4595,"lon":77.0266,"label":"Gurgaon DLF"}].

## Actor input object example

```json
{
  "pincodes": [
    "122002"
  ],
  "subcategories": [],
  "maxPagesPerCategory": 0,
  "delayMs": 400,
  "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 = {
    "pincodes": [
        "122002"
    ],
    "subcategories": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("ikmal_suzali_atr/zepto-catalog").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 = {
    "pincodes": ["122002"],
    "subcategories": [],
}

# Run the Actor and wait for it to finish
run = client.actor("ikmal_suzali_atr/zepto-catalog").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 '{
  "pincodes": [
    "122002"
  ],
  "subcategories": []
}' |
apify call ikmal_suzali_atr/zepto-catalog --silent --output-dataset

```

## MCP server setup

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

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/a6IRJQAnyV4TcENoe/builds/QWGIgOywSPJ2z2XJr/openapi.json