Myntra Product Scraper

Myntra Product Scraper is an Apify Actor for people who need structured product data from Myntra.com. It accepts a keyword, a listing or category URL, or a product URL or numeric product ID, and returns one record per product. The record can include fields such as product name, brand, price, MRP, discount, rating, sizes, stock, seller, images, specifications, and the canonical Myntra URL. It is HTTP-only, MCP-ready, and usable through Apify MCP.

Best fit and connected workflows

This Actor fits workflows that start with a product discovery question and end with structured product records. It routes cleanly across three common input styles:

• Keyword search for broad catalog discovery, such as a brand plus product type.
• Listing or category URLs for exact Myntra pages, filtered views, or sorted catalog slices.
• Product URLs or product IDs for direct detail extraction.

A practical workflow is to search a category, review the returned card fields, and then enrich selected items into full product-detail records. Another useful workflow is to feed a prepared list of product IDs into the Actor to resolve each ID directly into a detail record for downstream analysis or agent use.

Myntra Product Scraper is designed as a focused standalone workflow.

Practical scenario

A merchandiser wants to compare women's kurta options on Myntra before updating a catalog sheet. She starts with a keyword search for "women kurta" and sets a modest maxItems value for a sample run. The Actor returns fields such as productName, brand, price, mrp, discountPercent, rating, ratingCount, inStock, and url. She uses price, discountPercent, and ratingCount to shortlist products, then opens the returned URLs to review the product detail pages or runs the same selection with enrichDetails enabled to collect sizes, seller, specifications, and images. Her next action is to add the shortlisted records to a catalog report.

Input fields

Field	Type	Purpose
search	string	Free-text keyword for Myntra search results. Returns paginated product cards.
startUrls	array of strings	Myntra listing/category URLs or product URLs. Auto-detects listing pages versus product pages.
productIds	array of strings	Bare numeric Myntra product/style IDs for direct detail resolution.
enrichDetails	boolean	Follows search or listing results to product pages for sizes, seller, specs, images, and description.
maxItems	integer	Maximum number of product records across all inputs. Pagination stops at this count.
pincode	string	Indian 6-digit delivery pincode used for price and serviceability context.
proxyConfiguration	object	Proxy configuration for Apify Proxy or custom proxy use.

Focused JSON input example

