Finn.no Vehicle Listing Lookup — Norway Marketplace API

Look up any vehicle listing on 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.
• 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:

   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

{
  "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.

{
  "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:

{
  "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.

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.