# Vander Haag's Parts Scraper — Heavy Truck Parts Prices & Stock (`crawloop/vanderhaags-parts-scraper`) Actor

Scrape Vander Haag's heavy-truck parts and whole trucks: price, stock, yard, OEM part number, fitment, and donor VIN. Search, part-number lists, SKUs, monitoring, and a catalog export of the full inventory.

- **URL**: https://apify.com/crawloop/vanderhaags-parts-scraper.md
- **Developed by:** [Andrej Kiva](https://apify.com/crawloop) (community)
- **Categories:** E-commerce, Other
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 part listings

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Vander Haag's Parts Scraper

> **Disclaimer:** Unofficial tool — not affiliated with, sponsored by, or endorsed by Vander Haag's, Inc. or its affiliates. Data is read from publicly accessible search, part, and truck pages only. No login. You are responsible for complying with applicable law and the site’s terms. No warranty on accuracy or availability. Provided for informational and research use.

Scrape one US heavy-truck salvage dealer: used, new, rebuilt, and aftermarket parts, plus whole trucks. Rows include price, call-for-price, yard and quantity, OEM part number, fitment, donor VIN, and stock. The inventory is hundreds of thousands of items across about 600 part types and 12 yards. Catalog mode can export the whole inventory. Use it as a Vander Haag's scraper and API alternative from Python, Node.js, or MCP, and export the dataset as JSON.

The site serves US visitors, so the default proxy is Apify in the United States. If the site blocks a run, it fails with a clear BLOCKED message instead of returning an empty dataset.

Set memory to **2048 MB** for search. SKU-only runs still launch on the same build.

### Pricing

Pay per event. A tiny start fee applies to every run.

| Event | Price | What you get |
| :--- | :--- | :--- |
| `part-listing` | $1.00 per 1,000 rows | Part or truck rows from search or catalog |
| `part-details` | $3.00 per 1,000 rows | Full details: stock by store, fitment, part number, donor VIN, warranty, and all images |
| `monitor-change` | $3.00 per 1,000 rows | Monitor changes |

Examples: 10,000 catalog rows are about $10. 1,000 detail rows are about $3.

### When to use

- Price and stock for a list of OEM or cross-reference numbers.
- A filtered search (category, make, model, condition, yard) with up to 500 cards per page.
- Whole trucks, with optional parts from the donor unit.
- A scheduled watch for new rows, price changes, stock or quantity changes, and removals.
- A full catalogue export. By default it searches every homepage inventory type (500 cards per page, deduped by SKU). `catalogSource: sitemap` walks sitemap files instead. Set `maxItems`.

### Input

`maxItems: 0` means no limit. Example bodies for each mode are `INPUT.json` (search), `INPUT.details.json`, `INPUT.partNumbers.json`, `INPUT.urls.json`, `INPUT.trucks.json`, `INPUT.catalog.json`, `INPUT.monitor-query.json`, and `INPUT.monitor-skus.json`.

| Field | Role |
| :--- | :--- |
| `mode` | `search` (default), `details`, `partNumbers`, `urls`, `trucks`, `catalog` |
| `catalogSource` | `search` (default) or `sitemap`. Catalog search walks inventory types; sitemap fetches detail URLs |
| `catalogCategories` | Optional inventory-type slugs. Empty means every type in the homepage nav |
| `keywords` | Part number, cross-reference, or free text |
| `partNumbers` | One search each |
| `category`, `subcategory`, `inventoryType`, `manufacturer`, `model`, `itemCategory` | Search filters |
| `conditions` | `NEW`, `USED`, `REBUILT`, `FOR PARTS` |
| `stores` | Yard codes `CB`, `DA`, `DM`, `IN`, `KC`, `CO`, `LV`, `SF`, `SP`, `SL`, `SV`, `WM` |
| `sort` | `match`, `lowest-price`, `highest-price` |
| `startUrls` | Search, detail, or trucks URLs |
| `skus` | Detail pages for those inventory ids |
| `includeDetails` | Open the detail page after a card search |
| `includeStoreAvailability` | Yard and quantity on detail rows |
| `includeUnitParts` | Also list parts for the donor `vehicleId` |
| `maxItems` | `0` = no limit |
| `monitorMode`, `monitorStoreName`, `resetMonitorState` | Named key-value watch, one key per SKU |
| `proxyConfiguration` | Apify proxy, country US |
| `concurrency` | Parallel detail fetches, 1–10 |

```json
{
  "mode": "partNumbers",
  "partNumbers": ["Q43-6080-1-2-031C", "P4272"],
  "includeDetails": true,
  "maxItems": 20,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyCountry": "US" }
}
```

### Output

Missing values are null. `recordType` is `part` or `truck`. `$0.00` becomes `price: null` and `callForPrice: true`. A page titled Product Not Available is a removed row, not a parse failure.

| Field | Meaning |
| :--- | :--- |
| `sku`, `url`, `canonicalUrl` | Inventory id, SKU URL, and the filter canonical |
| `recordType`, `title` | `part` or `truck`, and the H1 |
| `partNumber`, `stockTag` | OEM / cross-reference, and the internal tag when it differs from the SKU |
| `condition`, `partSource` | NEW / USED / REBUILT / FOR PARTS, and used / new / aftermarket / rebuilt |
| `price`, `currency`, `callForPrice`, `inStock` | USD price, call-for-price flag, availability |
| `storeAvailability` | `{store, city, state, qty}` |
| `itemLocation`, `category`, `subcategory`, `inventoryType`, `manufacturer`, `model` | Yard line and taxonomy |
| `specs`, `fitment` | Spec table and Reference Info lines |
| `donorVin`, `donorVehicle`, `vehicleId` | Donor unit |
| `engine`, `transmission`, `gvw`, `mileage`, `hours` | Parsed from the spec table or the description |
| `description`, `warranty`, `images`, `similarItems` | Copy, warranty text, pix URLs, similar `{sku, title, price}` |
| `scrapedAt`, `monitorChange` | UTC time, and `new` / `price_changed` / `stock_changed` / `removed` |

```json
{
  "sku": "26068481",
  "url": "https://www.vanderhaags.com/detailview.php?part=26068481",
  "recordType": "part",
  "title": "1999-2010 Sterling L9513 1 Piece Steel Bumper - Used",
  "partNumber": null,
  "condition": "USED",
  "partSource": "used",
  "price": 725,
  "currency": "USD",
  "callForPrice": false,
  "inStock": true,
  "storeAvailability": [{ "store": "DM", "city": "Des Moines", "state": "IA", "qty": 1 }],
  "itemLocation": "Des Moines, IA",
  "manufacturer": "Sterling",
  "model": "L9513",
  "donorVin": "2FZHAZCV75AN80258",
  "vehicleId": "168804",
  "monitorChange": null
}
```

### Monitor

Use one named store per watch (`monitorStoreName`). Each SKU is its own key. Keep `sort` and the filters identical between runs.

**Query watch.** Leave `skus` empty and schedule the same search. The first run emits every row as `new` and stores the window. Later runs emit only `new`, `price_changed`, `stock_changed`, and `removed` (a SKU that left the window).

**SKU watch.** Pass `skus` and turn `monitorMode` on. Each run re-reads those detail pages and emits price, stock, or quantity changes, plus `removed` when the title is Product Not Available.

`resetMonitorState` clears that store’s window before the run.

### Modes

**search** — filters, 500 cards per page, card fields only.

**details** — the same search, then one detail page per SKU. `includeDetails` does this from the other search modes.

**partNumbers** — `keywordsearch` once per number.

**urls** — `startUrls` are detected (search, `detailview.php` by part or filter URL, `trucks.php`). `skus` go straight to detail pages.

**trucks** — `inventorytype=truck`, optional `itemCategory`. `includeUnitParts` follows `vehicleId` into that donor’s parts.

**catalog** — export the whole inventory (hundreds of thousands of items, about 600 part types, 12 yards). `catalogSource: search` (the default) loads inventory-type slugs from the homepage nav and pages each type at 500 cards. Rows are search cards unless `includeDetails` is on. `catalogCategories` limits the types. `catalogSource: sitemap` walks sitemap files, fetches detail pages at `concurrency`, and pushes each new SKU as soon as that page returns. Set `maxItems`.

### Use cases

- A broker checks a spreadsheet of OEM numbers and keeps the rows whose price or yard quantity changed.
- A yard compares Sterling bumper stock and fitment before calling a store.
- A reseller schedules a lowest-price Cummins watch and reads only `monitorChange` rows.

### Integration examples

#### Node.js

```javascript
import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor("crawloop/vanderhaags-parts-scraper").call({
  mode: "partNumbers",
  partNumbers: ["Q43-6080-1-2-031C"],
  includeDetails: true,
  maxItems: 20,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

#### Python

```python
import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("crawloop/vanderhaags-parts-scraper").call(run_input={
    "mode": "search",
    "keywords": "cummins",
    "conditions": ["USED"],
    "sort": "lowest-price",
    "maxItems": 20,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["sku"], item["price"], item["itemLocation"])
```

#### cURL

```bash
curl -X POST "https://api.apify.com/v2/acts/crawloop~vanderhaags-parts-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"urls","skus":["26068481"],"maxItems":1}'
```

### MCP and AI assistants

Use this Actor from AI tools via [Apify MCP](https://docs.apify.com/platform/integrations/mcp).
Connect your Apify account, then call this Actor by its name.

Example prompts:

- "Run vanderhaags-parts-scraper in partNumbers mode for these OEM numbers and return price, yard, and quantity as JSON."
- "Run vanderhaags-parts-scraper in trucks mode for tandem axle day cabs and summarize engine, transmission, mileage, and price."
- "Using the SKU monitor input, list only rows whose monitorChange is price_changed or removed."

### Related Actors

| Actor | Role |
| :--- | :--- |
| **Vander Haag's Parts Scraper** ◄── you are here | US heavy-truck parts and trucks: price, yard stock, fitment, donor VIN |
| [TruckPaper Scraper](https://apify.com/crawloop/truckpaper-scraper) | US commercial trucks and trailers for sale |
| [Truck1 Scraper](https://apify.com/crawloop/truck1-scraper) | European trucks and trailers |
| [Car-Part Scraper](https://apify.com/crawloop/car-part-scraper) | Used auto parts and recycler stock |
| [PartsHotlines Scraper](https://apify.com/crawloop/partshotlines-scraper) | Used auto parts on the Hotlines yard network |
| [LKQ Online Scraper](https://apify.com/crawloop/lkqonline-scraper) | Used OEM price, interchange, and yard |
| [Row52 Scraper](https://apify.com/crawloop/row52-scraper) | Junkyard donor cars: VIN, yard, row |
| [Pick-n-Pull Scraper](https://apify.com/crawloop/picknpull-scraper) | Self-service yard inventory: VIN, row |
| [RockAuto Scraper](https://apify.com/crawloop/rockauto-scraper) | US catalog price, core, and fitment |
| [CarParts.com Scraper](https://apify.com/crawloop/carparts-com-scraper) | US aftermarket price and catalog status |

### FAQ

**Why did the run fail instead of returning zero rows?**\
The site serves US visitors, so the default proxy is Apify in the United States. If the site blocks a run, it fails with a clear BLOCKED message instead of returning an empty dataset.

**Why is the price null?**\
The page showed `$0.00`. `callForPrice` is true.

**Does the sitemap list 643,748 products?**\
No. Those are filter URLs. Catalogue search walks inventory types instead, and dedupes by SKU. `catalogSource: sitemap` is still available when you want those detail URLs.

# Actor input Schema

## `mode` (type: `string`):

search = filter cards. details = same search plus a detail page per SKU. partNumbers = one keyword search per part or cross-reference. urls = startUrls and/or skus. trucks = whole units. catalog = every inventory type (search by default; sitemap is optional).

## `catalogSource` (type: `string`):

Used when mode is catalog. search enumerates Search-Results.php for each homepage inventory type (500 per page, datacenter token session). sitemap walks sitemap files and fetches each detail page.

## `catalogCategories` (type: `array`):

Inventory type slugs to walk in catalog search. Empty means every type from the homepage nav.

## `keywords` (type: `string`):

keywordsearch: part number, cross-reference, or free text.

## `partNumbers` (type: `array`):

Part or cross-reference numbers. partNumbers mode runs keywordsearch once per value.

## `category` (type: `string`):

Top-nav category slug, for example engine or hood-and-front-end.

## `subcategory` (type: `string`):

Subcategory slug, for example hood-and-front-end-bumper.

## `inventoryType` (type: `string`):

Part type or unit type slug: truck, trailer, parts-unit, equipment-units, engine-assembly, bumper-assembly-front, and so on. trucks mode forces truck.

## `manufacturer` (type: `string`):

Make slug, for example peterbilt, cummins, sterling.

## `model` (type: `string`):

Model slug, for example l9513.

## `itemCategory` (type: `string`):

itemcategory for trucks and equipment, for example Tractor, Tandem Axle Day Cab.

## `conditions` (type: `array`):

Sent as filters\[0]\[]. Leave empty for every condition.

## `stores` (type: `array`):

Store codes from the header menu. One search per yard. Empty means every yard.

## `sort` (type: `string`):

order= on the search page. Keep this stable for a query monitor.

## `startUrls` (type: `array`):

Search-Results, detailview (part= or a filter URL), or trucks.php. Detail URLs are fetched over HTTP. Search URLs need the WAF token.

## `skus` (type: `array`):

Inventory ids. Detail pages are fetched over HTTP with no WAF. With monitor mode on, this is the fixed SKU watch.

## `includeDetails` (type: `boolean`):

After a card search, open detailview.php for each SKU. details mode always does this.

## `includeStoreAvailability` (type: `boolean`):

On detail rows, fill storeAvailability from the quantity table.

## `includeUnitParts` (type: `boolean`):

For a truck (or any row with vehicleId), also search that donor unit. The parts search needs the WAF token.

## `maxItems` (type: `integer`):

Maximum rows to save. 0 means no limit.

## `monitorMode` (type: `boolean`):

Save one key-value record per SKU in monitorStoreName. A search rerun emits new, price_changed, stock_changed, and removed. A skus list re-checks those detail pages over HTTP.

## `monitorStoreName` (type: `string`):

Named key-value store. Each SKU is its own key. Use one name per watch.

## `resetMonitorState` (type: `boolean`):

Delete the saved window before this run. The run becomes a new baseline.

## `proxyConfiguration` (type: `object`):

US Apify proxy. Datacenter is the default. After 3 blocks the run switches to US residential.

## `concurrency` (type: `integer`):

Parallel detail fetches (1–10).

## Actor input object example

```json
{
  "mode": "search",
  "catalogSource": "search",
  "catalogCategories": [],
  "keywords": "",
  "partNumbers": [],
  "category": "",
  "subcategory": "",
  "inventoryType": "",
  "manufacturer": "",
  "model": "",
  "itemCategory": "",
  "conditions": [],
  "stores": [],
  "sort": "match",
  "startUrls": [],
  "skus": [],
  "includeDetails": false,
  "includeStoreAvailability": true,
  "includeUnitParts": false,
  "maxItems": 0,
  "monitorMode": false,
  "monitorStoreName": "vanderhaags-monitor",
  "resetMonitorState": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyCountry": "US"
  },
  "concurrency": 4
}
```

# Actor output Schema

## `results` (type: `string`):

Default dataset items.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("crawloop/vanderhaags-parts-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("crawloop/vanderhaags-parts-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call crawloop/vanderhaags-parts-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,crawloop/vanderhaags-parts-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/XTjpycKEEYe6mWcTg/builds/RrgkiaWDENexwW8rR/openapi.json