# Chrono24 Scraper — Watch Prices & Last Ask (`noahadler/chrono24-sold-comps`) Actor

Scrape Chrono24 search: listingId, title, last ask, currency, status (in stock, sold badge, or removed). Chrono24 watch prices for dealers — not a sold archive and not an invented hammer. Public HTML only. RESIDENTIAL DE.

- **URL**: https://apify.com/noahadler/chrono24-sold-comps.md
- **Developed by:** [Noah Adler](https://apify.com/noahadler) (community)
- **Categories:** E-commerce, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 watch listings

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Chrono24 Scraper — Watch Prices & Last Ask

**chrono24 scraper** for **chrono24.com**: live watch listings with `listingId`, title, brand, `lastPrice` (last ask) and `status`. Built for dealers who need **chrono24 prices**, not a fake sold archive.

> Chrono24 does not publish a sold archive. WristSignal-class tools use Reddit for that gap. Public search is **InStock ads with last ask**. This Actor returns those listings on Try it. If you paste a listing URL, it reports a sold badge or **removed**. Last ask is **not** an invented hammer (`priceKind=last_ask` unless the page shows a real sold price).

### Table of contents

- [What you get](#what-you-get)
- [How it works](#how-it-works)
- [Input](#input)
- [Output](#output)
- [Example input](#example-input)
- [Use cases](#use-cases)
- [Proxy](#proxy)
- [API quick start](#api-quick-start)
- [FAQ](#faq)
- [Limitations](#limitations)
- [Keywords](#keywords)

### What you get

**Watch listing (last ask)**

- `listingId`, `url` (chrono24.com)
- `title`, `brand`, `model` (from the listing title)
- `reference` when that number appears in the title (many Chrono24 titles omit it)
- `status`: `active` | `sold` | `removed`
- `lastPrice`, `soldPrice` (only when a public sold price exists), `priceKind` (`last_ask` or `sold_price`), `currency`
- `firstSeenAt`, `lastSeenAt`, `sellerId`, `scrapedAt`

This is **chrono24 scraper** / **chrono24 prices** output. It is not a Chrono24 sold archive.

### How it works

| Step | Action |
|------|--------|
| 1 | Open chrono24.com search / model page for your keyword (e.g. Rolex Submariner). |
| 2 | Read public JSON-LD offers (live InStock cards) and push last-ask rows when `includeActive` is on (default). |
| 3 | Optional: check `listingUrls` / `listingIds` / `watchItems`. |
| 4 | Open those listing pages. InStock = `active`. Sold badge or SoldOut JSON-LD = `sold`. Redirect to browse / gone = `removed`. |

There is no public `showSold=true` filter (query params are ignored). Seller Price analysis is login-only — this Actor does not scrape that wall.

### Input

| Field | Required | Default | Notes |
|-------|----------|---------|-------|
| `keyword` | One of keyword / URL / IDs | Rolex Submariner | Brand + model as on Chrono24 |
| `searchUrl` | One of keyword / URL / IDs | — | Full search or model URL |
| `listingUrls` | One of keyword / URL / IDs | — | Listing URLs a dealer would paste |
| `listingIds` | One of keyword / URL / IDs | — | Numeric IDs of **real** listings — not probe dummies |
| `watchItems` | No | — | Last-known cards (`listingId`, `title`, `lastPrice`, …) |
| `maxItems` | No | 20 | 1–80 |
| `lookbackHours` | No | 168 | Keep IDs between scheduled runs |
| `includeActive` | No | **true** | On = last-ask listings (Try it). Off = sold-badge / removed only |
| `proxyConfiguration` | No | RESIDENTIAL + DE | Keep DE (or your market) aligned |

### Output

One row per listing. A hard block pushes one row with `error: true` and a message that names RESIDENTIAL + DE.

```json
{
  "listingId": "12345678",
  "url": "https://www.chrono24.com/rolex/rolex-submariner--id12345678.htm",
  "title": "Rolex Submariner Date",
  "brand": "Rolex",
  "status": "active",
  "lastPrice": 12500.0,
  "soldPrice": null,
  "priceKind": "last_ask",
  "currency": "USD",
  "scrapedAt": "2026-09-25T00:00:00Z"
}
```

`priceKind=last_ask` means the number is the last public asking price, not a Chrono24 hammer. `soldPrice` is filled only when the public page shows a sold price.

### Example input

```json
{
  "keyword": "Rolex Submariner",
  "maxItems": 15,
  "includeActive": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "DE"
  }
}
```

### Use cases

- Grey-market dealers pricing a Rolex Submariner from **chrono24 prices** (last ask)
- Catalog / lead lists from Chrono24 search
- Closed-sale checks on listing URLs you already track (sold badge or removed)

### Proxy

Chrono24 can challenge datacenter IPs. Default is **Apify RESIDENTIAL**, country **DE**. If you search a local chrono24.\* market, set the proxy country to that market.

### API quick start

```bash
apify call noahadler/chrono24-sold-comps --input '{
  "keyword": "Rolex Submariner",
  "maxItems": 15,
  "includeActive": true
}'
```

### FAQ

**Why is there no sold archive?**\
Chrono24 does not publish one. This Actor returns last-ask listings. Sold/removed is only a status on a specific listing URL.

**Is soldPrice the hammer?**\
Only if `priceKind=sold_price` (rare on public HTML). Otherwise use `lastPrice`.

**Can I hide live listings?**\
Set `includeActive` to false. Then you only get sold-badge / removed rows (often empty on a first run).

### Limitations

- No public Chrono24 sold archive
- Seller-only Price analysis / login wall is **not** scraped (honest error; no WAF rewrite loop)
- Disappeared listing = `removed` (sold or withdrawn). `sold` only with a public sold badge / SoldOut JSON-LD
- Do not invent hammer prices
- Do not pass dummy listing IDs (`1000`, `10000`) — Try it uses keyword search

### Keywords

`chrono24 scraper` · `chrono24 prices` · `chrono24 watches` · `rolex chrono24` · `chrono24 last ask`

# Actor input Schema

## `keyword` (type: `string`):

What a dealer types on Chrono24 (e.g. Rolex Submariner). Builds the watched universe. Required unless you pass searchUrl, listingIds, listingUrls or watchItems.

## `searchUrl` (type: `string`):

Optional chrono24.com / .de search or model URL. Overrides the keyword URL when set.

## `listingUrls` (type: `array`):

Chrono24 listing URLs a dealer would paste (…--id123.htm). Checked now for sold badge, last ask, or removed.

## `listingIds` (type: `array`):

Numeric Chrono24 listing IDs (or URLs). Same as listingUrls.

## `watchItems` (type: `array`):

Last-known cards from a previous run: listingId, title, brand, lastPrice, url. Used when you paste last run output instead of Actor storage.

## `maxItems` (type: `integer`):

Maximum sold/removed rows to save, and size of the watched search universe (1–80).

## `lookbackHours` (type: `integer`):

How long to keep IDs in the watched universe between scheduled runs (1–720). Typical: 168 (7 days).

## `includeActive` (type: `boolean`):

On by default so Try it returns live last-ask listings. Turn off only for scheduled runs that should emit sold-badge / removed rows.

## `proxyConfiguration` (type: `object`):

Default: Apify RESIDENTIAL, country DE (Chrono24). Keep RESIDENTIAL on if you see a challenge.

## Actor input object example

```json
{
  "keyword": "Rolex Submariner",
  "maxItems": 20,
  "lookbackHours": 168,
  "includeActive": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "DE"
  }
}
```

# Actor output Schema

## `comps` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keyword": "Rolex Submariner"
};

// Run the Actor and wait for it to finish
const run = await client.actor("noahadler/chrono24-sold-comps").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "keyword": "Rolex Submariner" }

# Run the Actor and wait for it to finish
run = client.actor("noahadler/chrono24-sold-comps").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keyword": "Rolex Submariner"
}' |
apify call noahadler/chrono24-sold-comps --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,noahadler/chrono24-sold-comps"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/VlAug90USmcRcp8Ru/builds/2PoXW5WFUXvbsqOya/openapi.json