{
  "search": "women floral dress",
  "enrichDetails": true,
  "maxItems": 12,
  "pincode": "110001",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Output fields

One dataset item is produced per Myntra product. Search and listing records carry card-level fields, while detail records add sizes, seller, specs, images, and description.

Field	Type	Meaning
source	string	Record origin: search or detail.
productId	string	Myntra style or product ID.
productName	string	Product title on search or listing records.
name	string	Product title on detail records.
brand	string	Brand name.
gender	string	Target gender such as Men, Women, Unisex, Boys, or Girls.
primaryColour	string	Primary colour on search records.
baseColour	string	Base colour on detail records.
articleType	string	Article type such as Tshirts or Casual Shoes.
masterCategory	string	Top-level category such as Apparel or Footwear.
subCategory	string	Subcategory such as Topwear.
mrp	integer	Maximum retail price in INR.
price	integer	Selling price in INR after discount.
discountAmount	integer	Discount amount in INR on search records.
discountPercent	integer	Discount percentage.
discountLabel	string	Display discount label.
rating	number	Average star rating from 0 to 5.
ratingCount	integer	Number of ratings.
sizes	array	Available sizes.
inStock	boolean	Whether any size is in stock.
colourVariantsCount	integer	Number of colour variants on search records.
seller	string	Selected seller name on detail records.
countryOfOrigin	string	Country of origin on detail records.
manufacturer	string	Manufacturer or packer information on detail records.
specifications	object	Article attributes such as fabric, fit, or pattern.
description	string	Plain-text product description.
image	string	Primary product image URL on search records.
images	array	All product image URLs on detail records.
url	string	Canonical Myntra product URL.
scrapedAt	string	ISO 8601 scrape timestamp.

Illustrative JSON output record

{
  "source": "detail",
  "productId": "42879609",
  "name": "Slim Fit T-Shirt",
  "brand": "Roadster",
  "gender": "Men",
  "masterCategory": "Apparel",
  "subCategory": "Topwear",
  "mrp": 1299,
  "price": 649,
  "discountPercent": 50,
  "rating": 4.2,
  "ratingCount": 1834,
  "sizes": [
    {
      "label": "M",
      "available": true,
      "skuId": "123456"
    }
  ],
  "inStock": true,
  "seller": "Selected Seller",
  "specifications": {
    "Fabric": "Cotton",
    "Fit": "Slim Fit"
  },
  "description": "Product description text.",
  "images": [
    "https://cdn.example.com/image-1.jpg"
  ],
  "url": "https://www.myntra.com/.../42879609/buy",
  "scrapedAt": "2026-07-27T00:00:00.000Z"
}

How it works

The Actor reads public Myntra product data from search, listing, and product pages. The supplied contract indicates that Myntra product information is available in the site's embedded window.__myx SSR JSON, and the Actor uses HTTP requests rather than a browser. The manifest also notes the use of a Chrome-like TLS fingerprint implementation for access to Myntra pages. Search and listing inputs return paginated card records, while product URLs and product IDs resolve to full detail records. When enrichDetails is enabled, each search or listing result is followed to its product page for expanded fields.

Pricing

Myntra Product Scraper uses Pay per event pricing together with Apify platform usage. The live Pricing tab in the Apify console shows the current event charges and platform usage details for this Actor.

A simple way to think about cost is by event count. For example, a run that returns one hundred search result records is billed by the Product scraped event for each returned product, plus the Actor start event for the run itself. If the same execution enriches those records into product-detail pages, the Product detail scraped event applies for each detailed record as well. For the most accurate view of current pricing, open the live Pricing tab.

Use with AI agents (MCP)

This Actor is available through Apify MCP as a tool that returns structured Myntra product data from a keyword, listing URL, product URL, or product ID. The exact Actor identity is khadinakbar/myntra-product-scraper.

Scrape Myntra products for the keyword "women kurta", return up to 10 items, and include product details for each result. Use the returned dataset items to extract brand, price, discount, rating, sizes, seller, and product URL.

Output interpretation is straightforward: each dataset item represents one product record. Search and listing runs usually return card fields first, while product URLs, product IDs, and enriched runs return detail fields such as sizes, seller, images, description, and specifications. Provenance is visible in the source field, which identifies whether the record came from a search/listing card or a product-detail page. Scope follows the input style: keyword inputs cover paginated search results, listing URLs cover the specified catalog view, and product IDs or product URLs resolve direct product records. Pagination continues until maxItems is reached. Cost guidance follows the same event model as the Actor UI: more returned products mean more billed events, and detailed records are billed separately from card records when detail scraping is used.

Run via the Apify API

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const run = await client.actor('khadinakbar/myntra-product-scraper').call({
  search: 'nike running shoes',
  maxItems: 5,
  enrichDetails: true,
  proxyConfiguration: {
    useApifyProxy: true,
  },
});

const dataset = await client.dataset(run.defaultDatasetId).listItems();
for (const item of dataset.items) {
  console.log(item.brand, item.price, item.url);
}

Best results and outcome guidance

Use search when you want Myntra to find products by text. Use startUrls when you already have a category page, a filtered listing, or a product page URL. Use productIds when you already have the numeric product IDs and want direct detail records. Keep maxItems aligned with the size of the sample or catalog segment you need. Turn on enrichDetails when your downstream work needs sizes, seller, specifications, images, or descriptions. The pincode field is useful when you want price and serviceability context for a specific Indian delivery area.

Focused standalone workflow

Myntra Product Scraper is designed as a focused standalone workflow for the public input and structured output contract described above.

Design note

I found that the dataset contract separates productName for search and listing records from name for detail records, which is a useful signal for handling mixed record types in downstream workflows.

FAQ

When should I use a keyword versus a listing URL?
Use a keyword for general discovery. Use a listing or category URL when you want a specific Myntra page, filter, or sort state.

When should I use product IDs?
Use product IDs when you already have Myntra style IDs and want each one resolved directly to a product-detail record.

What changes when enrichDetails is enabled?
Search or listing results are followed to the product page so the returned record can include sizes, seller, specifications, images, and description.

What does source tell me?
It identifies the record origin as search for a card record or detail for a product-page record.

Can I use this in an AI workflow?
Yes. The Actor is MCP-ready and can be called as an Apify MCP tool from agents that need structured product data.

Responsible use

This Actor reads public product information from Myntra.com. Use the output in a way that respects applicable laws, Myntra's terms, and intellectual property rights. Review how you store, transform, and redistribute scraped data, especially when it feeds automated decisions or public-facing systems.