List Wayfair categories API

Endpoint facts

Method

GET

API path

/wayfair/categories

Auth

apiKey

Credits

1 credit/request

Platform

Wayfair

Response schema

#/definitions/wayfair.categoriesResponseDoc

Overview

Returns a page of Wayfair categories discovered from Wayfair's own published sitemap, closing the discovery gap where a category id otherwise has to be found elsewhere. Pair a returned id with GET /wayfair/category to browse that category's product grid. name is derived from the category's own URL slug (title-cased), not an authoritative site-provided label. q, if set, case-insensitively filters to categories whose derived name or department contains it. 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

1 credit/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

- `name` is derived from the category's own URL slug (title-cased), not an authoritative site-provided label -- Wayfair's sitemap does not publish a display name. - `department` is the top-level storefront section the category sits under (e.g. `furniture`, `appliances`). - The full category list is refreshed periodically from Wayfair's sitemap rather than fetched fresh on every request; a brief staleness window (up to a day) is expected and does not affect correctness of ids returned. - `has_next` indicates whether a later page has more results. ```json {"code":200,"msg":"OK","data":{"total":1521,"page":1,"page_size":2,"has_next":true,"categories":[{"id":"1829184","name":"Kids Shower Curtains","department":"baby-kids","url":"https://www.wayfair.com/baby-kids/sb0/kids-shower-curtains-c1829184.html"},{"id":"1773657","name":"Bar Carts","department":"furniture","url":"https://www.wayfair.com/furniture/sb0/bar-carts-c1773657.html"}]}} ```

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