Chrono24 API endpoint
Use Crawlora's Chrono24 search-box suggestions 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/autocompleteFetches Chrono24's own search-box typeahead suggestions for a partial query: each suggested phrase with its own live result count, plus the Chrono24 search URL it resolves to. Useful for building a search box against chrono24-search without guessing a full query. 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 |
|---|---|---|---|---|---|
| query | string | Yes | Partial search text, e.g. \ | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/chrono24/autocomplete?query=coffee" \ -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 empty or whitespace-only `query` returns `400` before any upstream request is made. - Suggestions come with no results for a query Chrono24's own index has nothing to suggest for -- an empty `suggestions` array, not an error. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "submar", "suggestions": [ { "label": "Rolex Submariner", "result_count": 12428, "url": "https://www.chrono24.com/search/index.htm?dosearch=true&query=Rolex+submariner" }, { "label": "Rolex Submariner Date", "result_count": 6365, "url": "https://www.chrono24.com/search/index.htm?dosearch=true&query=Rolex+submariner+date" }, { "label": "Tudor Submariner", "result_count": 417, "url": "https://www.chrono24.com/search/index.htm?dosearch=true&query=Tudor+submariner" } ] } } ```
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": {
"query": "submar",
"suggestions": [
{
"label": "Rolex Submariner",
"result_count": 12428,
"url": "https://www.chrono24.com/search/index.htm?dosearch=true&query=Rolex+submariner"
},
{
"label": "Rolex Submariner Date",
"result_count": 6365,
"url": "https://www.chrono24.com/search/index.htm?dosearch=true&query=Rolex+submariner+date"
},
{
"label": "Tudor Submariner",
"result_count": 417,
"url": "https://www.chrono24.com/search/index.htm?dosearch=true&query=Tudor+submariner"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/chrono24.autocompleteResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | chrono24.AutocompleteResponse | No | ||||
| data.query | string | No | ||||
| data.suggestions | array | No | ||||
| data.suggestions[].label | string | No | Label is the suggested search phrase, e.g. "Rolex Submariner Date". | |||
| data.suggestions[].result_count | integer | No | ResultCount is Chrono24's own live result count for this suggestion. | |||
| data.suggestions[].url | string | No | URL is the Chrono24 search URL this suggestion resolves to, usable as-is or by passing its `query` value to Chrono24Search. | |||
| 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/autocomplete?query=coffee" \
-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