POST /api/ah/stores/search
Price: 10 credits
Find Albert Heijn stores in the Netherlands and Belgium by city, country, store type, opening times and amenities, optionally sorted by distance from a point: name, address, coordinates, phone, opening hours, amenities.
Albert Heijn stores filtered by city, country (nl, be), store_types, opening_hours and amenities; with latitude and longitude they come nearest first with distance_meters. Without filters it lists every store.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of results to return (min: 1)city string nullable — Only stores in this city (examples: "Utrecht", "Antwerpen")country string nullable — Only stores in this country (one of: "nl", "be")store_types array — Only stores of these types (any of them) (default: []; one of: "regular", "xl", "to_go")opening_hours array — Only stores open now, open in the evening or open on Sunday (all of the chosen) (default: []; one of: "open_now", "evening", "sunday")amenities array — Only stores offering these amenity codes (default: []; examples: ["AOS"])latitude number nullable — Latitude to sort stores by distance from (min: -90; max: 90)longitude number nullable — Longitude to sort stores by distance from (min: -180; max: 180)@type string (default: "AhStore")id integer requiredname string nullablestore_type string nullablephone string nullablestreet string nullablehouse_number string nullablehouse_number_extra string nullablepostal_code string nullablecity string nullablecountry_code string nullablelatitude number nullablelongitude number nullabledistance_meters integer nullableopening_days array (default: [])@type string (default: "AhStoreOpeningDay")date integer requiredopens_at integer nullablecloses_at integer nullableamenities array (default: [])@type string (default: "AhStoreFeature")code string requireddescription 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 — 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.