# finn.no Scraper – Property for sale & Property to rent (`babyman/finn-no-scraper`) Actor

Scrape property listings, rental listings, used-car listings, classified ads, job adverts from finn.no (Norway) into clean structured rows: title, price, currency, location, coordinates, seller and a direct link. Same schema as every other adscraper actor.

- **URL**: https://apify.com/babyman/finn-no-scraper.md
- **Developed by:** [HelpFunder AS](https://apify.com/babyman) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 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.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## finn.no Scraper – Property for sale & Property to rent

Scrape property listings and rental listings from **finn.no** (Norway) and get clean,
structured rows — title, price, currency, location, coordinates, images, seller
and the link back to the ad — as JSON, CSV or Excel.

### What you get

Every row uses the same schema across all adscraper actors, so finn.no data
lines up next to any other country's without remapping a thing.

| field | type | what it is |
|---|---|---|
| `source` | string | Which site the ad came from (`finn`) |
| `country` | string | ISO-2 country code (NO) |
| `category` | string | `realestate, rental, car, marketplace, job` |
| `id` | string | The site's own ad id |
| `url` | string | Direct link to the advert |
| `title` | string | Ad headline |
| `price` | number | Numeric price, separators stripped |
| `currency` | string | ISO currency code (NOK) |
| `location` | string | Place as the site states it |
| `lat` / `lng` | number | Coordinates, when the site publishes them |
| `published` | string | ISO-8601 publication time |
| `image` | string | Main photo URL |
| `seller_type` | string | `private`, `dealer` or `agent` |
| `seller_name` | string | Shop, dealer or agency name |
| `size_m2` | number | Living area in square metres |
| `rooms` | number | Room count |
| `bedrooms` | number | Bedroom count |
| `size_m2` | number | Living area in square metres |
| `rooms` | number | Room count |
| `bedrooms` | number | Bedroom count |
| `make` | string | Manufacturer |
| `model` | string | Model |
| `year` | number | Model year |
| `mileage` | number | Odometer reading |
| `fuel` | string | Fuel / drivetrain |
| `gearbox` | string | Transmission |
| `company` | string | Hiring organisation |
| `job_title` | string | Role title |
| `scraped_at` | string | When this row was captured |
| `raw` | object | The site's untouched record — only with **Include raw source record** |

### Input

| field | what it does |
|---|---|
| `category` | realestate, rental, car, marketplace, job |
| `searchQuery` | Free text. Empty means "newest listings". |
| `location` | Area filter. What finn.no accepts varies — a place name, a postcode or the site's own area id. Leave empty to search everywhere. |
| `startUrls` | Paste search URLs straight from finn.no with filters already applied — they win over the fields above. |
| `maxResults` | Default 50. `0` means everything the search has, capped at 10,000. |
| `includeRaw` | Adds the site's original record to each row. |
| `delaySeconds` | Politeness delay between pages. Minimum 2 s. |

#### Example input

```json
{
  "category": "realestate",
  "maxResults": 100
}
```

#### Example output

```json
{
  "source": "finn",
  "country": "NO",
  "category": "realestate",
  "id": "477140089",
  "url": "https://www.finn.no/ad/477140089",
  "title": "Example listing headline",
  "price": 2450000,
  "currency": "NOK",
  "location": "Example area",
  "lat": 59.9019,
  "lng": 10.7531,
  "published": "2026-09-24T08:12:00+00:00",
  "image": "https://images.example.com/photo.jpg",
  "seller_type": "agent",
  "seller_name": "Example Agency",
  "size_m2": 112,
  "rooms": 4,
  "bedrooms": 3,
  "scraped_at": "2026-09-26T03:06:14Z"
}
```

### What people use it for

- **Price research** — track what comparable homes actually list for, by area and over time.
- **Market monitoring** — run it on a schedule and diff the dataset to catch new listings and price cuts the day they happen.
- **Lead generation** — pull seller and agency names for outreach.
- **Data products and dashboards** — feed a BI tool, a spreadsheet or your own app through the Apify API.
- **Cross-border comparison** — combine with the other adscraper actors and compare Norway against any other market in one table.

### How it works

finn.no builds its search results into the page as JSON. This
actor reads that data structure directly — no headless browser, no brittle CSS
selectors, so it is fast and cheap to run and it does not break the moment the
site restyles a button.

Requests are paced politely: at least 1.5 seconds between pages and one request
at a time. This actor **does not bypass bot protection**, solve CAPTCHAs, rotate
proxies to dodge blocks, or log in anywhere. It reads what the site serves to an
ordinary visitor. If finn.no ever refuses the request, the run stops with a
clear message instead of fighting it — and you are not charged for listings that
were never returned.

### Pricing

Pay per result: **USD 2.00 per 1,000 listings**. You are charged only for rows
actually written to the dataset. A run that returns nothing costs nothing.

### FAQ

**How many listings can I get in one run?**
Up to 10,000. finn.no itself caps a search at about 50 pages. For bigger pulls, split the search — by area, by
price band, by category — and run it several times.

**Can I use my own search URL with filters?**
Yes. Set your filters on finn.no, copy the URL from the address bar and put
it in `startUrls`. Everything in the URL is respected.

**How fresh is the data?**
It is fetched live at the moment the run starts. Nothing is served from a cache.

**Can I run it on a schedule?**
Yes — use Apify Schedules. Many people run it nightly and diff datasets to spot
new listings and price changes.

**What if the site blocks it?**
The run ends with a status message saying so, and nothing is charged. This actor
respects the site's decision by design; there is no setting that changes that.

**Can I get fields you have not mapped?**
Turn on `includeRaw` and the site's complete original record comes along in each
row.

**Is this legal?**
It reads publicly visible listing pages the same way a browser does, at a
polite rate, without logging in or circumventing access controls. You are
responsible for how you use the data — check finn.no's terms and your local
rules, especially around personal data and republishing.

### Other actors in this family

Same schema, other markets: `finn-no-scraper` (Norway), `blocket-se-scraper`
(Sweden), `dba-dk-scraper` (Denmark), `tori-fi-scraper` (Finland),
`zillow-scraper` (US), `rightmove-scraper` (UK), `willhaben-scraper` (Austria),
`olx-scraper` (Poland) and more. Search the Store for **adscraper**.

# Actor input Schema

## `category` (type: `string`):

Which kind of ad to search. This site supports: realestate, rental, car, marketplace, job.

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

Free-text search, e.g. the make of a car or the thing you are looking for. Leave empty to get the newest listings.

## `location` (type: `string`):

Area filter. What finn.no accepts varies — a place name, a postcode or the site's own area id. Leave empty to search everywhere.

## `startUrls` (type: `array`):

Paste one or more search URLs copied straight from finn.no with your filters already applied. When set, these win over the fields above.

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

How many listings to return. 0 means every listing the search has (capped at 10,000).

## `includeRaw` (type: `boolean`):

Add the site's untouched source record to every row. Useful for fields this actor does not map yet; makes the dataset much larger.

## `delaySeconds` (type: `integer`):

Politeness delay. The minimum is 1.5 s and cannot be lowered — this actor does not hammer sites.

## Actor input object example

```json
{
  "category": "realestate",
  "startUrls": [],
  "maxResults": 50,
  "includeRaw": false,
  "delaySeconds": 2
}
```

# 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 = {
    "searchQuery": "",
    "location": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("babyman/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 = {
    "searchQuery": "",
    "location": "",
}

# Run the Actor and wait for it to finish
run = client.actor("babyman/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 '{
  "searchQuery": "",
  "location": ""
}' |
apify call babyman/finn-no-scraper --silent --output-dataset

```

## MCP server setup

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