POST /api/jumbo/recipes/search
Price: 5 credits
Search Jumbo.com recipes by keyword and by course, dish type, occasion, season, cuisine, difficulty, source, quick or five-ingredient recipes. Returns recipe cards with title, image, cooking time, servings, ingredient count, author and rating.
Dutch recipes from Jumbo.com. Filter values are the Dutch labels shown on the site (course 'Hoofdgerecht', cuisine 'Italiaans', season 'Herfst'); values of one filter match any, different filters must all match. Pass an id to jumbo/recipes for ingredients, linked products and instructions.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)keyword string — Search keyword; all recipes when empty (default: ""; examples: "lasagne")count integer required — Max number of results to return (min: 1; max: 1000)course array — Only recipes of these courses (any of them) (default: []; examples: ["Hoofdgerecht"])dish_type array — Only recipes of these dish types (any of them) (default: []; examples: ["Pasta"])occasion array — Only recipes for these occasions (any of them) (default: []; examples: ["Bbq"])season array — Only recipes of these seasons (any of them) (default: []; examples: ["Herfst"])cuisine array — Only recipes of these cuisines (any of them) (default: []; examples: ["Italiaans"])difficulty array — Only recipes of these difficulty levels (any of them) (default: []; examples: ["Makkelijk"])source array — Only recipes from these sources (any of them) (default: []; examples: ["Bo Schinkel"])quick_only boolean — Only recipes ready in 20 minutes (default: false)five_ingredients_only boolean — Only recipes with five ingredients (default: false)@type string (default: "JumboRecipeCard")id string requiredtitle string nullableurl string nullableimage string nullablecooking_minutes integer nullableingredient_count integer nullableservings integer nullablecalories integer nullablecourse string nullablecooking_tip string nullableauthor string nullablerating number nullablerating_count integer 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 — 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.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.