Skip to content

Chrono24 Scraper API

Chrono24 is a global marketplace for new and pre-owned luxury watches.

OUTPUT FORMATSHTMLJSONMarkdown

Its listings carry the signals watch traders, resellers and market analysts care about: reference numbers, asking prices, availability, seller reputation and shipping terms. Collecting those signals by hand does not scale, and building your own browser fleet around bot detection, CAPTCHAs and layout changes is a maintenance project in itself. This API returns rendered HTML or structured output from Chrono24 pages so your team can spend its time on analysis instead of infrastructure.

What you can collect from Chrono24

The scraper is aimed at the data that drives watch-market decisions. Typical targets include:

  • Listings and specifications — model names, reference numbers, condition, year and included accessories.
  • Prices — asking prices per listing, useful for competitor benchmarking and trend tracking.
  • Availability — whether a watch is in stock, reserved or sold, and how that shifts over time.
  • Seller information — dealer or private-seller details shown on the listing.
  • Delivery and shipping costs — stated delivery times and shipping fees, which matter when comparing landed prices across regions.

Because Chrono24 pages are JavaScript-heavy and change structure periodically, the API renders pages in a real browser environment before returning them. You can then parse the HTML yourself, apply CSS or XPath extraction rules, or ask the AI extraction feature to return specific fields in natural language.

How the workflow runs

  1. Create an account. Signing up provides an API key; any starter credit allowance, trial length or usage cap is set by the account terms in force at the time you register, so check those terms before planning a test run. A sensible first step is a small pilot: pick a handful of Chrono24 listing URLs, record the fields you need, and confirm the returned pages contain them before scaling up. If you want a concrete worksheet, note for each pilot URL the reference number, asking price, availability status, seller type and stated shipping cost, then compare what the API returns against what you see in a browser — that gap tells you whether you need rendering, extraction rules or a different output mode. Any free-credit offer, its size and its expiry are commercial terms to confirm with the provider rather than assumptions to build a budget on. 2. Add the client library. The official Python library lets you send scraping requests without configuring proxies or browsers yourself. 3. Send a Chrono24 URL. The API fetches the page, handles rendering and anti-bot measures, and returns ready-to-parse HTML. 4. Shape the output. Use extraction rules, AI extraction, Markdown output or screenshots depending on what your pipeline needs. For teams that prefer no-code, the Zapier integration can turn extraction rules into structured JSON inside an automated workflow.

Choosing the right output for your task

The API supports several output modes, and the right one depends on how stable your target fields are.

GoalRecommended modeWhy
Full control over parsingRendered HTMLYou write and own the parser; useful when you already have a scraping stack.
Fixed, well-understood fieldsCSS/XPath extraction rulesReturns JSON with only the fields you specify; predictable and cheap to process.
Fields that shift or are described in plain languageAI extractionAsk for the data you want in natural language and get results back without writing selectors.
Content for LLM or text pipelinesMarkdown or plain textStrips page chrome and returns readable text.
Visual verification or archivingScreenshotsCaptures full or partial page visuals, including pages that block simple requests.

A practical pattern is to start with AI extraction while you learn the page structure, then move stable fields to CSS/XPath rules to reduce cost and variability.

Two different failures, two different fixes

When a Chrono24 request fails, the cause is usually one of two things, and they need different responses.

Blocking. The request was refused or served a CAPTCHA because the site identified it as automated traffic. Symptoms include 403 responses, challenge pages and empty bodies. The fix is proxy rotation and browser-like rendering, which the API applies by default. If you are building your own stack, this is where most engineering time disappears.

Rendering. The request succeeded, but the data you expected is missing because it is injected by JavaScript after the initial HTML loads. Symptoms include a 200 response with a shell page and no listing content. The fix is enabling JavaScript rendering and, where needed, a JavaScript scenario that waits for or interacts with the page before capture.

Separating these two cases early saves hours: check whether you received a block page or a rendered-but-incomplete page before changing your extraction rules.

Credits, plans and what each request costs

Requests are metered in API credits. A standard request starts at one credit, and optional features add to that cost. The pricing table below lists every plan with its monthly price, included credits and concurrency. Prices are shown exclusive of VAT.

Credit costs per successful request, as published with the plans:

  • Base request: 1 credit.
  • JavaScript rendering enabled: 5 credits.
  • Premium proxies without JavaScript rendering: 10 credits.
  • Premium proxies with JavaScript rendering: 25 credits.

