Otomoto Change Intelligence — Price Drop & Inventory Monitor

Stop comparing the same OTOMOTO search by hand. Track public used-car listings, asking-price changes, newly visible offers, and listings that leave your monitored result window. Export structured events to a spreadsheet, webhook, database, or AI agent.

Start in one click with a preconfigured use case: BMW 3 Series price drops, Audi A4 competitor price monitoring, or Skoda Octavia new offers.

This Actor is for recurring change monitoring, not just another one-off bulk scraper. Your first successful run establishes a baseline; later runs emit meaningful deltas. Listings outside a bounded result window are not necessarily sold or deleted.

What you get

For every monitored search, the Actor keeps a persistent snapshot and emits structured events:

• NEW_LISTING — a listing appeared since the previous run.
• PRICE_CHANGE — price or currency changed, with absolute and percentage delta.
• REMOVED_LISTING — a listing disappeared from the monitored result set.
• BASELINE_CREATED — the first successful run created the baseline.

Each listing contains a stable OTOMOTO ID, URL, title, price, currency, year, mileage, fuel type, and gearbox when present on the public result card.

Best use cases

• Dealer inventory monitoring.
• Price-drop alerts for a saved OTOMOTO search.
• Sourcing newly listed vehicles before a manual review.
• Competitive inventory monitoring.
• Daily or hourly market-segment snapshots.
• Feeding change events into Make, Zapier, n8n, webhooks, Sheets, databases, or agents.

Quick start

Use any public OTOMOTO search/category URL:

{
  "searchUrl": "https://www.otomoto.pl/osobowe/bmw/seria-3",
  "maxItems": 100,
  "maxPages": 4,
  "snapshotKey": "bmw-3-series",
  "includeCurrentSnapshot": true
}

First run

The first run stores a baseline. It emits BASELINE_CREATED, not hundreds of fake "new" events. With includeCurrentSnapshot=true, the dataset also contains CURRENT_LISTING rows, so users immediately see the current inventory while preparing for later price-change comparisons.

Later runs

Run the same input again — ideally on an Apify Schedule. The Actor compares the current public result set with the persistent baseline and emits only actual changes.

Pricing

Pay per event, with platform usage included in event pricing.

• Source scan: $0.01 per successfully fetched and parsed OTOMOTO result page.
• Detected listing change: $0.001 for each new, removed, or price-changed listing.
• A tiny Actor-start and default dataset-item charge may also apply as displayed by Apify.

The Actor respects the run's maximum charge. It stops cleanly when the event budget is exhausted.

Cost control

Use maxItems and maxPages as hard limits.

For a narrow saved search, start with:

{
  "maxItems": 100,
  "maxPages": 4
}

A typical OTOMOTO result page contains dozens of cards, so change monitoring does not require fetching individual detail pages.

Input

searchUrl

Public OTOMOTO category or filtered search URL. Individual listing pages are intentionally rejected.

snapshotKey

Optional stable identifier for the monitored search. Reuse the same value across scheduled runs.

maxItems

Maximum listings retained in the current snapshot.

maxPages

Maximum public search-result pages fetched in one run.

requestDelaySeconds

Delay between result-page requests. Minimum is 0.5 seconds.

includeCurrentSnapshot

When enabled, current listing rows are also written to the default dataset. Leave disabled when you only need changes.

Reliability and safety

• Public search/category pages only.
• No login or OTOMOTO account required.
• No CAPTCHA bypass.
• No residential-proxy requirement in the current adapter.
• No hidden/private endpoints.
• The Actor fails loudly if the result-card structure disappears instead of silently returning an empty dataset.
• Snapshots are committed only after a successful scan, so a failed run does not overwrite the previous baseline.
• Watch history is partitioned by the authenticated Apify user, public search URL and snapshot key. Different users cannot share a comparison baseline even when they choose identical task names.
• October 2026 baseline migration: the new isolated storage keys intentionally do not reuse older, unpartitioned comparison records. The first run after this update establishes a fresh baseline; subsequent runs resume normal price-change detection. No legacy data is copied across accounts.
• REMOVED_LISTING means an offer left the currently configured, bounded search result window. It does not prove the vehicle sold, was removed from OTOMOTO, or became unavailable.
• The Actor stores no private seller contact details; search URLs and results must be publicly accessible.
• Output tab includes both the default dataset link and a machine-readable OUTPUT run summary for APIs and agent workflows.

Recommended workflow

1. Build the OTOMOTO filters you care about in your browser.
2. Copy the resulting public search URL.
3. Run once to create the baseline.
4. Create an Apify Schedule with the same snapshotKey.
5. Consume only NEW_LISTING, PRICE_CHANGE, and REMOVED_LISTING events.

Output example

{
  "type": "PRICE_CHANGE",
  "listing": {
    "id": "6150993730",
    "url": "https://www.otomoto.pl/osobowe/oferta/example.html",
    "title": "Example vehicle",
    "price": 119900,
    "currency": "PLN",
    "year": 2022,
    "mileage_km": 42000
  },
  "previous_price": 124900,
  "previous_currency": "PLN",
  "delta": -5000,
  "delta_pct": -4.0032
}

Scope

The Actor monitors the public data visible on OTOMOTO result pages. It does not claim access to private seller data or privileged OTOMOTO APIs.