# Namshi Catalogue by Category (`ikmal_suzali_atr/namshi-catalog`) Actor

Every product on a Namshi category listing (UAE (English), UAE (Arabic), Saudi Arabia (English), Saudi Arabia (Arabic)): id, name, brand, price, original price, rating, seller and sponsored flag, page by page, optionally with subcategories. Dual-mode: the same code runs as an ATR BullMQ worker.

- **URL**: https://apify.com/ikmal\_suzali\_atr/namshi-catalog.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 $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

## Namshi Catalogue by Category

Pulls every product on a Namshi category listing for the UAE and Saudi Arabia, in English or Arabic, one row per product with price, discount, stock label, badges and a sponsored flag. Built for fashion brands and marketplace teams who need the full shelf of a category, in shelf order, on a schedule.

### What you get

- Complete coverage page by page, with `category`, `category_title`, `page` and `position` on every row.
- Real pricing: `price` is the live selling price, `original_price` the pre-discount price, and `discount_percent` the site's own figure.
- `is_sponsored` on every row, from the product's placement source. `source` carries the raw value, so an ads placement is distinguishable from an organic one.
- Merchandising signals shoppers see: `badges`, `tags` such as "Selling out fast", `is_outlet`, `is_rocket` for express delivery and `stock_label` for low stock.
- Ratings where Namshi publishes them, as `rating` and `rating_count`, plus `image_url` and `product_url`.
- Both the parent style and the specific offer: `id` is the parent SKU, `sku` the offer-level SKU.

### Input

Give it category paths or full Namshi URLs plus a storefront.

```json
{
  "categories": ["/women-shoes/"],
  "locale": "uae-en",
  "maxPages": 1,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "AE"
  },
  "expandSubcategories": false,
  "delayMs": 1200,
  "callsPerSession": 60
}
```

- `categories` (required): paths such as `/women-shoes/` or URLs such as `https://www.namshi.com/uae-en/men-clothing/`. Every path is listed in the sitemap at `https://www.namshi.com/sitemap-index.xml`.
- `locale`: `uae-en`, `uae-ar`, `saudi-en` or `saudi-ar`. Default `uae-en`.
- `maxPages`: pages per category. `0` means every page.
- `proxyConfiguration`: residential in the storefront's country, AE for UAE and SA for Saudi. AE is the default.

### Output

One dataset row per product.

```json
{
  "platform": "namshi",
  "locale": "uae-en",
  "category": "/women-shoes/",
  "category_title": "Women's  Shoes",
  "page": 1,
  "position": 1,
  "id": "ZA7EB15693D36DF80F7D2Z",
  "sku": "ZA7EB15693D36DF80F7D2Z-1",
  "name": "Keds Women's BlissWalk Athletic Loafer",
  "brand": "Keds",
  "price": 109,
  "original_price": 299,
  "currency": "AED",
  "discount_percent": 64,
  "in_stock": true,
  "is_sponsored": true,
  "source": "ads",
  "stock_label": "Low Stock",
  "is_outlet": true,
  "product_url": "https://www.namshi.com/uae-en/buy-keds-women-s-blisswalk-loafer",
  "fetched_at": "2026-09-12T02:59:18.273Z"
}
```

Namshi does not show reviews on every card, so `rating` and `rating_count` are null for a large share of products. `breadcrumbs` and `seller` are null on this site. Currency is AED on the UAE locales and SAR on the Saudi ones.

### Use cases

- Discount depth tracking across a category from `price`, `original_price` and `discount_percent`.
- Assortment and newness: diff `id` sets between runs to see what was added or dropped.
- Ad placement share in a category, from `is_sponsored` and `source`, with `position` showing where paid slots sit.
- Stock pressure monitoring with `stock_label` and `in_stock`, to catch styles running out.
- Outlet versus full-price mix per brand, from `is_outlet` and `brand`.

### Notes and limits

- A verified run on `/women-shoes/` at `uae-en` returned 83 products from one page, and two categories at two pages each returned 338. Expect about 83 products per page.
- Sponsored placement is common here. The single-page verified run reported 26 sponsored products out of 83.
- Sponsored slots only appear on a session-backed request, so the proxy country changes what is shown, not just whether the run succeeds.
- Only category paths are accepted. A `/search/` path is rejected and counted in `failed_categories`.
- Arabic locales return Arabic names in the same fields. Nothing else changes.

### FAQ

**Do I need a proxy?** Yes. Residential in the storefront's country, AE for the UAE locales and SA for the Saudi ones. AE is the input default.

**How many results can I get?** `maxPages: 0` walks the whole category at about 83 products per page.

**Does it need a login or an API key?** No. No Namshi account and no API key.

**How is sponsored detected?** From the placement source Namshi attaches to each product. A `source` of `ads`, `commercial` or `ramp_control` sets `is_sponsored: true`, and the raw value stays on the row.

# Actor input Schema

## `categories` (type: `array`):

Namshi category paths or URLs, e.g. "/women-shoes/" or "https://www.namshi.com/uae-en/men-clothing/". The category sitemap at https://www.namshi.com/sitemap-index.xml lists every path.

## `locale` (type: `string`):

Which storefront / locale.

## `maxPages` (type: `integer`):

0 = all pages.

## `expandSubcategories` (type: `boolean`):

Also crawl each category's subcategories when the site exposes them.

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

Pause between page fetches.

## `callsPerSession` (type: `integer`):

Re-mint the session after this many page fetches.

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

On the Apify platform this decides egress. A residential proxy in the storefront's country is recommended (AE for the default). On our own servers it is ignored and our residential proxy is used.

## Actor input object example

```json
{
  "categories": [
    "/women-shoes/"
  ],
  "locale": "uae-en",
  "maxPages": 0,
  "expandSubcategories": false,
  "delayMs": 1200,
  "callsPerSession": 60,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "AE"
  }
}
```

# 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 = {
    "categories": [
        "/women-shoes/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ikmal_suzali_atr/namshi-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 = { "categories": ["/women-shoes/"] }

# Run the Actor and wait for it to finish
run = client.actor("ikmal_suzali_atr/namshi-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 '{
  "categories": [
    "/women-shoes/"
  ]
}' |
apify call ikmal_suzali_atr/namshi-catalog --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ikmal_suzali_atr/namshi-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/5XEvrI4aute7UvOhS/builds/h0NayVlDGU5U0TnGM/openapi.json