WooCommerce Public Catalog & Price Change API

Export public product observations for supplier catalogs, price monitoring and e-commerce integrations. Returns exact decimal strings, availability flags, product images/categories, stable hashes and changes against your previous observation. Uses the unauthenticated WooCommerce Store API. No admin credentials or paid upstream key.

Quick start

{"storeUrls": ["https://porterandyork.com"], "maxProductsPerStore": 5}

This public example was tested at publication, but a third-party store may change or restrict access. Use your own authorized store for reliable integrations. Enter the WordPress installation URL, including its subdirectory when applicable. Download the default dataset as JSON, CSV or Excel. Inspect OUTPUT for source errors, pagination and completeness.

Repeat-run monitoring

1. Save the previousHashes object from the SNAPSHOT key-value record.
2. Include it as previousHashes in the next input.
3. Rows have NO_BASELINE when no baseline was supplied, FIRST_SEEN when absent from a supplied baseline, UNCHANGED when the hash matches, and CHANGED otherwise.

Hashes cover normalized name, SKU, type, prices, stock/purchasability/sale flags, URLs, images, categories and attributes. They exclude request page and observation timestamp. CHANGED is not exclusively a price change. FIRST_SEEN does not prove a product was newly listed. Only successfully emitted rows are included in SNAPSHOT. An incomplete snapshot cannot establish deletions. Do not interpret missing rows as removed products.

Prices and catalog coverage

Prices are exact strings normalized using currency_minor_unit, such as 1105 -> 11.05 for a two-decimal currency. Original currency and minor-unit precision are retained. Currency may depend on store/plugin configuration; there is no exchange conversion or checkout-price guarantee. Variable products are parent observations; public price_range is preserved when present. This is not a complete variant exporter. Stock flags are not exact inventory quantities. No sales, revenue or future inventory inference is performed.

Only visible products from /wp-json/wc/store/v1/products are queried; password-protected products are skipped. At most three stores, five pages of twenty products each and 100 returned observations per store. Pagination follows ascending product ID; duplicate IDs are not charged twice. The source can change during a run. OUTPUT.complete means the observed public query ended without truncation, protected records, pagination instability or errors; it is not proof of the store's full private catalog. A cap produces PRODUCT_LIMIT or PAGE_LIMIT. Unavailable or denied sources produce errors without bypassing access restrictions. A legitimate empty catalog can succeed with zero result events.

Pricing

$0.001 per emitted product observation ($1 per 1,000), plus a $0.005 Actor-start event for the default 256 MB run. Higher memory can multiply the start-event count according to Apify rules. Sources that fail incur no result event; startup can still apply. Inspect effective Store pricing before running. Event-only pricing includes platform usage. Budget truncation reports PARTIAL_BUDGET and complete=false. No external API, proxy or browser fees.

Access and resource bounds

Public HTTP(S), ports 80/443 only. Embedded credentials and private DNS addresses are rejected. Validated IPs are pinned while TLS hostname checks remain enabled. Up to five redirects, a 2 MiB decoded response limit and approximately 95 seconds network budget. robots.txt is respected; unavailable or blocking robots policy is a source error. No private REST API, login, cookies, cart, order, review-text or customer endpoint is accessed. HTML fallback, proxy rotation and blocking workarounds are not used. Image and product URLs are returned without being fetched. Respect source terms and data rights.

API and integration

POST https://api.apify.com/v2/actors/soilair~woocommerce-public-catalog-change-api/runs with your own Apify authorization header and the input JSON. Poll the returned run ID and retrieve its defaultDatasetId. OUTPUT and SNAPSHOT are in the run's default key-value store. You can configure schedules and integrations in Apify Console; this Actor creates neither. Carry previousHashes yourself; no hidden persistent baseline is used.

Data and support

Inputs and outputs stay in your Apify run storage under its retention settings. Requests go only to your public store inputs and their redirects/robots policy URLs. No separate customer-data or analytics endpoint is used. Do not submit secrets. Developed with AI assistance. Fixtures, real public-source observations and Apify cloud runs verify documented examples, not universal compatibility. Report a run ID and expected behavior through the issue tab without credentials.

Reference: https://developer.woocommerce.com/docs/apis/store-api/resources-endpoints/products/