/noon/products/search

POST /api/noon/products/search

Price: 5 credits

Search Noon products by keyword with rich filters: brand, seller, colour, price range, minimum rating, deals, price drop, new arrivals, noon-fulfilled, product grade, category and category-specific facets, plus sorting. Returns product cards with name, brand, price and discount, currency, rating, images, seller and specifications. Region drives currency and localisation.

How to use it

Search the Noon catalog by keyword and get matching product cards. Each item has id (sku), url, alias, name, brand, brand_code, price, original_price, discount_percent, currency, image+images, rating, rating_count, store_name, seller_rating, is_bestseller, nudges, deal_tag, flags and specifications. Filter with brands, sellers, colours, price_min/price_max, min_rating, price_drop, new_arrivals, fulfilled_by_noon, item_condition, deals, grades, category and the generic filters map for category-specific facets; order with sort. Use the returned id with the Noon product endpoint for full details.

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, pricing and localisation) (default: "uae"; one of: "uae", "saudi", "egypt", "kuwait", "bahrain", "oman", "qatar")
• language string — Content language (default: "en"; one of: "en", "ar")
• count integer required — Max number of products to return (min: 1)
• sort string — Result ordering (default: "recommended"; one of: "recommended", "price_low_to_high", "price_high_to_low", "rating", "best_selling", "new_arrivals")
• brands array — Filter by brand codes (e.g. apple, samsung, xiaomi) (default: []; examples: ["apple"])
• sellers array — Filter by seller partner codes (e.g. p_9404 for noon) (default: []; examples: ["p_9404"])
• colours array — Filter by colour family (default: []; one of: "black", "white", "blue", "red", "green", "pink", "purple", "yellow", "orange", "brown", "beige", "grey", "silver", "gold", "multi")
• price_min number nullable — Minimum price (min: 0)
• price_max number nullable — Maximum price (min: 0)
• min_rating number nullable — Minimum product rating (1-5) (min: 1; max: 5)
• price_drop string nullable — Keep items at their lowest price in a period (one of: "365_days", "30_days", "7_days")
• new_arrivals string nullable — Keep only recently added items (one of: "7_days", "30_days", "60_days")
• fulfilled_by_noon boolean nullable — Keep only items fulfilled by noon when true
• item_condition array — Filter by item condition (default: []; one of: "new", "refurbished")
• deals array — Filter by deal type (default: []; one of: "deals-generic", "mega-deal", "flash-sale-tag")
• grades array — Filter by product grade (default: []; one of: "max", "plus", "premium", "basic", "refurbished", "refurbished_assured")
• filters object — Additional category-specific facets as raw facet_code -> value(s) pairs (comma-separate multiple values), e.g. mobile_storage -> 256_gb or mobile_ram_size -> 8_gb,12gb_more. Facet codes vary per category. (default: {})
  • * string
• query string required — Search keyword (examples: "iphone", "running shoes", "coffee maker"; minLength: 1)
• category string nullable — Restrict the search to a category code (from a product's category_code / breadcrumbs) (examples: "electronics-and-mobiles/mobiles-and-accessories/mobiles-20905/smartphones")

Response

• @type string (default: "NoonProductCard")
• id string required
• sku string nullable
• url string nullable
• alias string nullable
• name string nullable
• brand string nullable
• brand_code string nullable
• price number nullable
• original_price number nullable
• discount_percent integer nullable
• currency string nullable
• image string nullable
• images array (default: [])
• rating number nullable
• rating_count integer nullable
• store_name string nullable
• seller_rating object nullable
  • @type string (default: "NoonSellerRating")
  • partner_code string nullable
  • store_name string nullable
  • rating number nullable
  • rating_count integer nullable
  • positive_percent number nullable
  • as_described_percent number nullable
  • partner_since_years integer nullable
  • badges array (default: [])
• is_bestseller boolean nullable
• best_seller_rank integer nullable
• is_buyable boolean nullable
• nudges array (default: [])
• deal_tag string nullable
• discount_tag_title string nullable
• discount_tag_code string nullable
• flags array (default: [])
• specifications array (default: [])
  • @type string (default: "NoonProductCardSpec")
  • name string required
  • value 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.