POST /api/jumbo/stores/search
Price: 5 credits
Find Jumbo stores nearest to a city, postal code or address, closest first: name, address, distance, weekly opening hours, holiday hours and which of in-store shopping, home delivery and collection each offers.
Jumbo stores in the Netherlands nearest to a place, sorted by distance_km, optionally within a radius and of chosen store types. The place is a postal code, a town or village (optionally with its province), a street address or a nickname such as Den Bosch; a municipality name that is not also a town or village (Hoeksche Waard, Súdwest-Fryslân, Land van Cuijk) returns an empty list. Opening hours are clock times in UTC. Pass an id to jumbo/stores for phone, coordinates and facilities.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)location string required — Dutch city, postal code or street address (examples: "Utrecht", "3526MC")count integer required — Max number of results to return (min: 1)radius integer — Search radius in kilometres (default: 1000; min: 1; max: 1000)store_types array — Only stores of these types (any of them); all types when empty (default: []; one of: "supermarket", "supermarket_pick_up_point", "pick_up_point")@type string (default: "JumboStoreCard")id string requiredname string nullableurl string nullablealias string nullablelocation_type string nullablestreet string nullablehouse_number string nullablecity string nullabledistance_km number nullableopening_hours array (default: [])@type string (default: "JumboOpeningHours")day string requiredopens string nullablecloses string nullableopening_exceptions array (default: [])@type string (default: "JumboOpeningException")starts_at integer nullableends_at integer nullablereason string nullablehas_in_store_shopping boolean nullablehas_home_delivery boolean nullablehas_collection boolean 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.