Woolworths AU Product Search & Catalog (Unofficial)

Search Woolworths Australia products and fetch category, search, and item data in normalized output.

This is an unofficial actor and is not affiliated with Woolworths.

Supported operations

• categories
• search
• item
• category

Operation guide

The Apify Console form shows the union of all supported fields, so the visible inputs do not change when you switch operation. Use the guide below to know which fields are required.

• categories Required: none Optional: includeRaw
• search Required: query Optional: page, includeRaw
• item Required: productId or itemId or url Optional: includeRaw
• category Required: categoryId Optional: page, includeRaw

How categories work

categories returns a flattened version of the Woolworths category tree with id, name, slug, parent_id, and breadcrumb context. Use the returned id as categoryId for the category operation.

Example inputs

These starter examples were validated locally against the live site and are a good base for private smoke checks and saved tasks.

{
  "operation": "categories",
  "includeRaw": false
}

{
  "operation": "search",
  "query": "milk",
  "page": 1,
  "includeRaw": false
}

{
  "operation": "item",
  "productId": "888140",
  "includeRaw": false
}

{
  "operation": "category",
  "categoryId": "1_6E4F4E4",
  "page": 1,
  "includeRaw": false
}

Output

• Dataset: normalized products or structured category rows
• Key-value store OUTPUT: run summary with source, operation, success, total, errors, proxy, and monetization

Notes

• categories and search are the safest first smoke tests.
• item and category support real validated examples now: 888140 and 1_6E4F4E4.
• Product rows include richer category context, normalized image URLs, and parsed unit-price metadata.
• Default proxy strategy is direct, with shared runtime support for apify and custom proxy modes later.
• The runtime is prepared for future pay-per-event monetization.