POST /api/jumbo/products/category
Price: 5 credits
List the products of a Jumbo.com category, optionally filtered by brand, dietary preference and offers and sorted by price. Returns the same product cards as the search.
Products of one Jumbo.com (Dutch supermarket) category, given as a category path from jumbo/categories (alias) or a category page URL; same filters and sort as the product search. Each result has id (SKU), title, brand, price, list_price, price_per_unit, availability, promotions, badges and characteristics.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)category string required — Category path or category page URL (examples: "zuivel,-boter-en-eieren", "zuivel,-boter-en-eieren/verse-melk", "https://www.jumbo.com/producten/zuivel,-boter-en-eieren/"; minLength: 1)count integer required — Max number of results to return (min: 1; max: 3000)sort string nullable — Result order; the default is by popularity (one of: "price_asc", "price_desc", "price_per_unit_asc")brand array — Only products of these brands (any of them), as shown on the site (default: []; examples: ["Jumbo"])diet array — Only products matching all of these dietary preferences, as shown on the site (default: []; examples: ["Vegetarisch"])offers_only boolean — Only products currently on offer (default: false)@type string (default: "JumboSearchProduct")id string requiredtitle string nullablesubtitle string nullablebrand string nullablecategory string nullableimage string nullableurl string nullableprice number nullablelist_price number nullableprice_per_unit number nullableprice_unit string nullableavailability object nullable@type string (default: "JumboAvailability")status string nullableis_available boolean nullablelabel string nullablestock_limit integer nullablereason string nullablenote string nullabledelisted_date integer nullableis_in_assortment boolean nullableis_sponsored boolean (default: false)promotions array (default: [])@type string (default: "JumboPromotion")id string requiredtags array (default: [])group string nullableimage string nullableurl string nullableduration string nullableduration_title string nullableduration_description string nullablestart object nullable@type string (default: "JumboPromotionDate")date integer nullableday_short string nullablemonth_short string nullableend object nullable@type string (default: "JumboPromotionDate")date integer nullableday_short string nullablemonth_short string nullablemax_quantity integer nullablevolume_discounts array (default: [])@type string (default: "JumboVolumeDiscount")volume string nullablediscount string nullableis_kies_and_mix boolean (default: false)badges array (default: [])@type string (default: "JumboBadge")text string nullableimage string nullablecharacteristics array (default: [])@type string (default: "JumboCharacteristic")name string nullablevalue string nullableimage string nullable422 — 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 — No category exists at this path 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.