Shopify Products - Full Public Catalog

Shopify Products — Full Catalog (APIFY-031)

Batch in 30 seconds

{"storeUrls":["https://www.allbirds.com","https://www.beardbrand.com"],"maxProductsPerStore":1000,"includeDescriptionHtml":false,"includeImages":true}

Each store is isolated, duplicate domains are skipped and successful catalogs remain available when another store fails. Start with 10–50 products, then raise maxProductsPerStore for full exports.

Extract a public Shopify storefront catalog into structured product rows without Admin API credentials, customer login, account cookies, or CAPTCHA solving.

Buyer job

Shopify store URL → products + variants + SKU + price + compare-at price + availability + vendor + tags + images

Input

• storeUrls — one or more public Shopify storefront domains/URLs.
• maxProductsPerStore — 1–5000, default 1000.
• includeDescriptionHtml — default false.
• includeImages — default true.
• requestTimeoutSecs — 5–60 seconds, default 30.

Output

One Dataset row per product. Variants stay nested under their product so the paid event maps to one delivered product row.

Important fields include storeDomain, productId, handle, title, vendor, productType, tags, productUrl, price range, compare-at price range, onSale, available, variants, and images.

Only products with a usable productId or handle, non-empty handle, and non-empty title are accepted into the paid Dataset output. A page containing products but no rows satisfying this contract fails as PRODUCT_SCHEMA_INCOMPLETE; malformed rows are never silently billed. Short pages are followed until an empty page, the configured cap, or a clear pagination failure, so a short first page is not treated as a complete catalog.

Billing

PPE event: product-result.

The Actor pushes successful rows to the Dataset first and then charges exactly the number of delivered product rows. Empty/failed stores do not create a charge. A delivery/billing count mismatch fails validation instead of being silently accepted.

Public-data boundary

This Actor uses the storefront's public Shopify catalog endpoint only. It does not use Shopify Admin API credentials, buyer/seller accounts, private inventory history, cookies, login sessions, CAPTCHA solving, checkout, or purchase automation. OUTPUT is an object, not a text blob. It reports requested/accepted/invalid/duplicate stores, input-cap truncation, processed/succeeded/failed stores, possible catalog truncation, delivered versus billed products, and failure details so recurring catalog calls can be audited.