/jumia/sellers

POST /api/jumia/sellers

Price: 10 credits

Get a Jumia seller store by slug or store URL: name, seller score, follower count, performance metrics (shipping speed, quality score, customer rating, cancellation rate), total product count and a paginated listing of the seller's products.

How to use it

Fetch a Jumia seller store profile by store slug (e.g. bafur-store) or store URL. Returns one item with alias, url, name, seller_score (0-100), follower_count, performance (shipping_speed/quality_score/customer_rating/cancellation_rate), product_count (total) and products (up to `count` of the seller's listings, each with id/name/price/rating/image). 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")
• seller string required — Jumia seller store slug or store URL (examples: "bafur-store", "https://www.jumia.com.ng/bafur-store/"; minLength: 1)
• count integer required — Max number of seller products to return (min: 1)

Response

• @type string (default: "JumiaSeller")
• id string nullable
• alias string required
• url string required
• name 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
• product_count integer nullable
• products array (default: [])
  • @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 — Seller not found (well-formed but nonexistent store slug, or page has no seller) 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.