Chrono24 API endpoint
Use Crawlora's Chrono24 search filter values API to extract supported public Chrono24 data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/chrono24/facetsFetches 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. 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.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| 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 | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/chrono24/facets?group=condition" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
- 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`): ```json { "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 } ] } } ```
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 500 | Internal Server Error | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.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 | Enum | Bounds | 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 |
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"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms