HLJ Product Scraper

Turn HLJ searches into structured product records you can compare, monitor, or send to another workflow. Provide one or more search terms and receive a deduplicated dataset containing product names, prices, availability, catalog details, images, and direct HLJ links.

What you can do

• Compare USD and JPY prices across products returned by several searches.
• Track availability and release information for model kits, figures, hobby supplies, and other HLJ catalog items.
• Build product research, purchasing, catalog, or monitoring workflows from normalized dataset records.
• Export results from the default dataset in the formats supported by Apify.

Input

Run the Actor with an input such as:

{
  "searchQueries": ["Gundam", "Tamiya paint"],
  "maxItems": 100,
  "scrapeDetails": true,
  "proxyConfiguration": {"useApifyProxy": false}
}

• searchQueries is a required non-empty list of HLJ search terms.
• maxItems is the maximum number of unique products returned across all queries and pages. It defaults to 100.
• scrapeDetails controls whether individual product pages are visited for additional catalog fields. It defaults to true.
• proxyConfiguration optionally routes requests through your selected proxy. Direct requests are used by default.

The Actor follows search-result pagination until it reaches maxItems, finds no additional products, or runs out of pages. Products found by more than one query or page are returned once, based on their canonical product URL.

Output

Each product is stored as an item in the run's default dataset. name and url are always present. Other fields are included when HLJ supplies them:

{
  "name": "Example model kit",
  "url": "https://www.hlj.com/example-product",
  "price_usd": 24.99,
  "price_jpy": 3800,
  "maker": "Example maker",
  "category": "Plastic Models",
  "availability": "In stock",
  "release_date": "2026-09",
  "gtin": "1234567890123",
  "image": "https://www.hlj.com/media/example.jpg",
  "search_query": "Gundam"
}

Fields that are not available are omitted instead of being guessed. The normalized output fields are name, url, price_usd, price_jpy, maker, category, availability, release_date, gtin, image, and search_query.

Pricing and run behavior

This Actor uses pay-per-event billing. A start event is charged when a run starts, based on the run's memory allocation with a minimum of one event. One dataset-item event is charged for each product successfully stored in the default dataset. Products that are not stored are not charged; products already stored remain available and chargeable if a later request causes the run to fail or time out.

HLJ page structure and availability can change. If HLJ does not expose a field in its page HTML or structured product data, that field will not appear in the result. Detail-page requests are sequential to keep resource use and target-site load bounded.