/ulta/products

POST /api/ulta/products

Price: 10 credits

Get an Ulta Beauty product: brand, description, usage, ingredients, price, stock, rating, every shade or size, images, highlights, category path and delivery options

How to use it

Fetch one Ulta Beauty product by the id that ends its URL, or by the URL. Pass sku_id, or a URL with ?sku=, to get that shade or size's price and stock; variants lists every shade or size either way.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Ulta product id or URL (examples: "pimprod2051122", "https://www.ulta.com/p/cheek-thrills-multi-finish-face-trio-pimprod2051122", "xlsImpprod14251035"; minLength: 1)
• sku_id string nullable — Shade or size id to return; the product's default when omitted (examples: "2654271")

Response

• @type string (default: "UltaProduct")
• id string required
• sku_id string nullable
• url string nullable
• name string nullable
• brand string nullable
• brand_url string nullable
• summary string nullable
• description string nullable
• usage string nullable
• ingredients string nullable
• restrictions string nullable
• warning string nullable
• rating number nullable
• review_count integer nullable
• question_count integer nullable
• list_price number nullable
• sale_price number nullable
• discount number nullable
• currency string nullable
• price_label string nullable
• kit_price string nullable
• stock_status string nullable
• is_in_stock boolean nullable
• is_on_sale boolean nullable
• is_subscription_eligible boolean nullable
• subscription_discount number nullable
• variant_type string nullable
• variant_name string nullable
• size string nullable
• badges array (default: [])
• categories array (default: [])
  • @type string (default: "UltaCategoryRef")
  • name string required
  • url string nullable
• images array (default: [])
• videos array (default: [])
• highlights array (default: [])
  • @type string (default: "UltaHighlight")
  • name string required
  • description string nullable
  • url string nullable
• variants array (default: [])
  • @type string (default: "UltaVariant")
  • sku_id string required
  • name string nullable
  • description string nullable
  • url string nullable
  • image string nullable
  • swatch string nullable
  • list_price number nullable
  • sale_price number nullable
  • is_available boolean nullable
  • is_selected boolean nullable
  • tags array (default: [])
• fulfillment array (default: [])
  • @type string (default: "UltaFulfillment")
  • method string required
  • name string nullable
  • is_available boolean nullable
  • text string nullable
  • delivery_speed string nullable
  • delivery_note string nullable
• promotions array (default: [])
• offers array (default: [])
  • @type string (default: "UltaOffer")
  • description string nullable
• positive_review object nullable
  • @type string (default: "UltaReviewHighlight")
  • text string nullable
• negative_review object nullable
  • @type string (default: "UltaReviewHighlight")
  • text 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 — No Ulta product has this id, or the sku_id belongs to another product. 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.