Chrono24 API endpoint
Use Crawlora's Chrono24 watch brands 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/brandsReturns Chrono24's full watch-brand index: every brand name and the slug identifying it, usable as the brand parameter on chrono24-models and chrono24-search. This is the discovery endpoint for that parameter, so every accepted value is obtainable from this API rather than by reading the website. 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 |
|---|---|---|---|---|---|
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/chrono24/brands" \ -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.
- `brands` lists every brand Chrono24 currently lists on its own brand index, deduplicated by slug. Brand count varies over time as Chrono24 adds or retires brands; treat `count` as informational rather than fixed. Example response: ```json { "code": 200, "msg": "OK", "data": { "brands": [ {"name": "Rolex", "slug": "rolex", "url": "https://www.chrono24.com/rolex/index.htm"}, {"name": "Omega", "slug": "omega", "url": "https://www.chrono24.com/omega/index.htm"}, {"name": "Patek Philippe", "slug": "patekphilippe", "url": "https://www.chrono24.com/patekphilippe/index.htm"} ], "count": 599 } } ```
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 |
|---|---|---|
| 500 | Internal Server Error | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"brands": [
{
"name": "Rolex",
"slug": "rolex",
"url": "https://www.chrono24.com/rolex/index.htm"
},
{
"name": "Omega",
"slug": "omega",
"url": "https://www.chrono24.com/omega/index.htm"
},
{
"name": "Patek Philippe",
"slug": "patekphilippe",
"url": "https://www.chrono24.com/patekphilippe/index.htm"
}
],
"count": 599
}
}Request schema
No body schema
Response schema
#/definitions/chrono24.brandsResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | chrono24.BrandsResponse | No | ||||
| data.brands | array | No | ||||
| data.brands[].name | string | No | ||||
| data.brands[].slug | string | No | ||||
| data.brands[].url | string | No | ||||
| data.count | integer | No | ||||
| 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/brands" \
-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