# Finn.no Vehicle Listing Lookup — Norway Marketplace API (`accountable_eel/finn-listing-lookup`) Actor

Look up vehicle listings on finn.no, Norway's dominant marketplace, by URL. Get price, make, model, year, mileage, fuel type, gearbox, VIN, and color. Pay only for listings that resolve.

- **URL**: https://apify.com/accountable\_eel/finn-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, 0 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

## Finn.no Vehicle Listing Lookup — Norway Marketplace API

Look up any vehicle listing on [finn.no](https://www.finn.no), Norway's dominant online
marketplace, by URL or item ID — price, make, model, year, mileage, fuel type, gearbox,
VIN, color, and more. This actor reads the listing's own structured product data plus its
server-rendered key-info specs table directly, no login required.

### Features

- **URL or bare ID → full listing record.** Accepts a full listing URL
  (`finn.no/mobility/item/474052152`) or just the numeric item ID.
- **Structured product data.** Title, price, currency, availability, and photo count
  pulled from the listing's own `Product` structured data.
- **Full vehicle spec table.** Make, model, model year, mileage (km), fuel type, gearbox,
  body type, wheel drive, color, VIN, country, and sales form — parsed from finn.no's own
  Norwegian-labeled key-info table.
- **Pay only for hits.** URLs that don't resolve — sold, removed, or malformed — 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 Finn.no Vehicle Listing Lookup — Norway 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~finn-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"listingUrls":["https://www.finn.no/mobility/item/474052152"]}'
   ```
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.finn.no/mobility/item/474052152"
  ]
}
```

One finn.no /mobility/item/ listing URL (or bare item ID) per line. Accepted formats: https://www.finn.no/mobility/item/474052152, 474052152.

```json
{
  "listingUrls": ["https://www.finn.no/mobility/item/474052152"],
  "testRun": false,
  "onlyFound": false,
  "maxConcurrency": 5
}
```

`listingUrls` is a list of finn.no vehicle listing URLs, or bare item IDs (e.g.
`474052152`) — one per line. Turn on `testRun` to check the first 5 before committing to
a full list. `onlyFound` hides rows with no result (still free either way).
`includeKeywords` / `excludeKeywords` filter by keyword, `maxResults` caps how many hits
you pay for, `columns` picks which fields come back, and `proxyConfiguration` defaults to
Apify's Residential proxy group.

### Output

| query | found | status | title | price | currency | availability | make | model | year | mileageKm | fuelType | gearbox | bodyType | wheelDrive | color | vin | country | salesForm | imageCount | listingId | url | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| https://www.finn.no/mobility/item/474052152 | true | OK | BMW 340i | 599000 | NOK | InStock | BMW | 340i | 2017 | 145000 | Bensin | Automat | Stasjonsvogn | Firehjulsdrift | Blå | WBA8H3107HK823646 | Norge | Bruktbil til salgs | 3 | 474052152 | https://www.finn.no/mobility/item/474052152 | 2026-08-31T07:10:13.151Z |

One row per listing, for example:

```json
{
  "query": "https://www.finn.no/mobility/item/474052152",
  "found": true,
  "status": "OK",
  "title": "2019 Volkswagen Golf 1.5 TSI",
  "price": 245000,
  "currency": "NOK",
  "availability": "InStock",
  "make": "Volkswagen",
  "model": "Golf",
  "year": 2019,
  "mileageKm": 42000,
  "fuelType": "Bensin",
  "gearbox": "Automat",
  "bodyType": "Stasjonsvogn",
  "wheelDrive": "Forhjulsdrift",
  "color": "Grå",
  "vin": "WVWZZZAUZKW123456",
  "country": "Norge",
  "salesForm": "Bruktbil til salgs",
  "imageCount": 24,
  "listingId": "474052152",
  "url": "https://www.finn.no/mobility/item/474052152",
  "scrapedAt": "2026-08-21T10:15:00.000Z"
}
```

A row with `"found": false` means the listing was sold, removed, or the ID/URL didn't
resolve to a real listing — these rows are never charged.

### Use cases

- Track price changes on specific vehicles across a shortlist over time.
- Enrich a list of finn.no listing links (from a saved search export) with structured
  price, mileage, and spec data for spreadsheet analysis or filtering.
- Feed clean vehicle data into a valuation model or comparable-listings report for the
  Norwegian used-car market.
- Monitor whether a set of listings is still active, or has sold/been removed.
- Pull VIN and full spec data for a batch of listings ahead of a purchase decision.

### 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~finn-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"listingUrls":["https://www.finn.no/mobility/item/474052152"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~finn-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"listingUrls":["https://www.finn.no/mobility/item/474052152"]}` (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~finn-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 "Finn.no API — Vehicle Listing Data by URL" — the agent will find and run this actor.

### FAQ

**What counts as "not found"?** A URL or item ID that finn.no returns as a 404 (listing
sold or removed), or a page with no `Product` JSON-LD block at all — both come back as
`found: false` and are never charged.

**Can I submit just the item ID instead of a full URL?** Yes — a bare numeric ID like
`474052152` is automatically expanded to
`https://www.finn.no/mobility/item/474052152`.

**Does this cover finn.no's real estate or job listings too?** No — this actor is scoped
to `/mobility/item/` vehicle listings specifically, where price and spec data are both
available in server-rendered HTML.

**Where do fields like fuel type and gearbox come from?** They're read from finn.no's own
Norwegian-labeled key-info table on the listing page (e.g. `Drivstoff`, `Girkasse`) — if a
seller leaves a field blank on the listing itself, it comes back `null` rather than
guessed.

**What proxy should I use?** Residential is the default and recommended setting — this
is a marketplace at real-world scale, and a plain datacenter IP is more likely to get
blocked.

**Can I run thousands of URLs at once?** Yes. Use `maxConcurrency` to control request
rate, `testRun` to sanity-check a small sample first, and `maxResults` if you only need
the first N hits.

# Actor input Schema

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

One finn.no /mobility/item/ listing URL (or bare item ID) per line. Accepted formats: https://www.finn.no/mobility/item/474052152, 474052152. 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.finn.no/mobility/item/474052152"
  ],
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "columns": [
    "title",
    "price",
    "currency",
    "availability",
    "make",
    "model",
    "year",
    "mileageKm",
    "fuelType",
    "gearbox",
    "bodyType",
    "wheelDrive",
    "color",
    "vin",
    "country",
    "salesForm",
    "imageCount",
    "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.finn.no/mobility/item/474052152"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/finn-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.finn.no/mobility/item/474052152"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/finn-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.finn.no/mobility/item/474052152"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/finn-listing-lookup --silent --output-dataset

```

## MCP server setup

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