/jumbo/products/search

POST /api/jumbo/products/search

Price: 5 credits

Search Jumbo.com products by keyword. Returns product cards with title, brand, category, image, current price, regular price during promotions, price per unit, availability, promotions, badges, characteristics and a sponsored flag.

How to use it

Keyword search across the Jumbo.com (Dutch supermarket) catalog. Each result has id (SKU), title, subtitle (pack size), brand, category, image, url, price (current selling price), list_price (regular price, filled only while a promotion is active), price_per_unit/price_unit (EUR), availability, is_in_assortment, is_sponsored, promotions (with discount tags like '1+1 gratis' and start/end dates), badges and characteristics (freshness/quality labels).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (examples: "pindakaas", "melk"; minLength: 1)
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "JumboSearchProduct")
• id string required
• subtitle string nullable
• brand string nullable
• category string nullable
• image string nullable
• url string nullable
• price number nullable
• list_price number nullable
• price_per_unit number nullable
• price_unit string nullable
• availability object nullable
  • @type string (default: "JumboAvailability")
  • status string nullable
  • is_available boolean nullable
  • label string nullable
  • stock_limit integer nullable
  • reason string nullable
  • note string nullable
• is_in_assortment boolean nullable
• is_sponsored boolean (default: false)
• promotions array (default: [])
  • @type string (default: "JumboPromotion")
  • id string required
  • tags array (default: [])
  • group string nullable
  • image string nullable
  • url string nullable
  • duration string nullable
  • start object nullable
    • @type string (default: "JumboPromotionDate")
    • date integer nullable
    • day_short string nullable
    • month_short string nullable
  • end object nullable
    • @type string (default: "JumboPromotionDate")
    • date integer nullable
    • day_short string nullable
    • month_short string nullable
  • max_quantity integer nullable
  • volume_discounts array (default: [])
    • @type string (default: "JumboVolumeDiscount")
    • volume string nullable
    • discount string nullable
  • is_kies_and_mix boolean (default: false)
• badges array (default: [])
  • @type string (default: "JumboBadge")
  • text string nullable
  • image string nullable
• characteristics array (default: [])
  • @type string (default: "JumboCharacteristic")
  • name string nullable
  • value string nullable
  • image string 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 — 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.