/ulta/stores

POST /api/ulta/stores

Price: 20 credits

Find Ulta Beauty stores nearest to a point: address, phone, opening hours, services, pickup options and the brands each store carries, ordered by distance

How to use it

Find Ulta Beauty stores around a latitude and longitude, nearest first, with distance_miles measured in a straight line. Ulta stores are in the United States, so a point elsewhere returns the nearest US stores unless max_distance_miles is set.

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 point to search around (examples: 40.758; min: -90; max: 90)
• longitude number required — Longitude of the point to search around (examples: -73.9855; min: -180; max: 180)
• count integer required — Max number of stores to return (min: 1)
• max_distance_miles number nullable — Only stores within this many miles (examples: 25; >: 0)

Response

• @type string (default: "UltaStore")
• id string required
• store_number string nullable
• alias string nullable
• url string nullable
• name string nullable
• mall_name string nullable
• address string nullable
• address_line_2 string nullable
• city string nullable
• state string nullable
• postal_code string nullable
• country string nullable
• phone string nullable
• latitude number nullable
• longitude number nullable
• distance_miles number nullable
• timezone string nullable
• is_permanently_closed boolean nullable
• opening_date string nullable
• message string nullable
• description string nullable
• short_description string nullable
• booking_url string nullable
• hours array (default: [])
  • @type string (default: "UltaStoreHours")
  • day string required
  • opens_at string nullable
  • closes_at string nullable
• curbside_hours array (default: [])
  • @type string (default: "UltaStoreHours")
  • day string required
  • opens_at string nullable
  • closes_at string nullable
• special_hours array (default: [])
  • @type string (default: "UltaStoreSpecialHours")
  • date string required
  • is_closed boolean nullable
  • is_open_24_hours boolean nullable
  • opens_at string nullable
  • closes_at string nullable
• amenities array (default: [])
• services array (default: [])
• brands array (default: [])
• brands_coming_soon array (default: [])
• payment_methods array (default: [])
• categories array (default: [])
• tags array (default: [])

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.