Drakes AU Product Search & Catalog (Unofficial) avatar

Drakes AU Product Search & Catalog (Unofficial)

Pricing

from $0.04 / 1,000 results

Go to Apify Store
Drakes AU Product Search & Catalog (Unofficial)

Drakes AU Product Search & Catalog (Unofficial)

Search products from Drakes Australia and fetch normalized catalog data for search, item pages, and category pages.

Pricing

from $0.04 / 1,000 results

Rating

0.0

(0)

Developer

Dmitriy Gyrbu

Dmitriy Gyrbu

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Drakes AU Product Search, Catalog & Store Discovery (Unofficial)

Search products from Drakes Australia, fetch normalized catalog data, and discover real store/shop values from the live store chooser.

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

Supported operations

  • stores
  • search
  • item
  • categories
  • 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.

  • stores Required: none Optional: query, limit, includeRaw
  • search Required: query Optional: shop, page, includeRaw
  • item Required: itemSlug or itemId Optional: shop, includeRaw
  • categories Required: none Optional: shop, topOnly, includeRaw
  • category Required: categorySlug or categoryId Optional: shop, page, includeRaw

How shop values work

Do not guess shop values manually.

Use the stores operation first. It returns the live shop metadata parsed from https://online.drakes.com.au/change, including:

  • shop: canonical shop code/host prefix, for example 079
  • catalogue_url
  • shop_url
  • store_info_url
  • address, phone, and store attributes

So shop: "079" is not a magic hardcoded value. It comes from the live Drakes store chooser and currently maps to Drakes Online Findon.

Example inputs

{
"operation": "stores",
"query": "findon",
"limit": 5,
"includeRaw": false
}
{
"operation": "search",
"shop": "079",
"query": "bananas",
"page": 1,
"includeRaw": false
}
{
"operation": "categories",
"shop": "079",
"topOnly": true,
"includeRaw": false
}
{
"operation": "category",
"shop": "079",
"categorySlug": "fruit-vegetables",
"page": 1,
"includeRaw": false
}
{
"operation": "item",
"shop": "079",
"itemSlug": "bananas-cavendish",
"includeRaw": false
}

Output

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

Notes

  • search uses the upstream Myfoodlink q parameter, not the older broken query parameter.
  • shop accepts a shop code like 079, a store name like Findon, a host prefix, or a full shop URL.
  • item payloads now include richer metadata such as category path, availability, currency, and store context.
  • topOnly=true keeps only first-level categories under All Departments.
  • Default proxy strategy is direct.
  • The runtime is prepared for future pay-per-event monetization.