POST /api/jumbo/stores
Price: 1 credit
Get a Jumbo supermarket by store id or store page URL: address, coordinates, phone, weekly opening hours, dated holiday hours, in-store facilities and home delivery.
One Jumbo store by id or store page URL. Opening hours are clock times in UTC; opening_exceptions are holiday and special dates as unix timestamps with a reason.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)store string required — Store id or store page URL (examples: "3119", "https://www.jumbo.com/winkel/amersfoort/jumbo-amersfoort-wiekslag"; minLength: 1)@type string (default: "JumboStore")id string requiredname string nullableurl string nullablealias string nullablelocation_type string nullableaddress object nullable@type string (default: "JumboStoreAddress")street string nullablehouse_number string nullablepostal_code string nullablecity string nullablelatitude number nullablelongitude number nullablephone string 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 nullablefacilities object nullable@type string (default: "JumboStoreFacilities")has_cooking_studio boolean nullablehas_dry_cleaning boolean nullablehas_flowers boolean nullablehas_kitchen boolean nullablehas_liquor_service boolean nullablehas_pharmacy boolean nullablehas_photo_service boolean nullablehas_post_office boolean nullablehas_self_checkout boolean nullablehas_self_scan boolean nullablehas_wifi boolean nullableparking string nullablepick_up_type string nullablehas_home_delivery 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 — No store exists with this id or URL 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.