# FINN.no Scraper \[From $1💰] | Real Estate | Cars | Jobs (`ahmed_jasarevic/finn-no-scraper`) Actor

Scrape FINN.no, Norway's largest marketplace, for real estate for sale/rent, used cars, and jobs. Get price, sqm, rooms, photos, and seller/dealer contact from search and detail pages — no official API needed.

- **URL**: https://apify.com/ahmed\_jasarevic/finn-no-scraper.md
- **Developed by:** [Ahmed Jasarevic](https://apify.com/ahmed_jasarevic) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 listings

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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 Scraper

### What does Finn No Scraper do?

**Finn No Scraper** extracts structured data from [FINN.no](https://www.finn.no) — Norway's largest online marketplace — across **real estate (homes for sale and rentals), used cars, and jobs**. For every listing it captures the **price, address, beds/baths/sqm, photos, seller/dealer contact, ad ID, and timestamps**, pulling from both the search results pages and each listing's detail page.

The actor runs on the [Apify platform](https://apify.com), which gives you **API access, scheduling, integrations, proxy rotation, and monitoring** out of the box. You can run it once or on a schedule to track the Norwegian market over time.

### Why use Finn No Scraper?

- **Nordics-focused investors** can track property prices, rental yields, and market trends across Norwegian cities.
- **Realtors and property analysts** get structured listing data (price, sqm, rooms, location) for comps and market reports.
- **Auto dealers** can monitor used-car inventory, pricing, and seller types (private vs. dealer).
- **Recruiters and market researchers** can pull job postings with company, location, and application deadlines.

### How to use Finn No Scraper

1. Open the actor in [Apify Console](https://console.apify.com).
2. Pick a **vertical** (homes for sale, rentals, cars, or jobs).
3. Optionally enter a **search query** (e.g. `Oslo`, `Toyota`, `sykepleier`) and set **max pages**.
4. Click **Start**. The actor crawls the search pages, then each listing's detail page.
5. Download the dataset as **JSON, HTML, CSV, or Excel**.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `vertical` | enum | `realestate_homes` | `realestate_homes`, `realestate_lettings`, `cars`, or `jobs` |
| `searchQuery` | string | empty | Optional keyword filter (e.g. `Oslo`, `Toyota`) |
| `maxPages` | integer | 5 | Max search result pages to crawl (~50 listings/page) |
| `includeDetails` | boolean | true | Also crawl each listing's detail page for full data |
| `useApifyProxy` | boolean | true | Route requests through the Apify residential proxy |

### Output

Each dataset row is one listing. Search-page rows carry the `source: "search"` summary; detail-page rows carry `source: "detail"` with the full key-info table, description, seller, and photos.

```json
{
  "source": "detail",
  "vertical": "realestate_homes",
  "adId": "475553698",
  "title": "Innholdsrik 3-roms i 3.etg - Sentral beliggenhet i attraktivt område",
  "price": "3 750 000 kr",
  "priceNumber": 3750000,
  "address": "Havstadvegen 11 B, Trondheim",
  "keyInfo": {
    "Boligtype": "Leilighet",
    "Eieform": "Eier (Selveier)",
    "Soverom": "2",
    "Bruksareal": "75 m²",
    "Etasje": "3",
    "Byggeår": "2021"
  },
  "sellerName": "EiendomsMegler 1 Melhus",
  "photos": ["https://images.finncdn.no/dynamic/1280w/..."],
  "url": "https://www.finn.no/realestate/homes/ad.html?finnkode=475553698"
}
```

You can download the dataset in various formats such as **JSON, HTML, CSV, or Excel**.

### Data table

| Field | Description |
|-------|-------------|
| `adId` | FINN ad ID (finnkode) |
| `title` | Listing title |
| `price` / `priceNumber` | Price as text and as a numeric NOK value |
| `address` / `location` | Street address and city/area |
| `area` | Square meters (real estate) |
| `rooms` | Number of rooms/bedrooms |
| `keyInfo` | Full key-value table from the detail page (beds, baths, sqm, year, fuel, mileage, etc.) |
| `company` / `sellerName` | Seller or dealer company |
| `publishedAt` | Publish timestamp (jobs) |
| `photos` | Array of image URLs |
| `url` | Canonical listing URL |

### Pricing / Cost estimation

This is a **CheerioCrawler** actor — it uses plain HTTP requests, no browser rendering — so it is very cheap to run. A typical run of 5 search pages + detail pages for one vertical costs a fraction of a compute unit. Free Apify users get a capped preview of **10 items**; paid users get unlimited runs.

### Technical notes — how the scraping works

FINN.no renders its search results **server-side** in the HTML. Recon showed:

- No `__NEXT_DATA__` / `__NUXT__` embedded JSON blobs with listing data.
- No Algolia/Meilisearch/Elasticsearch backend for listings (the `searchContext` API only returns market statistics).
- The listing data is fully present in the raw served HTML of the search and detail pages.

Therefore the actor uses **CheerioCrawler** (plain HTTP + HTML parsing) against the server-rendered pages:

- **Search pages**: `https://www.finn.no/realestate/homes/search.html`, `/realestate/lettings/search.html`, `/mobility/search/car`, `/job/search` — parsed for listing cards (`article.sf-search-ad`, `article.job-card`).
- **Detail pages**: `/realestate/homes/ad.html?finnkode=XXXX`, `/mobility/item/XXXX`, `/job/ad/XXXX` — parsed for the key-info table, pricing, description, seller, and photos.

Requests go through the **Apify residential proxy** (`BUYPROXIES94952`) to avoid IP blocks. This keeps the actor fast, cheap, and reliable — no browser needed.

### Tips / Advanced options

- **Limit cost**: set `maxPages` to 1-2 for a quick sample, or disable `includeDetails` to only get search-card summaries.
- **Track the market**: schedule the actor to run weekly and compare `priceNumber` over time.
- **Filter by location**: use `searchQuery` with a city name (e.g. `Bergen`) to narrow results.

### FAQ, disclaimers, and support

**Is scraping FINN.no legal?** FINN.no's robots.txt states that automated crawling requires written permission. Please review FINN.no's terms of service and applicable Norwegian law before using this actor at scale. This actor is provided for research and personal use; you are responsible for compliance.

**Known limitations**: FINN.no serves different page layouts per vertical, so field availability varies (e.g. jobs have no price; cars have no sqm). Some detail pages (external lettings) may lack the full key-info table.

For feedback or feature requests, open an issue on the actor's Issues tab. Need a custom solution or a different Norwegian data source? Contact us — we build custom scrapers on request.

# Actor input Schema

## `vertical` (type: `string`):

Which FINN.no category to scrape.

## `searchQuery` (type: `string`):

Optional keyword to filter listings (e.g. 'Oslo', 'Toyota', 'sykepleier'). Leave empty for all listings.

## `directUrls` (type: `array`):

Paste specific FINN.no listing URLs to scrape directly (skips search). Each URL goes straight to the detail page for full data — faster than discovery via search. Example: https://www.finn.no/realestate/homes/ad.html?finnkode=12345678

## `maxPages` (type: `integer`):

Maximum number of search result pages to crawl (each page has ~50 listings). Ignored when Direct listing URLs are provided.

## `includeDetails` (type: `boolean`):

Also crawl each listing's detail page for full data (key info, description, seller, photos). Doubles the request count.

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

Select proxies to be used by the crawler. Apify Proxy is recommended to avoid IP blocks.

## Actor input object example

```json
{
  "vertical": "realestate_homes",
  "searchQuery": "",
  "directUrls": [],
  "maxPages": 5,
  "includeDetails": true,
  "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 = {
    "vertical": "realestate_homes",
    "searchQuery": "",
    "directUrls": [],
    "maxPages": 5,
    "includeDetails": true,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("ahmed_jasarevic/finn-no-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 = {
    "vertical": "realestate_homes",
    "searchQuery": "",
    "directUrls": [],
    "maxPages": 5,
    "includeDetails": True,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("ahmed_jasarevic/finn-no-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 '{
  "vertical": "realestate_homes",
  "searchQuery": "",
  "directUrls": [],
  "maxPages": 5,
  "includeDetails": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call ahmed_jasarevic/finn-no-scraper --silent --output-dataset

```

## MCP server setup

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