Home Depot Category API

Endpoint facts

Method

GET

API path

/homedepot/category

Auth

apiKey

Credits

3 credits/request

Platform

Home Depot

Response schema

#/definitions/homedepot.categoryResponseDoc

Overview

Returns one page of a Home Depot category or brand browse page's product grid: normalized products with title, image, model, current/original price, and rating/review count, plus the category's total result count and the refinement facets the page offers. path is the segment of a /b/ URL after "/b/", e.g. "Tools-Power-Tools-Drills-Impact-Drivers/N-5yc1vZc29x"; a full https://www.homedepot.com/b/... URL or a "/b/..." path is also accepted. sort selects the result ordering and is one of best_match, top_sellers, top_rated, price_low_to_high, price_high_to_low, most_popular, delivery_date; omit it to keep the site's default ordering. page is a 1-indexed page number (default 1, maximum 42), 24 products per page. Each returned facet's path is directly usable as this endpoint's own path parameter to drill down. An unrecognized or blocked path returns an upstream error rather than an empty result. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

3 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- `sort` and `page` are optional and additive. With both omitted the request and response are identical to what this endpoint returned before they existed, so existing callers are unaffected. - `total` is the category's total result count across all pages (from the page's own "Viewing 1-N of M" marker); `count` is how many products this response carries; `page` echoes the page returned. - `facets` are the refinement links the browse page offers, e.g. `Cordless` or `18v` under Impact Drivers. Each facet's `path` is directly usable as this endpoint's own `path` parameter, so a caller drills down by passing a facet's `path` back in. Facets are omitted when the page offers none. - `price` is the current price; `original_price` is present only when the product is on sale. - `rating` and `review_count` are parsed from the card's `(rating / reviews)` text; they are omitted for products that show no rating. - A `path` that would resolve to a URL Home Depot's `robots.txt` disallows (keyword-refined browse such as `Ntt-`/`Ntk-`, the `NCNI-5` search-context marker, or the AJAX/overlay fragments) is rejected with a `400` rather than fetched. Facets pointing at such URLs are likewise never returned. - Keyword search is not part of this endpoint — see `/api/v1/homedepot/search`. - An unrecognized or blocked `path` returns a `503` upstream error rather than an empty result. Example response: ```json {"code":200,"msg":"OK","data":{"path":"Tools-Power-Tools-Drills-Impact-Drivers/N-5yc1vZc29x","sort":"top_sellers","page":1,"title":"IMPACT DRIVERS","total":1962,"count":1,"products":[{"id":"320326875","title":"M18 FUEL 18V Lithium-Ion Brushless Cordless 1/4 in. Hex Impact Driver (Tool-Only)","url":"https://www.homedepot.com/p/Milwaukee-M18-FUEL-18V-Lithium-Ion-Brushless-Cordless-1-4-in-Hex-Impact-Driver-Tool-Only-2953-20/320326875","image":"https://images.thdstatic.com/productImages/fa7d2462-8481-4bd3-8010-384a85aa902f/svn/milwaukee-impact-drivers-2953-20-64_600.jpg","model":"2953-20","price":179,"rating":4.7,"review_count":1542}],"facets":[{"name":"Cordless","path":"Cordless/N-5yc1vZc29xZ1z140i3","url":"https://www.homedepot.com/b/Cordless/N-5yc1vZc29xZ1z140i3"}],"source_url":"https://www.homedepot.com/b/Tools-Power-Tools-Drills-Impact-Drivers/N-5yc1vZc29x?sortby=topsellers&sortorder=desc","fetched_at":"2026-09-05T00:00:00Z"}} ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related