Docs menu

Chrono24 API endpoint

Chrono24 search filter values API

Fetches every value Chrono24 accepts for one of chrono24-search's advanced-search filter params, each with its own live listing count: the discovery endpoint for condition, used_or_new, case_material, dial_color, bracelet_material, movement_type, gender, watch_type and stock_info.

GETapiKey3 credits/requestChrono24chrono24.facetsResponseDoc/chrono24/facets

Endpoint facts

Method: GET
API path: /chrono24/facets
Auth: apiKey
Credits: 3 credits/request
Charged on: Successful 2xx responses only
Platform: Chrono24
Response schema: #/definitions/chrono24.facetsResponseDoc

Chrono24 Scraper API Try Chrono24 search filter values API in Playground Chrono24 API documentation

How this endpoint behaves

Query parameters:

group (required) — which filter to list values for. One of: condition, usedOrNew, caseMaterial, dialColor, braceletMaterial, movementType, gender, watchType, stockInfo. This is Chrono24's own internal id for the filter; the response's param field names the matching chrono24-search query param.

Notable response behavior:

An unrecognized group returns 400 before any upstream request is made.
count on each value is Chrono24's own live listing count carrying that value, across all brands (not scoped to any one search).
The value space is cached up to 6 hours, since it changes rarely; a fresh chrono24-search call always applies filters against Chrono24's live inventory regardless of this cache.

Example response (group=caseMaterial):

{
  "code": 200,
  "msg": "OK",
  "data": {
    "group": "caseMaterial",
    "label": "Case material",
    "param": "case_material",
    "count": 20,
    "values": [
      { "label": "Steel", "value": "steel", "count": 412873 },
      { "label": "Yellow gold", "value": "yellow_gold", "count": 48213 },
      { "label": "White gold", "value": "white_gold", "count": 15942 },
      { "label": "Titanium", "value": "titanium", "count": 9021 }
    ]
  }
}

Live monitoring

Monitored request: GET /chrono24/facets?group=caseMaterial
Checks passed, 7 days to 14 Oct 2026: 100%
Median response time: 10.38 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /chrono24/facets?group=caseMaterial
Items in values: 20
Fields filled in every checked item: 3

Field	Filled in, of 20 checked	Values in the sample
label	20	“Aluminum” and 19 other values
value	20	0 to 21, median 10
count	20	114 to 382,978, median 4,550

Request parameters

Parameter	Type	Required	Default	Description	Example
group	string	Yes		Filter to list values for Allowed values: condition, usedOrNew, caseMaterial, dialColor, braceletMaterial, movementType, gender, watchType, stockInfo.	condition
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/chrono24/facets?group=condition" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "group": "caseMaterial",
    "label": "Case material",
    "param": "case_material",
    "count": 20,
    "values": [
      {
        "label": "Steel",
        "value": "steel",
        "count": 412873
      },
      {
        "label": "Yellow gold",
        "value": "yellow_gold",
        "count": 48213
      },
      {
        "label": "White gold",
        "value": "white_gold",
        "count": 15942
      },
      {
        "label": "Titanium",
        "value": "titanium",
        "count": 9021
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/chrono24.facetsResponseDoc

Field	Type	Required	Example	Description
code	integer	No	200
data	chrono24.FacetsResponse	No
data.count	integer	No
data.group	string	No		Group echoes the requested group id.
data.label	string	No		Label is Chrono24's own display name for this filter, e.g. "Case material".
data.param	string	No		Param is the Chrono24Search query param this group's values feed, e.g. "case_material".
data.values	array	No
data.values[].count	integer	No		Count is Chrono24's own live listing count carrying this value, across all brands (not scoped to any one search).
data.values[].label	string	No		Label is Chrono24's own human-readable label, e.g. "Steel".
data.values[].value	string	No		Value is exactly what Chrono24Search's matching param (FacetsResponse .Param) accepts for this value.
msg	string	No	OK

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
500	Internal Server Error	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/chrono24/facets?group=condition" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

More Chrono24 endpoint docs Chrono24 Scraper API Chrono24 search-box suggestions API documentation Chrono24 watch brands API documentation Chrono24 dealer storefront API documentation Chrono24 dealer buyer reviews API documentation Chrono24 watch listing detail API documentation Chrono24 models for a brand API documentation

Open in Playground Back to group

Docs menu

Chrono24 API endpoint

Chrono24 search filter values API

GETapiKey3 credits/requestChrono24chrono24.facetsResponseDoc/chrono24/facets

Endpoint facts

Method: GET
API path: /chrono24/facets
Auth: apiKey
Credits: 3 credits/request
Charged on: Successful 2xx responses only
Platform: Chrono24
Response schema: #/definitions/chrono24.facetsResponseDoc

Chrono24 Scraper API Try Chrono24 search filter values API in Playground Chrono24 API documentation

How this endpoint behaves

Query parameters:

group (required) — which filter to list values for. One of: condition, usedOrNew, caseMaterial, dialColor, braceletMaterial, movementType, gender, watchType, stockInfo. This is Chrono24's own internal id for the filter; the response's param field names the matching chrono24-search query param.

Notable response behavior:

An unrecognized group returns 400 before any upstream request is made.
count on each value is Chrono24's own live listing count carrying that value, across all brands (not scoped to any one search).
The value space is cached up to 6 hours, since it changes rarely; a fresh chrono24-search call always applies filters against Chrono24's live inventory regardless of this cache.

Example response (group=caseMaterial):

{
  "code": 200,
  "msg": "OK",
  "data": {
    "group": "caseMaterial",
    "label": "Case material",
    "param": "case_material",
    "count": 20,
    "values": [
      { "label": "Steel", "value": "steel", "count": 412873 },
      { "label": "Yellow gold", "value": "yellow_gold", "count": 48213 },
      { "label": "White gold", "value": "white_gold", "count": 15942 },
      { "label": "Titanium", "value": "titanium", "count": 9021 }
    ]
  }
}

Live monitoring

Monitored request: GET /chrono24/facets?group=caseMaterial
Checks passed, 7 days to 14 Oct 2026: 100%
Median response time: 10.38 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /chrono24/facets?group=caseMaterial
Items in values: 20
Fields filled in every checked item: 3

Field	Filled in, of 20 checked	Values in the sample
label	20	“Aluminum” and 19 other values
value	20	0 to 21, median 10
count	20	114 to 382,978, median 4,550

Request parameters

Parameter	Type	Required	Default	Description	Example
group	string	Yes		Filter to list values for Allowed values: condition, usedOrNew, caseMaterial, dialColor, braceletMaterial, movementType, gender, watchType, stockInfo.	condition
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/chrono24/facets?group=condition" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "group": "caseMaterial",
    "label": "Case material",
    "param": "case_material",
    "count": 20,
    "values": [
      {
        "label": "Steel",
        "value": "steel",
        "count": 412873
      },
      {
        "label": "Yellow gold",
        "value": "yellow_gold",
        "count": 48213
      },
      {
        "label": "White gold",
        "value": "white_gold",
        "count": 15942
      },
      {
        "label": "Titanium",
        "value": "titanium",
        "count": 9021
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/chrono24.facetsResponseDoc

Field	Type	Required	Example	Description
code	integer	No	200
data	chrono24.FacetsResponse	No
data.count	integer	No
data.group	string	No		Group echoes the requested group id.
data.label	string	No		Label is Chrono24's own display name for this filter, e.g. "Case material".
data.param	string	No		Param is the Chrono24Search query param this group's values feed, e.g. "case_material".
data.values	array	No
data.values[].count	integer	No		Count is Chrono24's own live listing count carrying this value, across all brands (not scoped to any one search).
data.values[].label	string	No		Label is Chrono24's own human-readable label, e.g. "Steel".
data.values[].value	string	No		Value is exactly what Chrono24Search's matching param (FacetsResponse .Param) accepts for this value.
msg	string	No	OK

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
500	Internal Server Error	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/chrono24/facets?group=condition" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

Open in Playground Back to group

Chrono24 search filter values API

Endpoint facts

How this endpoint behaves

Live monitoring

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related

Chrono24 search filter values API

Endpoint facts

How this endpoint behaves

Live monitoring

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related