# Namshi Fashion Catalog Scraper (`coolinbex/namshi-fashion-scraper`) Actor

Extract public Namshi fashion products, brands, prices, discounts, sizes, colors, availability, ratings, images, SKUs, breadcrumbs, and pagination results.

- **URL**: https://apify.com/coolinbex/namshi-fashion-scraper.md
- **Developed by:** [coolinbex](https://apify.com/coolinbex) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.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

## Namshi Fashion Catalog Scraper

Extract public Namshi catalog and product-page data for fashion discovery, assortment analysis, price research, and marketplace benchmarking. The Actor does not log in, call private APIs, bypass CAPTCHAs, or bypass access controls.

### What it extracts

Product URL, SKU, title, brand, gender/category when publicly exposed, breadcrumbs, sizes, colors, current/original price, discount percentage, currency, availability, rating, review count, images, and description. Listing pages are followed with bounded pagination and product URLs are deduplicated.

### Input

Provide `startUrls` with public `namshi.com` listing/search/category/product URLs. `maxProducts` (1–500), `maxPages` (1–20), low `maxConcurrency` (1–3), optional price/currency/title filters, and optional authorized Apify proxy settings are supported. Example:

```json
{"startUrls":[{"url":"https://www.namshi.com/uae-en/women/"}],"maxProducts":50,"maxPages":2,"includeImages":true}
```

### Output and limits

One dataset record is emitted per product that passes filters. `status` is `ok` for complete-looking records, `partial` when public markup omits key fields, `blocked` when a page is unavailable/challenged, and `error` for an extraction failure. A `SUMMARY` key-value record reports counts and run status. A blocked-only run completes successfully with `status: "blocked"` and an explicit dataset record; genuine request or runtime failures still make the run fail.

Markup, regional availability, currency, consent screens, and anti-automation responses can change. Use conservative schedules, respect Namshi terms and robots guidance, and verify lawful use. Runtime is primarily network/browser time: a small 50-product run normally uses several minutes and browser compute; exact cost depends on Apify compute-unit pricing, proxy usage, page count, and retries. For customer pricing, use pass-through Apify compute/proxy cost plus a service margin (for example, $5–$15 per 1,000 products for standard runs, excluding proxy charges), with a minimum run fee for very small jobs.

### Local quality gate

```text
npm install
npm test
npm run build
npm start
```

The default local smoke run requires a public network and may be blocked by Namshi; blocked pages are reported explicitly and are not treated as products.

# Actor input Schema

## `startUrls` (type: `array`):

Public Namshi listing, search, category, or product URLs.

## `maxProducts` (type: `integer`):

Maximum unique products to write.

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

Bounded pagination depth.

## `includeDescription` (type: `boolean`):

Include the public product description when available.

## `includeImages` (type: `boolean`):

Include up to 30 public product image URLs.

## `minPrice` (type: `number`):

Keep products at or above this price.

## `maxPrice` (type: `number`):

Keep products at or below this price.

## `currency` (type: `string`):

Optional marketplace currency filter.

## `includeKeywords` (type: `array`):

Keep products whose title contains at least one keyword.

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

Number of simultaneous browser requests; keep low for responsible crawling.

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

Use only an authorized Apify proxy configuration for larger runs.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.namshi.com/uae-en/women/"
    }
  ],
  "maxProducts": 100,
  "maxPages": 3,
  "includeDescription": true,
  "includeImages": true,
  "maxConcurrency": 1
}
```

# Actor output Schema

## `dataset` (type: `string`):

Dataset containing normalized product, blocked, partial, and error records.

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

Key-value summary containing product, blocked, partial, and error counts.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("coolinbex/namshi-fashion-scraper").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("coolinbex/namshi-fashion-scraper").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 '{}' |
apify call coolinbex/namshi-fashion-scraper --silent --output-dataset

```

## MCP server setup

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

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/M9gGMHwaCbmZiFg21/builds/zr79wvKFbn24x0uwq/openapi.json