# Otomoto Scraper — Poland Car Listings, Specs & Prices (`logiover/otomoto-scraper`) Actor

Scrape job postings for Portugal from Talent.com: title, hiring company, city, quick-apply flag, update recency and a description snippet. Keyless, no login. Export JSON, CSV or Excel.

- **URL**: https://apify.com/logiover/otomoto-scraper.md
- **Developed by:** [Logiover](https://apify.com/logiover) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 4 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.50 / 1,000 results

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Otomoto Scraper — Poland Car Listings, Specs & Prices

Export vehicle adverts from **Otomoto**, Poland's largest car marketplace — price, make, model, year, mileage, fuel, gearbox and seller — to JSON, CSV or Excel. Keyless, no login.

### What does Otomoto Scraper do?

Otomoto ships its **entire result set as structured JSON inside the page**, and this Actor reads that payload rather than parsing the rendered cards. The difference matters: prices arrive as real numbers with a currency code, and every specification comes through as a labelled parameter — no scraping values out of styled `div`s whose class names change on the next deploy.

Otomoto carries **over 200 000 live adverts**. The spec parameters arrive as a key/value list, which this Actor flattens into named columns — `make`, `model`, `year`, `mileageKm`, `fuel`, `gearbox`, `enginePowerHp` — so the export is filterable straight away.

One Polish-market signal comes along for free: **Otomoto's own price evaluation**, its assessment of whether an advert sits below or above market for that vehicle.

### Who is it for?

- **Car dealers** benchmarking Polish stock and pricing.
- **Importers** sourcing vehicles from one of Europe's biggest used-car markets.
- **Price analysts** building depreciation curves by make, model and year.
- **Marketplace builders** who need a Polish vehicle feed.
- **Fleet buyers** filtering by mileage, fuel and gearbox at scale.

### Use cases

- Build a price-versus-mileage curve for a model year across Poland.
- Find adverts Otomoto itself rates as below market price.
- Split dealer stock from private sellers to compare pricing.
- Compare dealer versus private-seller pricing for the same model.
- Track how many electric vehicles are listed month over month.

### Why use this Actor?

- **Structured source** — reads the page's own JSON, not brittle HTML.
- **Typed columns** — price, year, mileage and power are numbers, not strings.
- **Full spec breakdown** — make, model, version, fuel, gearbox, engine, body.
- **Price evaluation** included, plus whether the seller is private or a dealer.
- **Six vehicle categories** — cars, vans, motorcycles, trucks, trailers, machinery.
- **Keyless** — no account, no token, no login (Polish residential proxy is used automatically).

### What data can you extract?

Every row carries the advert identity and URL, price with currency and gross flag, Otomoto's price evaluation, the full specification set, the seller type (private or dealer) and ID, the city and region, posting date and thumbnail. See the Output tab for types.

### How to use it

1. Pick the vehicle category.
2. Optionally set a make, price band and minimum year.
3. Set **Maximum results** and run, then export JSON, CSV or Excel.

### Input example

```json
{
  "categoryPath": "osobowe",
  "make": "bmw",
  "minYear": 2018,
  "maxPrice": 120000,
  "maxResults": 2000
}
```

### Notes and limits

- Prices are asking prices in PLN, not transaction prices. `isGrossPrice` tells you whether VAT is included as published.
- Specification fields depend on what the seller filled in; missing ones stay `null` rather than being guessed.
- Mileage on brand-new vehicles is often a token value such as `5` km — that is the advert, not a parsing error.
- This Actor exports the listing payload, not full advert pages; open `advertUrl` for photos and the full description.
- You are responsible for how you use advert and seller data, including under GDPR.

### FAQ

**Do I need an Otomoto account?**
No. Adverts are public and this Actor needs nothing from you.

**Why read the JSON instead of the HTML?**
Because it gives typed values and survives redesigns — the rendered cards use build-hashed class names that change constantly.

**What is the price evaluation?**
Otomoto's own assessment of the asking price against comparable adverts, passed through as published.

**Can I scrape motorcycles or trucks?**
Yes, switch the category input.

**How am I charged?**
Pay per result — you pay for the adverts delivered.

# Actor input Schema

## `categoryPath` (type: `string`):

Otomoto section to scrape.

## `make` (type: `string`):

Optional make slug to narrow the listing, e.g. bmw, audi, toyota, tesla.

## `minPrice` (type: `integer`):

Only return adverts at or above this price. 0 disables the filter.

## `maxPrice` (type: `integer`):

Only return adverts at or below this price. 0 disables the filter.

## `minYear` (type: `integer`):

Only return vehicles from this model year onwards. 0 disables the filter.

## `maxResults` (type: `integer`):

Stop after this many adverts. Otomoto carries over 200 000 listings, so raise this for a market-wide export.

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

Otomoto blocks datacenter ranges with HTTP 403, so Polish residential IPs are used by default.

## Actor input object example

```json
{
  "categoryPath": "osobowe",
  "minPrice": 0,
  "maxPrice": 0,
  "minYear": 0,
  "maxResults": 500,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "PL"
  }
}
```

# Actor output Schema

## `advertId` (type: `string`):

No description

## `title` (type: `string`):

No description

## `shortDescription` (type: `string`):

No description

## `advertUrl` (type: `string`):

No description

## `priceAmount` (type: `string`):

No description

## `currency` (type: `string`):

No description

## `isGrossPrice` (type: `string`):

No description

## `priceEvaluation` (type: `string`):

No description

## `make` (type: `string`):

No description

## `model` (type: `string`):

No description

## `version` (type: `string`):

No description

## `year` (type: `string`):

No description

## `mileageKm` (type: `string`):

No description

## `fuel` (type: `string`):

No description

## `gearbox` (type: `string`):

No description

## `engineCapacityCcm` (type: `string`):

No description

## `enginePowerHp` (type: `string`):

No description

## `sellerType` (type: `string`):

No description

## `sellerLink` (type: `string`):

No description

## `city` (type: `string`):

No description

## `region` (type: `string`):

No description

## `createdAt` (type: `string`):

No description

## `thumbnailUrl` (type: `string`):

No description

## `country` (type: `string`):

No description

## `source` (type: `string`):

No description

## `scrapedAt` (type: `string`):

No description

## `sellerId` (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 = {
    "categoryPath": "osobowe",
    "make": "",
    "minPrice": 0,
    "maxPrice": 0,
    "minYear": 0,
    "maxResults": 500,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "PL"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("logiover/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 = {
    "categoryPath": "osobowe",
    "make": "",
    "minPrice": 0,
    "maxPrice": 0,
    "minYear": 0,
    "maxResults": 500,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "PL",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("logiover/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 '{
  "categoryPath": "osobowe",
  "make": "",
  "minPrice": 0,
  "maxPrice": 0,
  "minYear": 0,
  "maxResults": 500,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "PL"
  }
}' |
apify call logiover/otomoto-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,logiover/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/sH3KaDkCaOXnHs100/builds/thjaA3RQfSF9vI3wl/openapi.json