/myntra/brands/products

POST /api/myntra/brands/products

Price: 20 credits

List all Myntra products for a given brand. Returns product cards (id, name, brand, gender, category, colour, MRP, price, discount, rating, available sizes, image and URL) with filters for colour, size, gender, category and price range, plus result ordering.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• brand string required — Brand name (examples: "Nike", "Roadster"; minLength: 1)
• count integer required — Max number of products to return (min: 1)
• sort string nullable — Result ordering (one of: "new", "popularity", "discount", "price_asc", "price_desc", "customer_rating")
• color string nullable — Filter by colour (examples: "Black", "Blue")
• size string nullable — Filter by size (examples: "M", "XL")
• gender string nullable — Filter by gender (one of: "men", "women", "boys", "girls", "unisex")
• category string nullable — Filter by article-type category (examples: "Tshirts")
• min_price integer nullable — Minimum price filter (min: 0)
• max_price integer nullable — Maximum price filter (min: 0)

Response

• @type string (default: "MyntraProductCard")
• id string required
• name string nullable
• brand string nullable
• gender string nullable
• article_type string nullable
• sub_category string nullable
• master_category string nullable
• colour string nullable
• mrp number nullable
• price number nullable
• discount_percent integer nullable
• discount_label string nullable
• rating number nullable
• rating_count integer nullable
• sizes array (default: [])
• image string nullable
• url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.