Jumia search

GET https://api.api.sh/jumia/v1/search
1 credit / call e-commerce try it in the playground →

Jumia search or category listing (Nigeria, Kenya, Egypt, Morocco, Ghana, Côte d'Ivoire, Uganda, Senegal, Tunisia, Algeria): SKU, name, brand, link, price, old price, discount, rating and count, categories, seller, sponsored and Express flags, badges and images, with price range, rating, Express and tag filters, sort and paging, plus every filter with options. Also filter by brand, size, colour, minimum discount and minimum seller score (values as listed in filters).

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
q string Search words (or category). Example: iphone
category string Category path, e.g. smartphones.
country ng | ke | eg | ma | gh | ci | ug | sn | tn | dz Jumia country (default ng). Example: ng
sort popularity | newest | lowest-price | highest-price | rating Sort order. Example: lowest-price
min_price integer Lowest price (local currency).
max_price integer Highest price.
rating integer Minimum stars (1-5).
express boolean true for Jumia Express items only.
tag string Campaign or store tag, e.g. JMALL (official stores).
brand string One brand slug, e.g. adidas or samsung (the brand filter's option value, with or without its numeric prefix). Works with q or a one-level category; alone it lists the brand's catalog.
size string Size value(s) from the size filter, comma-separated, e.g. 42 or 42,43.
color string Colour name(s) from the colour filter (color_family), comma-separated, e.g. Black,Blue.
discount_min integer Minimum discount in percent (1-99), e.g. 50.
seller_rating integer Minimum seller score (1-5).
page integer Page number (default 1). next_page is null on the last page. Example: 1

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/jumia/v1/search?q=iphone" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.