Myer AU Product Scraper

Extract Myer Australia product, price, category, brand, offer-page, and product-detail data for ecommerce monitoring and catalog intelligence.

Use this unofficial Myer scraper to monitor assortment changes, track sale pages, enrich product databases, compare brands, discover category shelves, and feed market research or price intelligence workflows.

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

Recommended Saved Tasks

Eight ready-to-run Apify Saved Tasks cover product search monitoring, category shelves, product detail enrichment, brand tracking, offer pages, category maps, brand directories, and filter discovery. Their proven inputs and use cases are documented in ./SAVED_TASKS.md.

Supported operations

• probe - Check access to the Myer category API.
• categories - Build a Myer category map with category IDs, slugs, names, and breadcrumbs.
• search_filters - Discover live category and facet values for search or category workflows.
• search - Search Myer products by keyword.
• category - Browse products from a Myer category shelf.
• brands - Extract public brands from Myer navigation.
• brand - Monitor a Myer brand page.
• offers_featured - Extract the current public promotional strip with offer messages and ready-to-use sale URLs.
• offers - Resolve a Myer offer/sale page URL into product results.
• item - Extract normalized product detail data by product slug.

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.

• probe Required: none Optional: includeRaw

• categories Required: none Optional: depth, includeRaw

• search_filters Required: none Optional: query, slug, categoryId, category_id, facets, depth, includeRaw

• search Required: query Optional: page, pageSize, facets, details, includeFilters, includeRaw

• category Required: slug or categoryId/category_id Optional: page, pageSize, facets, details, includeFilters, includeRaw

• brands Required: none Optional: includeRaw

• brand Required: brand or url Optional: page, facets, details, includeFilters, includeRaw

• offers_featured Required: none Optional: includeRaw

• offers Required: url Optional: details, includeFilters, includeRaw

• item Required: slug Optional: includeRaw

Example inputs

{
  "operation": "search",
  "query": "dress",
  "page": 1,
  "pageSize": 10,
  "includeFilters": true,
  "includeRaw": false
}

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

{
  "operation": "category",
  "slug": "women-clothing-sale",
  "categoryId": "974553",
  "page": 1,
  "pageSize": 10,
  "includeFilters": true,
  "includeRaw": false
}

{
  "operation": "item",
  "slug": "basque-long-sleeve-midi-georgette-dress-with-belt-in-navy",
  "includeRaw": false
}

{
  "operation": "brand",
  "brand": "Blaq",
  "page": 1,
  "includeFilters": true,
  "includeRaw": false
}

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

{
  "operation": "offers",
  "url": "/c/offers/home--sale",
  "includeFilters": true,
  "includeRaw": false
}

{
  "operation": "search_filters",
  "query": "dress",
  "depth": 1,
  "includeRaw": false
}

Output

• Dataset: normalized products, categories, brands, or offers depending on operation
• Key-value store OUTPUT: run summary with source, operation, success, total, errors, proxy, and monetization

Output fields

Depending on the operation, dataset items may include:

Products:

• id - Product ID
• slug - Product slug for URL
• name - Product name
• brand - Brand name
• source_url - Full product URL
• price - Current price
• discount_price - Discount/sale price
• currency - AUD
• saved_amount - Amount saved
• saved_percent - Percentage saved
• availability - in_stock or out_of_stock
• in_stock - Boolean availability flag
• buyable - Boolean buyable flag
• color - Product color
• images - List of image URLs
• price_info - Price breakdown
• variants - Product variants (when details=true)
• barcodes - EAN barcodes (item operation)
• attributes - Product attributes (item operation)
• breadcrumbs - Category breadcrumbs (item operation)
• payment_flags - Payment method flags (item operation)

Categories:

• id - Category ID
• slug - Category slug
• name - Category name
• children - Child categories (if depth > 0)
• breadcrumbs - Category path

Brands:

• name - Brand name
• slug - Brand slug
• url - Brand URL
• path - Brand path
• landing_type - brand_page or category_page
• section - Navigation section

Offers:

• message - Offer message
• url - Offer URL
• path - Offer path
• facets - Parsed facet values

Notes

• For category, first run categories and copy a real slug or categoryId from that output.
• For item, use the slug from search or category results.
• For brand, use the brand slug from brands output, or pass a full url for featured-brand/category pages.
• For offers, use a concrete Myer offer path such as /c/offers/home--sale.
• The facets parameter uses comma-separated exact facet values returned by live Myer responses. Use search_filters to discover available facet values.
• maxItems can cap the final Dataset for any operation. It is especially useful for brand, offer, category-map, and directory exports.
• Default access strategy is direct, the cheapest route verified against the live Myer source. auto is available for accounts whose Actor token can create Apify proxy configurations.
• details=true on listing endpoints only expands fields already present in the listing payload. It does not trigger hidden per-item detail fetches.

Use with n8n / Make

An importable n8n example is included in examples/n8n_myer_prices_to_google_sheets.json.

The workflow is:

Myer Actor → wait for run → Dataset products → Google Sheets / Telegram / CRM

Start a run and wait for completion:

curl -X POST "https://api.apify.com/v2/acts/dromb~myer-wave1/runs?token=YOUR_APIFY_TOKEN&waitForFinish=120" \
  -H "Content-Type: application/json" \
  -d '{"operation":"search","query":"dress","pageSize":10,"maxItems":10}'

Read defaultDatasetId from the run response and download clean rows:

$curl "https://api.apify.com/v2/datasets/DATASET_ID/items?clean=true&format=json&token=YOUR_APIFY_TOKEN"

For production workflows, continue only when the run is SUCCEEDED, OUTPUT.success=true, and OUTPUT.errors=[].

Proxy behavior

• Recommended mode: direct
• Proxy required: No
• Startup strategy: direct
• direct forces the cheapest route. auto tries direct first and can use an Apify datacenter fallback when proxy permission is available. apify forces datacenter proxy, and residential forces an Australian residential route. special is available only for explicit diagnostics and is not recommended for normal Myer runs.
• Browser automation is not required for the current public source.

Limitations

• Featured offer strips can change or temporarily disappear with Myer's campaigns. Use offers with a concrete current sale URL for product extraction.
• Some featured-brand/category brand pages may require URL-based routing via the url parameter instead of brand.
• Product availability and pricing may vary by location; this actor uses the default public API response.