# Otomoto Scraper - Polish Car Listings, Prices & Dealers (`listingworks/otomoto-scraper`) Actor

Scrape Otomoto.pl car listings with prices, mileage, specs and dealer details. 24 fields per car, no proxy needed, one flat price per result.

- **URL**: https://apify.com/listingworks/otomoto-scraper.md
- **Developed by:** [Yusuke Suda](https://apify.com/listingworks) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 result items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Otomoto Scraper — Polish car listings, prices and dealers

Otomoto is Poland's largest car marketplace, with around 250,000 live listings.
This Actor turns any Otomoto search into a clean table: what the car is, what it
costs, and who is selling it.

Press Start. The defaults return listings with no configuration needed.

### What a row looks like

```json
{
  "make": "Audi",
  "model": "A3",
  "version": "Sportback 35 TDI",
  "year": 2019,
  "mileage_km": 142000,
  "fuel_type": "Diesel",
  "gearbox": "Automatic",
  "engine_capacity_ccm": 1968,
  "engine_power_hp": 150,
  "price": 69900,
  "currency": "PLN",
  "price_is_gross": true,
  "city": "Warszawa",
  "region": "Mazowieckie",
  "seller_name": "Auto Centrum Sp. z o.o.",
  "seller_type": "professional",
  "seller_url": "https://autocentrum.otomoto.pl",
  "dealer_id": "16051117",
  "posted_at": "2026-09-15T07:55:06Z",
  "source_url": "https://www.otomoto.pl/osobowe/oferta/…",
  "thumbnail_url": "https://…/image;s=640x480",
  "external_id": "6149919634"
}
```

25 columns are defined for a listing, and a row carries 24 or 25 of them: a
number the site does not give is left out rather than zeroed, which on a
100-row sample was the engine size on 2 listings. Text columns are always
there and may be blank — `seller_name`, `seller_url` and `dealer_id` are blank
on the two thirds of rows that are private sellers, and `version` where the
site names no trim level. Business sellers come with their identity and dealer
page at no extra charge and with no second request; private sellers' personal
details are deliberately not collected.

### What people use it for

Price monitoring, where you re-run a saved search on a schedule and watch a
segment of the market move. Dealer and inventory research, where the seller
fields matter as much as the cars. And feeding a comparison or valuation tool
that needs Polish market data it cannot get from an official API.

### Input

| Field | What it does |
|---|---|
| `searchTerms` | Makes to filter by. Leave empty for everything. |
| `location` | A Polish city. Uses Otomoto's own city pages. |
| `postedAfter` | Only listings posted at or after this time, for fetching just what is new since your last run. Otomoto does not order listings strictly by date, so the run keeps going until two consecutive pages are entirely older. |
| `maxItems` | Hard stop, so your bill is predictable. |
| `proxyConfiguration` | Off by default. This Actor does not need a proxy. |

### Pricing

$3.00 per 1,000 listings, dropping to $1.50 per 1,000 on higher Apify plans.
Plus $0.005 per run start. There is no separate charge for dealer details or enrichment, and
platform usage is not passed on to you.

You are charged for rows you actually receive. If you set a maximum charge for
the run, it stops cleanly at that limit instead of overshooting it.

### Scope and limits

Public listings only. Nothing behind a login.

The `location` filter uses Otomoto's own city paths. If the city is not one
Otomoto recognises, the run fails and tells you, rather than quietly returning
every listing in Poland and charging you for them.

If Otomoto changes its page structure, the run goes red. It does not return
zero rows and report success — a silent scraper is worse than a broken one,
because you find out weeks later.

A run that is blocked or cut short partway also goes red, even though the rows
it did collect are in the dataset and yours to keep. Red here means "this is
not the complete answer", not "you lost the data" — on a schedule, a run that
quietly came back short is the thing you most need to hear about.

Every run also publishes the site's own result count next to the rows it
delivered, so you can see "60 rows of 9,969 the site reports" without going
back to the site to check. That number is what the site says, not a promise
about what one run returns.

### Same data, other countries

Listings from other marketplaces on this platform come back in exactly this
shape, so a parser you write once keeps working when you add a country.

### Support

Open an issue on this Actor with the run ID and your input. Answered within
one business day.

# Actor input Schema

## `searchTerms` (type: `array`):

Makes to filter by, e.g. bmw, toyota. Leave empty for all listings.

## `location` (type: `string`):

City or region as written in the site's own URL, e.g. warszawa, krakow, lisboa. Covers the surrounding area too. Leave empty for the whole country. An unrecognised name fails the run instead of returning unfiltered results.

## `postedAfter` (type: `string`):

Return only listings posted at or after this ISO 8601 date-time, e.g. 2026-09-01T00:00:00Z.

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

Stop after this many records. Keeps your cost predictable.

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

Off by default. Turn on (residential, in the site's country) only if runs start getting blocked with 403/429.

## Actor input object example

```json
{
  "searchTerms": [],
  "location": "",
  "postedAfter": "",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

All listings from this run: what the car is, what it costs, and who is selling it.

## `pricing` (type: `string`):

The same listings reduced to the fields used for price analysis and market monitoring.

## `dealers` (type: `string`):

The same listings focused on who is selling them.

## `runReport` (type: `string`):

Pages read, records delivered, errors, and the verdict (ok, degraded or broken).

# 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 = {
    "searchTerms": [],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("listingworks/otomoto-scraper").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 = {
    "searchTerms": [],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("listingworks/otomoto-scraper").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 '{
  "searchTerms": [],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call listingworks/otomoto-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,listingworks/otomoto-scraper"
        }
    }
}
```

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/G4rj1RjhFbmJCSCTJ/builds/b9u7jslDaWxRL9efy/openapi.json