Product research
Use Home Depot endpoints to turn product research into repeatable API requests with documented inputs and JSON responses.
Build home-improvement catalog, pricing, product research, and department-browse workflows from normalized Home Depot data.
Collect public Home Depot product, category, department, keyword-search, and product-question data as structured JSON through documented endpoints.
Endpoint families
4
Documented params
10
Examples
0
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
9
Schema refs
5
{
"platform": "Home Depot",
"endpoint": "homedepot-product",
"method": "GET",
"path": "/homedepot/product/{id}",
"auth": "apiKey"
}Use cases
Collect public Home Depot product, category, department, keyword-search, and product-question data as structured JSON through documented endpoints.
Use Home Depot endpoints to turn product research into repeatable API requests with documented inputs and JSON responses.
Use Home Depot endpoints to turn catalog and price monitoring into repeatable API requests with documented inputs and JSON responses.
Use Home Depot endpoints to turn home-improvement market research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/homedepot/product/{id}
/homedepot/categories
/homedepot/category
/homedepot/search
Endpoint catalog
/homedepot/product/{id}Returns one Home Depot product's full detail: name, description, brand, model, store SKU, GTIN, price, images, aggregate rating and review count, and the featured customer reviews embedded on the product page. id is the numeric product/internet id (the trailing number of a /p/{slug}/{id} URL). The product page does not distinguish an unknown id from a known one in a consistent way, so an unrecognized id may return an upstream error rather than a not-found.
/homedepot/searchReturns one page (up to 24 products) of a Home Depot keyword search's product listing: normalized products with title, image, model, current/original price, and rating/review count, plus the search's total result count. q is free-text search keywords, e.g. "impact driver". page is a 1-indexed page number (default 1). An unrecognized/blocked query returns an upstream error rather than an empty result.
/homedepot/categoryReturns one Home Depot category or brand browse page's product grid (page 1 only): normalized products with title, image, model, current/original price, and rating/review count, plus the category's total result count. 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. An unrecognized or blocked path returns an upstream error rather than an empty result.
/homedepot/categoriesReturns Home Depot's top-level department taxonomy (name, path, url) from the homepage's own "All Departments" navigation. Each department's path is directly usable as GET /homedepot/category's path parameter.
/homedepot/product/{id}/questionsReturns the first page (8 questions) of a Home Depot product's customer questions and answers, plus the product's total Q&A count. id is the numeric product/internet id. A product with no Q&A returns a genuine zero-result response rather than an error.
Related APIs
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.