Finn.no Jobs Scraper

Extract comprehensive job listings from FINN.no with fast, reliable automation. Collect detailed hiring data including titles, companies, locations, deadlines, and full job descriptions. Ideal for recruitment intelligence, market research, and job board aggregation.

---

Features

• Comprehensive Job Data — Collect listing metadata plus rich detail fields in one run.
• Flexible Search Input — Run by keyword/location or provide one or multiple FINN search URLs.
• Full Description Coverage — Capture structured description HTML and clean text output.
• Automatic Pagination — Continue through search pages until your result target is reached.
• Production-Ready Output — Structured dataset suitable for BI tools, alerts, and pipelines.
• Proxy Support — Optional proxy configuration for more reliable large-scale runs.

---

Use Cases

Recruitment Intelligence

Track active hiring demand across roles, regions, and employers. Build candidate sourcing and outreach lists from current openings.

Labor Market Analysis

Analyze hiring trends over time using titles, industries, locations, and posting dates. Measure seasonal demand and category shifts.

Competitor Hiring Monitoring

Monitor which companies are expanding and what skill sets they prioritize. Use this signal for strategic planning and benchmarking.

Job Aggregation Products

Feed external job listings into your internal portal, newsletter, or niche board. Keep listings fresh with repeat scheduled runs.

---

Input Parameters

Parameter	Type	Required	Default	Description
startUrls	Array	No	—	One or more FINN search URLs to process.
keyword	String	No	"utvikler"	Search keyword when startUrls are not provided.
location	String	No	—	Location name or FINN location taxonomy id.
results_wanted	Integer	No	20	Maximum number of job records to save.
max_pages	Integer	No	20	Safety cap for number of result pages.
proxyConfiguration	Object	No	{"useApifyProxy": false}	Optional proxy settings for reliability.

---

Output Data

Each dataset item can include:

Field	Type	Description
title	String	Job title
company	String	Hiring company name
sector	String	Employer sector
location	String	Job location
industry	String	Industry categories
job_function	String	Functional role categories
employment_type	String	Employment type
date_posted	String	Posting timestamp/date
valid_through	String	Application deadline
description_html	String	Job description in HTML
description_text	String	Job description as plain text
url	String	Listing URL
ad_id	Number	FINN ad identifier
search_key	String	Search source key
no_of_positions	Number	Number of open positions
coordinates	Object	Geo coordinates when available
labels	Array	Listing labels/tags
keywords	Array	Extracted listing keywords
working_languages	Array	Languages listed for the role
salary	Object	Salary/compensation information
address	Object	Structured job address
ai_summary	Object	Structured short summary fields
_source	String	Source identifier

---

Usage Examples

Basic Keyword Search

{
  "keyword": "utvikler",
  "location": "Oslo",
  "results_wanted": 20
}

Start From a Specific FINN Search URL

{
  "startUrls": [
    { "url": "https://www.finn.no/job/search?q=ingenior&location=1.20001.20061" }
  ],
  "results_wanted": 20
}

Multiple Searches in One Run

{
  "startUrls": [
    { "url": "https://www.finn.no/job/search?q=utvikler&location=1.20001.20061" },
    { "url": "https://www.finn.no/job/search?q=analytiker&location=1.20001.20012" }
  ],
  "results_wanted": 50,
  "max_pages": 20
}

With Proxy Configuration

{
  "keyword": "data engineer",
  "results_wanted": 20,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

---

Sample Output

{
  "title": "Sommervikarer søkes til Norsk skogfinsk museum",
  "company": "STIFTELSEN NORSK SKOGFINSK MUSEUM",
  "sector": "Privat",
  "location": "Grue Finnskog",
  "industry": "Kunst og kultur, Reise og turisme, Restaurant, mat og uteliv",
  "job_function": "Kontor og administrasjon / Resepsjon",
  "employment_type": "Sommer/Sesong",
  "date_posted": "2026-02-18T08:41:19.000Z",
  "valid_through": "2026-03-15T22:59:59.999Z",
  "description_html": "<p>...</p>",
  "description_text": "Sommersesongen naermer seg...",
  "url": "https://www.finn.no/job/ad/451608196",
  "ad_id": 451608196,
  "search_key": "SEARCH_ID_JOB_PARTTIME",
  "no_of_positions": 6,
  "labels": [
    { "id": "job_easy_apply", "text": "Enkel soeknad", "type": "PRIMARY" }
  ],
  "_source": "finn.no"
}

---

Tips for Best Results

Use Focused Queries

• Start with specific role terms (for example: utvikler, analytiker).
• Add location filtering to reduce noise and improve relevance.

Keep QA and Monitoring Runs Small

• Use results_wanted: 20 for quick verification runs.
• Increase limits only for production collection jobs.

Use Stable Start URLs

• Save high-performing FINN search URLs and reuse them.
• Prefer explicit location filters to keep results consistent.

Improve Reliability at Scale

• Enable proxy configuration for larger recurring runs.
• Schedule periodic runs instead of one very large run.

---

Integrations

Connect your data with:

• Google Sheets — Build live job tracking dashboards
• Airtable — Create searchable recruiting databases
• Slack — Send alerts when new matching jobs appear
• Webhooks — Push results to your internal services
• Make — Automate downstream enrichment and routing
• Zapier — Trigger hiring and reporting workflows

Export Formats

• JSON — API pipelines and custom applications
• CSV — Spreadsheet analysis and sharing
• Excel — Business reporting workflows
• XML — System integration scenarios

---

Frequently Asked Questions

Can I scrape by keyword and by URL?

Yes. You can use keyword/location or provide startUrls with one or more FINN search URLs.

Does it include full job descriptions?

Yes. Output includes description_html and description_text when available.

How many jobs can I collect in one run?

You can increase results_wanted based on your needs. For QA and smoke tests, keep it at 20.

What if some fields are missing?

Some listings do not expose every field. Missing fields are returned as null or empty arrays.

Does the actor handle duplicates?

Yes. The output is deduplicated during collection to avoid repeated job ads.

---

Support

For issues or feature requests, use the Apify Console issue/support workflow.

Resources

• Apify Documentation
• Apify API Reference
• Apify Schedules

---

Legal Notice

This actor is intended for legitimate data collection and analysis. Users are responsible for complying with FINN.no terms and all applicable laws and regulations. Use collected data responsibly.