/zara/stores/search

POST /api/zara/stores/search

Price: 5 credits

Find Zara physical stores near a geographic point (latitude/longitude). Returns stores ordered by distance, each with name, address, city, state, country, coordinates, phone, store type, sections and weekly opening hours.

How to use it

Search Zara physical stores by geolocation. Provide latitude and longitude (the center of the search) and optionally a radius in kilometers. Returns stores nearest first, each with id, name (malls only; street stores may have none), address, city, state/state_code, country/country_code, zip_code, latitude, longitude, phones, type (Street/Mall), kind, timezone, status, is_pickup_allowed, has_ecommerce, sections and opening_hours (per-day intervals with open_time/close_time).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• latitude number required — Latitude of the search point (min: -90; max: 90)
• longitude number required — Longitude of the search point (min: -180; max: 180)
• radius integer — Search radius in kilometers (default: 30; min: 1; max: 100)
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "ZaraStore")
• id string required
• name string nullable
• address string nullable
• city string nullable
• state string nullable
• state_code string nullable
• country string nullable
• country_code string nullable
• zip_code string nullable
• latitude number nullable
• longitude number nullable
• phones array (default: [])
• type string nullable
• kind string nullable
• timezone string nullable
• status string nullable
• is_pickup_allowed boolean nullable
• has_ecommerce boolean nullable
• sections array (default: [])
• opening_hours array (default: [])
  • @type string (default: "ZaraStoreOpeningHours")
  • date string nullable
  • week_day integer nullable
  • intervals array (default: [])
    • @type string (default: "ZaraStoreOpeningInterval")
    • open_time string nullable
    • close_time 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.