/noon/sellers

POST /api/noon/sellers

Price: 1 credit

Get a Noon seller (marketplace partner) profile by partner code: store name, legal name, contact phone, joining date, unique customers, badges, overall rating with positive-rating and product-as-described percentages and the full star-rating breakdown.

How to use it

Fetch a Noon marketplace seller profile by partner code (e.g. p-99900) or a seller store URL. Returns one item with id (partner_code), url, name, legal_name, contact, email, location, joining_date, unique_customers, rating, rating_count, positive_percent, as_described_percent, badges, image, banner and rating_breakdown (per-star counts). Use the region parameter to switch marketplace/localisation.

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")
• seller string required — Noon seller partner code or a seller store URL containing it (examples: "p-99900", "https://www.noon.com/uae-en/seller/p-99900/"; minLength: 1)

Response

• @type string (default: "NoonSeller")
• id string required
• url string nullable
• name string nullable
• legal_name string nullable
• contact string nullable
• email string nullable
• location string nullable
• joining_date string nullable
• unique_customers string nullable
• rating number nullable
• rating_count integer nullable
• positive_percent number nullable
• as_described_percent number nullable
• badges array (default: [])
• image string nullable
• banner string nullable
• rating_breakdown array (default: [])
  • @type string (default: "NoonSellerRatingBucket")
  • rating number nullable
  • count integer 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 — Seller not found (well-formed but nonexistent partner code) 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.