/jumia/products/search

POST /api/jumia/products/search

Price: 10 credits

Search Jumia products by keyword, category or brand with full filter support: price range, discount, official store, express delivery, refurbished, color, RAM, minimum rating, minimum seller score, sort order and extra category facets. Returns id, name, brand, price, list_price, discount, rating, review count, image and badges.

How to use it

Search or list Jumia products. Provide at least one of query (keyword), category (slug) or brand. Filter by price_min/price_max, discount_percentage (10/20/30/40/50), official_store, express_delivery, refurbished, color, ram, min_rating (1-4), min_seller_score (1-4), sort (popularity/newest/price_asc/price_desc/rating) and extra category facets via filters. Each result has id (SKU), url, name, brand, price/list_price/discount_percentage/currency, image, rating, review_count, is_official_store, is_express. Use the domain field for other Jumia country marketplaces.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• domain string — Jumia country marketplace domain. (default: "jumia.com.ng"; one of: "jumia.com.ng", "jumia.com.eg", "jumia.com.gh", "jumia.ci", "jumia.co.ke", "jumia.ma", "jumia.sn")
• query string nullable — Search keyword (examples: "power bank", "iphone")
• category string nullable — Category slug to list (examples: "phones-tablets", "electronics")
• count integer required — Max number of results to return (min: 1)
• sort string — Result ordering (default: "popularity"; one of: "popularity", "newest", "price_asc", "price_desc", "rating")
• price_min integer nullable — Minimum price filter (min: 0)
• price_max integer nullable — Maximum price filter (min: 0)
• brand string nullable — Brand name filter (examples: "oraimo", "samsung")
• discount_percentage string nullable — Minimum discount percentage bucket (one of: "10", "20", "30", "40", "50")
• official_store boolean nullable — Only official store products
• express_delivery boolean nullable — Only Jumia Express products
• refurbished boolean nullable — Only refurbished products
• color string nullable — Color filter (examples: "Black", "Blue")
• ram string nullable — RAM (GB) filter (examples: "4", "8")
• min_rating string nullable — Minimum product star rating (one of: "1", "2", "3", "4")
• min_seller_score string nullable — Minimum seller score band (one of: "1", "2", "3", "4")
• filters object nullable — Extra category-specific facets as name/value (e.g. product_type, display_size, megapixels, system_memory, screen_size) (examples: {"product_type":"Smartphones"})
  • * string

Response

• @type string (default: "JumiaSearchProduct")
• id string required
• url string required
• name string nullable
• brand string nullable
• price number nullable
• list_price number nullable
• discount_percentage number nullable
• currency string nullable
• image string nullable
• rating number nullable
• review_count integer nullable
• is_official_store boolean (default: false)
• is_express boolean (default: false)

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.