# Home Depot Product Scraper (`usestring/homedepot-products`) Actor

Reads Home Depot product data by item ID or product URL: numeric price, was-price, brand, model number, unrounded star rating, review count and a derived availability status. Pass a store number and both the price and the stock come back for that store instead of the national default.

- **URL**: https://apify.com/usestring/homedepot-products.md
- **Developed by:** [String](https://apify.com/usestring) (community)
- **Categories:** E-commerce, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.75 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Home Depot Product Scraper — price, stock and ratings, per store

This Actor scrapes Home Depot product data by item ID or product URL and returns one row per item: a
**numeric** `price`, plus `wasPrice`, `brand`, `modelNumber`, `rating`, `reviewCount` and a derived
`availability`. Set the optional `storeId` and the Home Depot Product Scraper returns **that store's
local price and stock** instead of the national default.

No Home Depot account, API key or cookies are used — this reads what a logged-out visitor's own
browser is served. One row per item, about 3.5 seconds per item at the measured median.

### What it returns

| Field | Type | Notes |
| --- | --- | --- |
| `itemId` | string | Home Depot's item ID — stable, use it to join or de-duplicate |
| `title` | string | The product label |
| `brand` | string | The manufacturer name |
| `modelNumber` | string | The manufacturer's model number |
| `price` | number | `249`, not `"$249.00"` |
| `priceText` | string | The same price formatted, e.g. `$249.00` |
| `wasPrice` | number | The list price, and only while it is genuinely higher than `price` |
| `currency` | string | `USD` |
| `rating` | number | Average stars out of 5, unrounded — `4.8235`, not `5` |
| `reviewCount` | number | Exact review count |
| `availability` | string | One of `IN_STOCK`, `LIMITED_STOCK`, `OUT_OF_STOCK`, `BACKORDERED`, `AVAILABLE`, `UNAVAILABLE`, `DISCONTINUED` |
| `imageUrl` | string | The primary image at the largest size Home Depot offers |
| `sourceUrl` | string | Home Depot's canonical product URL |
| `collectedAt` | string | Collection timestamp on every row |

**`AVAILABLE` is not a stock check.** It means the item is buyable but Home Depot reported no
location inventory — which is what an online-only item returns, and what any item returns on a run
with no `storeId`. `IN_STOCK` and `LIMITED_STOCK` are only reported when a location actually says so.

### Input

```json
{
  "products": ["313588232", "314030291"],
  "storeId": "0121",
  "maxItems": 1000
}
```

| Field | Description |
| --- | --- |
| `products` | Home Depot item IDs or full homedepot.com product URLs. Required, 1–300. |
| `storeId` | Optional numeric store number. Returns that store's local price and stock. |
| `maxItems` | Cap on dataset items. Default 1000. Free plans stop at 250 requests and 250 results — see below. |
| `concurrency` | Items fetched in parallel. Default 2, maximum 5. |

**A Home Depot item is addressed by the number at the end of its product URL** —
in `https://www.homedepot.com/p/<product-name>/313588232` the item is `313588232`. The bare ID and
the full URL resolve to the same item and are fetched once, so a mixed list is never billed twice.
A URL on any other host is rejected before it costs a fetch and is reported under `failures`.

### How it reads the page

Home Depot's storefront is a client-rendered shell, so its product page HTML carries no price and no
inventory to parse. The Home Depot Product Scraper calls the same `federation-gateway` GraphQL
endpoint the site itself calls, requesting only the fields in the dataset above. That is why `price`,
`wasPrice`, `rating` and `reviewCount` come back as numbers rather than display strings, and why one
item costs a single small response instead of a half-megabyte page.

### Use cases

- Price monitoring across a catalogue of Home Depot SKUs
- Local price and stock comparison for the same item across store numbers
- Availability checks before sourcing or fulfilment
- Enriching a building-products feed with brand, model number and ratings
- Feeding a competitive-pricing dashboard on a schedule

### Frequently asked questions

**Do I need a Home Depot account or API key to scrape Home Depot prices?** No. The Home Depot Product
Scraper uses no account, no cookies and no API key.

**What is a Home Depot item ID?** The number at the end of a `homedepot.com/p/…` product URL, for
example `313588232`. Pass it bare or pass the whole product URL — both work.

**Can I get the price and stock for one specific store?** Yes. Set `storeId` to the numeric store
number and both `price` and `availability` are resolved for that store. Without it, you get the
national price and no location inventory.

**Is the rating rounded?** No. `rating` is Home Depot's own unrounded average, e.g. `4.8235`, and
`reviewCount` is the exact total.

**How many rows does one item produce?** One. The Home Depot Product Scraper makes one request per
item and emits one row from it.

**What happens to an item ID that does not exist?** That target is recorded under `failures` in the
run's `SUMMARY` key, with Home Depot's own error message where it gives one, and the rest of the
batch still returns.

### Limitations

Product data on homedepot.com (US) only. This Actor does not return review text, specification
tables, variants or collections, shipping quotes, or a store locator, and it does not search or crawl
categories — you supply the items. Values reflect what Home Depot returned at collection time,
stamped in `collectedAt`.

### Free plan limit

Runs started from an Apify **free plan** stop at **250 requests and 250 results**, and the run
reports that it reached the limit. Any paid plan runs the full input and `maxItems` you set.

The limit exists because this Actor fetches through our own infrastructure, which Apify does not
cover for free-plan runs. It binds on requests as well as results so that a large input list cannot
spend those fetches for rows the run will not return.

# Actor input Schema

## `products` (type: `array`):

Home Depot store SKUs or full product URLs.

## `storeId` (type: `string`):

Optional store number for local pricing and stock.

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

Global cap on dataset items. Runs started from an Apify free plan stop at 250 requests and 250 results; any paid plan runs the full amount.

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

Targets fetched in parallel.

## Actor input object example

```json
{
  "products": [
    "320243591"
  ],
  "maxItems": 1000,
  "concurrency": 2
}
```

# Actor output Schema

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

Collect Home Depot product detail by item ID or URL - price, stock and ratings, with optional per-store pricing.

## `summary` (type: `string`):

Item count, failure count and every target that failed, with its error.

# 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 = {
    "products": [
        "320243591"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("usestring/homedepot-products").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 = { "products": ["320243591"] }

# Run the Actor and wait for it to finish
run = client.actor("usestring/homedepot-products").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 '{
  "products": [
    "320243591"
  ]
}' |
apify call usestring/homedepot-products --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,usestring/homedepot-products"
        }
    }
}

```

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/gPwIR9nHFfg4nNqWC/builds/PkxbdtvDFQxFxqwKZ/openapi.json