Credits are valid for one month and do not roll over. Concurrency is the number of requests that can be in flight at the same time.

Worked example. Suppose you run 2,000 Chrono24 listing requests in a month, all with JavaScript rendering and premium proxies. At 25 credits each, that is 50,000 credits — comfortably inside the Hobby plan's 75,000 credits, provided your concurrency needs stay at or below 25. If you drop premium proxies and keep JavaScript rendering, the same workload costs 10,000 credits. The choice between proxy tiers is therefore the single biggest lever on cost for this kind of crawl.

Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.

Plan comparison

The table below reproduces the published plan details. All figures are monthly and exclusive of VAT.

Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.

Responsible use

Scraping any site means respecting its terms of service and robots.txt, and keeping request rates reasonable. Chrono24 does not publish an official public API, so any programmatic access should be reviewed against its current policies before you build a production pipeline. The service does not collect or store personal data from scraped sites unless you explicitly request it. A practical compliance checklist for a Chrono24 pipeline: read the marketplace's current terms and robots.txt before the first request; decide in advance which fields you actually need and exclude personal data such as individual seller names or contact details unless you have a lawful basis; set a request rate and a retry ceiling so a failing crawl cannot hammer the site; keep a log of what you collected, when and why, so the purpose is auditable; and re-check the terms whenever you change scope, region or volume. Whether a given use is permitted depends on the site's terms, your jurisdiction and your purpose, so treat this as an evaluation framework rather than legal advice and take qualified counsel where the stakes are high.

Chrono24 scraper API plans (monthly, exclusive of VAT)
PlanPriceAPI creditsConcurrent requestsJS renderingRotating & premium proxiesGeotargetingScreenshots & extraction rulesPriority email supportDedicated account managerTeam management
Hobby$19 /mo75,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49 /mo250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

Prices and credit allowances are the published plan details and are exclusive of VAT. Credits are valid for one month and do not roll over. Check current pricing before purchasing.

Frequently asked questions

What is Chrono24?

Chrono24 is an online marketplace for buying and selling luxury watches, connecting buyers and sellers worldwide. It lists both new and pre-owned watches and provides search filters and seller reviews to help collectors and enthusiasts find specific timepieces.

What is Chrono24 scraping?

Chrono24 scraping is the automated collection of data from Chrono24 pages — listings, prices, specifications and seller details. Because the site uses JavaScript rendering and anti-scraping measures, a scraping API handles the browser and proxy work so your code can focus on parsing and analysis.

Is scraping Chrono24 legal?

Legality depends on how you scrape and where you operate. You should respect Chrono24's terms of service and robots.txt, keep request rates reasonable, and avoid collecting personal data without a lawful basis. Review the current terms and your local regulations before building a production pipeline.

What data can I extract from Chrono24?

Common targets include watch listings, prices, seller information, product specifications, delivery times and shipping costs. Which fields are available depends on the page layout at the time you scrape.

Can I set custom extraction rules when scraping Chrono24?

Yes. You can supply extraction rules in JSON to specify exactly which fields to return — product names, prices, availability and so on — using CSS or XPath selectors. The documentation covers the parameters and selector syntax.

Does Chrono24 have an official API?

Chrono24 does not provide an official public API. If you need programmatic access to its data, a scraping API can handle the rendering and anti-bot complexity, provided your use complies with Chrono24's terms of service.

How much does a Chrono24 request cost in credits?

A base request costs 1 credit. Enabling JavaScript rendering raises it to 5 credits per successful request. Premium proxies cost 10 credits without JavaScript rendering or 25 credits with it. Credits are valid for one month and do not roll over. To budget a crawl, multiply the number of successful requests by the per-request credit cost of the features you enable, then compare the total with the credit allowance on each plan and with the concurrency limit, since concurrency caps how many requests can be in flight at once. Worked example: 2,000 requests with JavaScript rendering and premium proxies at 25 credits each come to 50,000 credits; the same 2,000 requests with JavaScript rendering but no premium proxies come to 10,000 credits. Confirm current per-request costs, credit validity and plan allowances before committing to a volume.

What happens if a Chrono24 page returns incomplete data?

Incomplete data usually means the page was rendered but the content you wanted is injected later by JavaScript. Enable JavaScript rendering and, if needed, a JavaScript scenario that waits for the element before capture. A block page or CAPTCHA instead points to a proxy or anti-bot issue.