# Otomoto Listing Lookup — Poland's Dominant Car Marketplace API (`accountable_eel/otomoto-listing-lookup`) Actor

Look up vehicle listings on otomoto.pl, Poland's dominant car marketplace, by URL. Get price, make, model, year, mileage, fuel type, engine, gearbox, condition, seller type, and city. Pay only for listings that resolve.

- **URL**: https://apify.com/accountable\_eel/otomoto-listing-lookup.md
- **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community)
- **Categories:** E-commerce, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 successful lookups

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?

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 Listing Lookup

Look up any vehicle listing on [otomoto.pl](https://www.otomoto.pl), Poland's dominant
car marketplace, by URL — price, make, model, year, mileage, fuel type, engine,
gearbox, body type, condition, seller, and location. The listing's full detail set is
embedded server-side in a `__NEXT_DATA__` JSON payload, so this reads structured data
directly rather than scraping rendered HTML.

### Features

- **URL → full listing record.** Title, price, currency, and status straight from the
  page's own data, not parsed from visible text.
- **Full vehicle spec.** Make, model, year, mileage, fuel type, engine power and
  capacity, gearbox, body type, color, condition, and accident-free flag.
- **Seller & location.** Seller type (private/dealer), seller name, city, region, and
  photo count.
- **Pay only for hits.** Listings that don't resolve — sold, removed, or malformed
  URLs — cost nothing; see [Pricing](#pricing).
- **Built for bulk.** Feed in thousands of listing URLs; concurrency, keyword
  filtering, and column selection are all configurable.

### How to use Otomoto Listing Lookup — Poland's Dominant Car Marketplace API

1. **In the Apify Console.** Open the actor page and click **Start** — the `listingUrls` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~otomoto-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"listingUrls":["https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "listingUrls": [
    "https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html"
  ]
}
```

One otomoto.pl vehicle listing URL per line (the /osobowe/oferta/... page). Accepted formats: https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html.

```json
{
  "listingUrls": [
    "https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html"
  ],
  "testRun": false,
  "onlyFound": false,
  "maxConcurrency": 5
}
```

`listingUrls` is a list of otomoto.pl vehicle listing URLs (the `/osobowe/oferta/...`
page). One dataset row is returned per URL; rows with `"found": false` are never
charged. Turn on `testRun` to try your list against just the first 5 URLs before
running the full batch. Optional `includeKeywords` / `excludeKeywords` filter rows by
content, `maxResults` caps the run early, and `columns` lets you pick which fields to
return. `proxyConfiguration` defaults to Residential proxies — this is a defended
marketplace at scale, so a plain datacenter IP risks getting blocked.

### Output

| query | found | status | title | price | currency | make | model | year | mileageKm | fuelType | enginePower | engineCapacity | gearbox | bodyType | color | condition | accidentFree | sellerType | sellerName | city | region | photoCount | listingId | url | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html | true | OK | BMW Seria 5 | 49000 | PLN | BMW | Seria 5 | 2019 | 98000 | Benzyna | 245 KM | 1 998 cm3 | Automatyczna | Sedan | Biały | Używany | true | PRIVATE | Olek | Wrocław | Dolnośląskie | 10 | 6147794388 | https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html | 2026-08-31T07:10:15.700Z |

One row per listing URL, for example:

```json
{
  "query": "https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html",
  "found": true,
  "status": "OK",
  "listingId": "6I3va0",
  "title": "BMW Seria 5 520d xDrive",
  "url": "https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html",
  "price": 129900,
  "currency": "PLN",
  "make": "BMW",
  "model": "Seria 5",
  "year": 2019,
  "mileageKm": 98000,
  "fuelType": "Diesel",
  "enginePower": "190 KM",
  "engineCapacity": "1995 cm3",
  "gearbox": "Automatyczna",
  "bodyType": "Sedan",
  "color": "Czarny",
  "condition": "Używane",
  "accidentFree": true,
  "sellerType": "Dealer",
  "sellerName": "Auto Centrum Warszawa",
  "city": "Warszawa",
  "region": "mazowieckie",
  "photoCount": 24,
  "scrapedAt": "2026-08-21T10:00:00.000Z"
}
```

Listings that no longer exist — sold or removed — still get a row (`"found": false`,
`"status": "NOT_FOUND"`), so you always get one row per input URL, but you're never
charged for those.

### Use cases

- **Price monitoring** — track asking prices on a watchlist of listings over time.
- **Inventory enrichment** — attach full vehicle spec to a list of listing URLs pulled
  from search results or a lead list.
- **Dealer research** — compare seller type, pricing, and mileage across listings from
  a specific dealer or region.
- **Market analysis** — build a dataset of make/model/year/price combinations for
  valuation or trend work.
- **Listing health checks** — confirm which URLs in a saved list are still live before
  reaching out to a seller.

### Pricing

$3 per 1,000 listings, plus a $0.00005 start fee. Misses (`found:false`) are never charged.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~otomoto-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"listingUrls":["https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~otomoto-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"listingUrls":["https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~otomoto-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"listingUrls":["{{listing}}"]}`, mapping the row's listing into the `listingUrls` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Otomoto.pl API — Car Listing Data by URL" — the agent will find and run this actor.

### FAQ

**Do I need to log in to Otomoto to look up a listing?**
No. This actor reads the listing's own embedded page data over a plain HTTP request —
no account or API key involved.

**What happens if a listing has sold or been removed?**
You get a dataset row with `"found": false` and `"status": "NOT_FOUND"` — Otomoto
returns HTTP 404 or 410 for gone listings, and that row is never charged.

**Why does this default to Residential proxies?**
Otomoto is a large, actively defended marketplace. A plain datacenter IP risks getting
blocked at any real volume, so Residential is the safer default — you can override it
in `proxyConfiguration` if you have your own proxy setup.

**Can I look up listings in bulk?**
Yes. Turn on `testRun` first to sanity-check your list against 5 URLs, then run the
full batch — `maxConcurrency` controls how many requests run in parallel (keep it
conservative; this target has no browser fallback, so getting blocked costs more than
slow-and-steady).

**What URL format does it accept?**
The full listing page URL, e.g.
`https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html`. A bare listing slug
also works — it gets expanded to the full URL automatically.

**Does the price field include currency conversion?**
No — `price` and `currency` are returned exactly as Otomoto lists them (almost always
PLN), with no conversion applied.

# Actor input Schema

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

One otomoto.pl vehicle listing URL per line (the /osobowe/oferta/... page). Accepted formats: https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html. You're only charged for the ones we actually find — a miss costs nothing.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

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

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

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

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "listingUrls": [
    "https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html"
  ],
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "columns": [
    "title",
    "price",
    "currency",
    "make",
    "model",
    "year",
    "mileageKm",
    "fuelType",
    "enginePower",
    "engineCapacity",
    "gearbox",
    "bodyType",
    "color",
    "condition",
    "accidentFree",
    "sellerType",
    "sellerName",
    "city",
    "region",
    "photoCount",
    "listingId",
    "url"
  ],
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (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 = {
    "listingUrls": [
        "https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/otomoto-listing-lookup").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 = {
    "listingUrls": ["https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/otomoto-listing-lookup").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 '{
  "listingUrls": [
    "https://www.otomoto.pl/osobowe/oferta/bmw-seria-5-ID6I3va0.html"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/otomoto-listing-lookup --silent --output-dataset

```

## MCP server setup

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

```

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/OBA6a7yOUZCjVblaP/builds/Uqa2bhN82ZmgWihaU/openapi.json