/jumia/products

POST /api/jumia/products

Price: 5 credits

Get full Jumia product details by product URL, numeric id or config SKU: name, brand, price, list_price, discount, currency, images, rating with 5-star breakdown, review count, stock, breadcrumbs, key features, what's in the box, specifications, seller with performance metrics, promotions, official store flag, express delivery flag and last modified time.

How to use it

Fetch a single Jumia product by product URL, numeric id or config SKU. Returns one item with id, url, sku, name, brand, price/list_price/discount_percentage/currency, image+images, rating, rating_count, review_count, rating_breakdown (star_5..star_1 counts), stock_status/is_in_stock, category+breadcrumbs, key_features, whats_in_box, specifications (spec name to value), seller (id/name/url/seller_score/follower_count/performance shipping_speed+quality_score+customer_rating+cancellation_rate), promotions, is_official_store, is_express and updated_at (unix seconds). 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")
• product string required — Jumia product URL, numeric product id, or config SKU (examples: "https://www.jumia.com.ng/itel-20000mah-dual-output-fast-charging-power-bank-98332547.html", "98332547", "IT724EA18DAM5NAFAMZ"; minLength: 1)

Response

• @type string (default: "JumiaProduct")
• id string required
• url string required
• sku string nullable
• name string nullable
• brand string nullable
• price number nullable
• list_price number nullable
• discount_percentage number nullable
• currency string nullable
• image string nullable
• images array (default: [])
• rating number nullable
• rating_count integer nullable
• review_count integer nullable
• rating_breakdown object nullable
  • @type string (default: "JumiaRatingBreakdown")
  • star_5 integer nullable
  • star_4 integer nullable
  • star_3 integer nullable
  • star_2 integer nullable
  • star_1 integer nullable
• stock_status string nullable
• is_in_stock boolean nullable
• category string nullable
• breadcrumbs array (default: [])
• key_features array (default: [])
• whats_in_box array (default: [])
• specifications object (default: {})
  • * string
• seller object nullable
  • @type string (default: "JumiaProductSeller")
  • id string nullable
  • name string nullable
  • url string nullable
  • seller_score integer nullable
  • follower_count integer nullable
  • performance object nullable
    • @type string (default: "JumiaSellerPerformance")
    • shipping_speed string nullable
    • quality_score string nullable
    • customer_rating string nullable
    • cancellation_rate string nullable
• promotions array (default: [])
• is_official_store boolean nullable
• is_express boolean nullable
• description string nullable
• updated_at 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 — Product not found (well-formed but nonexistent id/SKU, or page has no product) 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.