/chrono24/watches

POST /api/chrono24/watches

Price: 10 credits

Get full Chrono24 watch listing details by ID (or listing URL): brand, model, reference, price/currency, condition, year, movement, case, dial, bracelet, functions, images, seller and location.

How to use it

Fetch a single Chrono24 luxury watch listing by numeric ID or listing URL. Returns brand, collection, model, reference, price/currency, condition, production year, gender, movement, caliber, case (material/diameter/bezel/crystal), dial, bracelet (material/color/clasp), water resistance, functions, other attributes, scope of delivery, listing code, availability, location, images, a full spec details map and seller info. Use the domain field for the regional market and currency.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• domain string — Marketplace domain (controls language, currency and regional market). (default: "chrono24.com"; one of: "chrono24.com", "chrono24.co.uk", "chrono24.com.au", "chrono24.ca", "chrono24.in", "chrono24.co.id", "chrono24.my", "chrono24.co.nz", "chrono24.ph", "chrono24.sg", "chrono24.co.za", "chrono24.fi", "chrono24.co.th", "chrono24.ae", "chrono24.de", "chrono24.fr", "chrono24.it", "chrono24.es", "chrono24.nl", "chrono24.at", "chrono24.ch", "chrono24.se", "chrono24.pl", "chrono24.com.br", "chrono24.hk", "chrono24.jp", "chrono24.cn")
• watch string required — Watch listing ID (e.g. '47198017') or full listing URL (examples: "47198017", "https://www.chrono24.com/rolex/submariner-116610ln--id47198017.htm"; minLength: 1)

Response

• @type string (default: "Chrono24Watch")
• id string required
• url string required
• name string required
• brand string nullable
• collection string nullable
• model string nullable
• reference string nullable
• price number nullable
• currency string nullable
• is_negotiable boolean (default: false)
• condition string nullable
• condition_detail string nullable
• is_new boolean nullable
• year integer nullable
• gender string nullable
• movement string nullable
• caliber object nullable
  • @type string (default: "Chrono24Caliber")
  • jewels integer nullable
  • power_reserve string nullable
• case_material string nullable
• case_diameter string nullable
• bezel_material string nullable
• crystal string nullable
• band_material string nullable
• band_color string nullable
• clasp string nullable
• dial_color string nullable
• dial_numerals string nullable
• water_resistance string nullable
• functions array (default: [])
• other_attributes array (default: [])
• scope_of_delivery string nullable
• listing_code string nullable
• dealer_product_code string nullable
• availability string nullable
• location string nullable
• shipping_cost number nullable
• shipping_currency string nullable
• description string nullable
• images array (default: [])
• details object (default: {})
  • * string
• seller object nullable
  • @type string (default: "Chrono24WatchSeller")
  • name string nullable
  • alias string nullable
  • url string nullable
  • location string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Watch listing not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.