Get GOAT search facet values API

Endpoint facts

Method

GET

API path

/goat/search/facets

Auth

apiKey

Credits

1 credit/request

Platform

GOAT

Response schema

#/definitions/goat.facetsResponseDoc

Overview

Returns the accepted values for goat_search's filter parameters: categories, colors, genders, conditions, brands, and years are read live from GOAT's own search API so a value GOAT adds is discoverable without any client-side change, while product_types and activities are served from a maintained list because GOAT exposes no live facet for them. brands is GOAT's top brands ordered by product count, not the complete brand list -- when brands_truncated is true, brands beyond the ones listed exist and remain valid goat_search values. Credential-free public data. 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

- Every live field reflects GOAT's vocabulary at request time -- treat this as the source of truth over any list hardcoded in other documentation, which can drift as GOAT adds values. - `brands` is GOAT's **top** brands, not its complete brand list. Upstream truncates the brand facet, and `brands_truncated` is `true` when that limit was hit. A brand missing from this list is still a valid `brands` value on `GET /goat/search` -- long-tail brands (for example single-product artists under the `art` category) simply never reach the top of the facet. Do not reject a caller-supplied brand for being absent here. - `years` matches a product's **season** year, which is the field `GET /goat/search`'s `years` parameter filters on. It is a superset of the release years GOAT shows elsewhere. - `product_types` and `activities` are maintained in this API rather than read live, so they can lag a GOAT change; every other field cannot. Example response (brand and year lists truncated for brevity): ```json { "code": 200, "msg": "OK", "data": { "categories": ["footwear", "apparel", "accessories", "bags", "collectibles", "jewelry", "home", "media", "sports", "objects", "other", "art"], "colors": ["black", "white", "blue", "grey", "green", "red", "multi-color", "brown", "pink", "cream", "tan", "purple", "yellow", "orange", "silver", "gold", "teal", "copper"], "genders": ["men", "women", "youth", "infant"], "conditions": ["new_no_defects", "used", "new_with_defects", "goat_clean"], "product_types": ["sneakers", "sandals", "cleats", "boots", "slip-ons"], "activities": ["lifestyle", "basketball", "running", "skateboarding"], "brands": ["nike", "adidas", "new-balance", "puma", "supreme", "air-jordan"], "brands_truncated": true, "years": ["2023", "2024", "2022", "2025", "2021", "2020"] } } ```

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