Ulta Beauty US Product Scraper

Turn public Ulta Beauty storefront pages into structured product data for price monitoring, beauty catalog research, assortment comparison, ingredient analysis, and workflow automation.

The Actor keeps search and category results compact while the item operation returns richer product details such as ingredients, usage, variants, reviews, badges, and images.

What you can extract

• Product search results with prices, ratings, reviews, images, badges, and URLs
• Category product listings with pagination and sorting
• Rich product details including ingredients, usage, variants, breadcrumbs, and review samples
• Public category links
• Search filters and sort options
• A lightweight storefront connectivity probe

Quick start

Search for products:

{
  "operation": "search",
  "query": "lipstick",
  "page": 1,
  "sort": "relevance",
  "proxy": "auto"
}

Get a category:

{
  "operation": "category",
  "url": "https://www.ulta.com/shop/makeup/lips/lip-liner",
  "page": 1,
  "proxy": "auto"
}

Get rich product details:

{
  "operation": "item",
  "url": "https://www.ulta.com/p/macximal-silky-matte-lipstick-pimprod2043558?sku=2621440",
  "proxy": "auto"
}

Operations

Operation	Required input	Dataset records
search	query	One record per product
category	url or path	Products, or one landing-category record
item	url, path, or sku	One rich product record
categories	None	One record per discovered category
search/filters	query	One filter metadata record
probe	None	One connectivity record

For item lookups, a full public product URL is more reliable than SKU-only resolution.

Output

Product and category data is written to the default Dataset. Service summaries and errors are not mixed into product rows.

The OUTPUT record in the default key-value store contains:

• success status
• number of Dataset records
• source result count and pagination when available
• selected connection route
• an actionable errors array

A failed source request fails the Actor run instead of producing a misleading successful run with an error row.

Proxy choices

auto starts with the cheapest direct route. You can explicitly select:

• direct
• datacenter
• residential
• special with specialProxyGroup
• custom with customProxyUrl

Current cloud validation shows that direct is the best default and US residential is the working paid fallback. Ulta currently blocks the tested Apify datacenter route, while tested account-specific special groups did not produce usable search results. Use a paid proxy tier only if direct access is blocked. Proxy credentials are never written to Dataset or OUTPUT.

Common use cases

• Monitor price and promotion changes for a product list
• Compare brands and assortments within a beauty category
• Build ingredient-aware beauty research datasets
• Track ratings and review volume
• Enrich a CRM, spreadsheet, or internal product catalog

Limitations

• Ulta can change its storefront data structures or access controls.
• SKU-only lookup is best effort; use a product URL when possible.
• Top-level category pages may be navigation landings and return subcategories instead of products.
• Availability can vary by store and user location; the Actor reports only public storefront data exposed by the selected page.

Responsible use

This is an unofficial Actor and is not affiliated with, endorsed by, or sponsored by Ulta Beauty. Use it responsibly and in accordance with applicable laws and website terms.