/namshi/products

POST /api/namshi/products

Price: 10 credits

Get full Namshi product details by parentSku (or product URL): product title, brand, normal and sale price, discount, currency, images and videos, size variants with per-size stock and price, product attributes, description, stock status, rating and review count, and delivery/returns flags. Region drives currency, stock and localisation.

How to use it

Fetch a single Namshi product by parentSku or product URL. Returns one item with id (parentSku), sku, url, alias, product_title, brand, brand_code, gender, listing_type, category, normal_price, sale_price, deal_price, discount_percent, deal_code, currency, image+images, videos, badges, tags, variant_name, stock_status/stock_label, max_qty, description, is_rocket/is_outlet/is_global/is_namshi_retail/is_returnable/is_exchangeable, brand_logo_url, rating and review_count, attributes (name/value pairs) and variants (each size with its own stock and price). Use the region parameter to switch currency and localised content.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• region string — Marketplace region (drives currency, stock and localisation) (default: "uae"; one of: "uae", "saudi", "kuwait", "qatar", "bahrain", "oman")
• language string — Content language (default: "en"; one of: "en", "ar")
• product string required — Namshi product identifier: parentSku or a full product URL (examples: "Z99CB16019DEB9D492EE8Z", "https://www.namshi.com/uae-en/buy-topshop-denim-barrel-jort-wh/Z99CB16019DEB9D492EE8Z/p/"; minLength: 1)

Response

• @type string (default: "NamshiProduct")
• id string required
• sku string nullable
• url string nullable
• alias string nullable
• product_title string nullable
• brand string nullable
• brand_code string nullable
• gender string nullable
• listing_type string nullable
• category string nullable
• normal_price number nullable
• sale_price number nullable
• deal_price number nullable
• discount_percent integer nullable
• deal_code string nullable
• currency string nullable
• image string nullable
• images array (default: [])
• videos array (default: [])
• badges array (default: [])
• tags array (default: [])
• variant_name string nullable
• stock_status string nullable
• stock_label string nullable
• max_qty integer nullable
• description string nullable
• is_rocket boolean nullable
• is_outlet boolean nullable
• is_global boolean nullable
• is_namshi_retail boolean nullable
• is_returnable boolean nullable
• is_exchangeable boolean nullable
• brand_logo_url string nullable
• rating number nullable
• review_count integer nullable
• attributes array (default: [])
  • @type string (default: "NamshiProductAttribute")
  • name string required
  • value string nullable
• variants array (default: [])
  • @type string (default: "NamshiProductVariant")
  • id string required
  • size string nullable
  • url string nullable
  • normal_price number nullable
  • sale_price number nullable
  • discount_percent integer nullable
  • max_qty integer nullable
  • stock_status string nullable
  • stock_label string nullable
  • is_rocket boolean 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 — Product not found (well-formed but nonexistent parentSku) 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.