# Arbeidsplassen Scraper: Norway Jobs (NAV) (`santamaria-automations/arbeidsplassen-jobs-scraper`) Actor

Scrape job ads from Arbeidsplassen (arbeidsplassen.nav.no), the public job portal of NAV in Norway: title, employer, places, county, dates, deadline and, on request, the full ad text, conditions and contacts. Pay-per-result.

- **URL**: https://apify.com/santamaria-automations/arbeidsplassen-jobs-scraper.md
- **Developed by:** [NanoScrape](https://apify.com/santamaria-automations) (community)
- **Categories:** Jobs, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## Arbeidsplassen Scraper: Norway Jobs (NAV)

Scrape job ads from [arbeidsplassen.nav.no](https://arbeidsplassen.nav.no/), the public job portal run by the Norwegian Labour and Welfare Administration (NAV). Search by keyword and county, get one clean row per ad, with Norwegian text kept as it is on the site. No login and no API key.

### What you get

- Title, job title, employer, every place (address, postal code, city, municipality, county), occupation categories, search tags, keywords, summary, published date, application deadline, expiry and ad status for every ad.
- Optional ad page data (includeDetails): full description as HTML and plain text, employer description, sector, engagement type, extent, number of positions, start date, work days and hours, work languages, home office wording, work experience, competences, how to apply, and contact persons exactly as the ad shows them publicly.
- Ids are the ad uuid, so you can dedupe across runs. Each row has the ad address in job_url.

### Use with AI Agents (MCP)

Connect this actor to any MCP-compatible AI client: Claude Desktop, Claude.ai, Cursor, VS Code, LangChain, LlamaIndex, or custom agents.

**Apify MCP server URL:**

`https://mcp.apify.com?tools=santamaria-automations/arbeidsplassen-jobs-scraper`

**Example prompt once connected:**

> "Use `arbeidsplassen-jobs-scraper` to find up to 30 ads for the keyword "sykepleier" in the counties Oslo and Akershus, with includeDetails turned on for the full ad text. Return results as a table with title, company, location and job URL."

Clients that support dynamic tool discovery (Claude.ai, VS Code) receive the full input schema automatically.

### Input

The sample input (this is also what an empty input `{}` runs). If you set any input but no keyword and no county, the actor reads all latest ads with your limits:

```json
{
  "includeDetails": false,
  "maxResults": 20,
  "maxResultsPerQuery": 20,
  "searchQueries": [
    "sykepleier"
  ]
}
```

| Input | What it does |
|---|---|
| searchQueries | Keywords, one search per entry (for example sykepleier, elektriker, utvikler). Empty means the latest ads. |
| counties | County names as the site lists them (for example OSLO, ROGALAND, VESTLAND, TRØNDELAG). Spelling without special characters also works. Combined with every keyword. |
| maxResultsPerQuery | Rows per keyword and county search. Default 50. |
| maxResults | Rows in total across all searches. |
| includeDetails | Open each ad page for the detail columns. Default off, same price either way. |

Limits: the only filters are keyword and county. Other site filters (sector, extent, engagement type, home office, education, language) are not offered because their address parameters are not verified. The site shows at most 400 result pages (10 000 ads) per search; narrow the search with a county or keyword to go deeper. Sector, engagement type and extent are not on the result list, so they are filled only with includeDetails.

### Sample output

```json
{
  "id": "4cc3bfdb-ee5b-41ff-9929-3eaf6743898d",
  "title": "Audiograf i ØNH avtalepraksis, fast stilling.",
  "job_title": "Audiograf med bachelorgrad",
  "employer_name": "Øre-nese-hals Sørvest As",
  "location": "EGERSUND",
  "locations": [
    {
      "address": "Lindøyveien 8",
      "postal_code": "4373",
      "city": "EGERSUND",
      "municipality": "EIGERSUND",
      "county": "ROGALAND",
      "country": "NORGE"
    }
  ],
  "address": "Lindøyveien 8",
  "postal_code": "4373",
  "city": "EGERSUND",
  "municipality": "EIGERSUND",
  "county": "ROGALAND",
  "country": "NORGE",
  "categories": [
    {
      "type": "JANZZ",
      "name": "Audiograf med bachelorgrad"
    },
    {
      "type": "ESCO",
      "name": "Audiograf med bachelorgrad"
    },
    {
      "type": "STYRK08",
      "name": "Audiografer og logopeder"
    }
  ],
  "search_tags": [],
  "search_tags_ai": [
    "Audiograf",
    "Helse",
    "Høreapparat",
    "Hørselsutredning",
    "Klinikk",
    "Pasientbehandling",
    "Tinnitus",
    "Veiledning",
    "Øre-nese-hals"
  ],
  "keywords": [],
  "summary": "Som audiograf utreder du hørsel hos barn og voksne og følger opp hørselsutfordringer og tinnitus. Krever norsk autorisasjon og gode norskkunnskaper.",
  "published": "2026-11-10T16:06:41+01:00",
  "application_due": null,
  "application_due_text": "Snarest",
  "expires": "2026-12-24T00:00:00+01:00",
  "status": "ACTIVE",
  "ad_source": "Stillingsregistrering",
  "reference": "4cc3bfdb-ee5b-41ff-9929-3eaf6743898d",
  "search_score": 1,
  "superrask_soknad": false,
  "under18": false,
  "under18_reason": "Stillingen krever bachelorgrad og norsk autorisasjon som audiograf, og innebærer selvstendig utredning og oppfølging av pasienter. Den er derfor ikke egnet for ...",
  "updated": "2026-11-10T15:07:18Z",
  "sector": "Offentlig",
  "engagement_type": "Fast",
  "extent": [
    "Heltid"
  ],
  "positions": 1,
  "start_date": "Etter avtale",
  "work_days": [
    "Ukedager"
  ],
  "work_hours": [
    "Dagtid"
  ],
  "work_languages": [
    "Norsk",
    "Skandinavisk"
  ],
  "remote_options": "Hjemmekontor ikke mulig",
  "remote": false,
  "hybrid": false,
  "work_experience": "ingen krav til arbeidserfaring",
  "competences": [
    "audiograf",
    "audiologi",
    "hørselsutredning",
    "høreapparat",
    "tinnitus",
    "hørselsrehabilitering"
  ],
  "summer_job": false,
  "apply_to": "[removed]",
  "apply_type": "email",
  "contacts": [
    {
      "name": "[removed]",
      "title": "Daglig leder",
      "role": null,
      "email": "[removed]",
      "phone": null
    }
  ],
  "employer_orgnr": "926548565",
  "employer_website": "https://xn--re-nese-hals-srvest-u7bo.no/",
  "employer_description_html": "<p>Øre, nese, hals avtalepraksis med driftsavtale med Helse Vest. Feirer 5-års jubileum denne påsken, etter at nåværende øre-nese-hals spesialist overtok i 2021 ...",
  "employer_description_text": "Øre, nese, hals avtalepraksis med driftsavtale med Helse Vest. Feirer 5-års jubileum denne påsken, etter at nåværende øre-nese-hals spesialist overtok i 2021. ...",
  "description_html": "<section id=\"arb-aapningstekst\">\n<p>Ønsker du å jobbe i Norges antagelig kjekkeste øre-nese-hals praksis?</p>\n<p>Vi ønsker å øke vårt tilbud til lokalbefolkning ...",
  "description_text": "Ønsker du å jobbe i Norges antagelig kjekkeste øre-nese-hals praksis?\n\nVi ønsker å øke vårt tilbud til lokalbefolkningen og etablerer en ny stilling.\n\nHva vi se ...",
  "job_url": "https://arbeidsplassen.nav.no/stillinger/stilling/4cc3bfdb-ee5b-41ff-9929-3eaf6743898d",
  "details_fetched": true,
  "search_query": "fixture",
  "source": "arbeidsplassen.nav.no",
  "scraped_at": "2026-11-10T15:00:00Z"
}
```

Contact details are shown here as \[removed]; the dataset holds what the ad shows publicly. Columns marked detail below are null (or an empty list) unless includeDetails is on.

### Fields

| Column | Mode | Description |
|---|---|---|
| `id` | list | Ad id (uuid): the id in the ad address /stillinger/stilling/<id>. It is the dedup key. |
| `title` | list | Ad headline as shown on the result list. |
| `job_title` | list | Job title (occupation name) the employer gave the ad. |
| `employer_name` | list | Employer name as shown on the ad. |
| `location` | list | Places of the ad joined by comma (city, else municipality, else county of each place). |
| `locations` | list | All work places of the ad: address, postal_code, city, municipality, county, country. Parts the ad does not give are null. |
| `address` | list | Street address of the first place that has a city. Not every ad gives one. |
| `postal_code` | list | Postal code of the first place that has a city. |
| `city` | list | City of the first place that has a city. |
| `municipality` | list | Municipality (kommune) of the first place. |
| `county` | list | County (fylke) of the first place, for example OSLO or ROGALAND. |
| `country` | list | Country of the first place (NORGE for Norway, or the foreign country of an international ad). |
| `categories` | list | Occupation categories of the ad as {type, name}. The type is JANZZ, ESCO or STYRK08. |
| `search_tags` | list | Occupation tags the site matched to the ad. Only some ads have them. |
| `search_tags_ai` | list | Topic tags the site generated for the ad. |
| `keywords` | list | Keywords the source of the ad gave. Only some ads have them. |
| `summary` | list | Short summary of the ad, generated by the site (Norwegian). |
| `published` | list | Publication time, ISO 8601 with the time zone offset. |
| `application_due` | list | Application deadline as ISO date. Null when the ad gives text instead, such as "Snarest" (see application_due_text). |
| `application_due_text` | list | Application deadline exactly as the ad gives it: a date or text such as "Snarest" (as soon as possible). |
| `expires` | list | Time the ad expires, ISO 8601 with the time zone offset. |
| `status` | list | Status of the ad, ACTIVE for open ads. |
| `ad_source` | list | Where the ad comes from on the site: Stillingsregistrering (entered on the portal), FINN or IMPORTAPI (imported). |
| `reference` | list | Reference of the ad at its source (an id or number). |
| `search_score` | list | Relevance score of the site for the search. 1 when no keyword was used. |
| `superrask_soknad` | list | True when the ad offers the quick "Superrask søknad" application. Null when the list does not say. |
| `under18` | list | True when the site rates the ad as suitable for applicants under 18 years. |
| `under18_reason` | list | Reason the site gives for its under-18 rating (Norwegian text). |
| `updated` | detail | Time the ad was last changed, ISO 8601. Needs the ad page. |
| `sector` | detail | Employer sector: Offentlig (public) or Privat (private). Needs the ad page. |
| `engagement_type` | detail | Type of employment, for example Fast, Vikariat, Engasjement, Prosjekt. Needs the ad page. |
| `extent` | detail | Heltid (full time) and/or Deltid (part time). Needs the ad page. |
| `positions` | detail | Number of open positions of the ad. Needs the ad page. |
| `start_date` | detail | Start of the job: an ISO date when the ad gives one, otherwise the text of the ad, for example "Etter avtale". Needs the ad page. |
| `work_days` | detail | Work days, for example Ukedager, Lørdag, Søndag. Needs the ad page. |
| `work_hours` | detail | Work hours, for example Dagtid, Kveld, Natt. Needs the ad page. |
| `work_languages` | detail | Languages of the work place, for example Norsk, Engelsk. Needs the ad page. |
| `remote_options` | detail | Home office wording of the ad. Needs the ad page. |
| `remote` | detail | True when the ad is home office only ("Kun hjemmekontor"). Null when the ad does not say. Needs the ad page. |
| `hybrid` | detail | True when the ad allows partial home office ("Delvis hjemmekontor"). Null when the ad does not say. Needs the ad page. |
| `work_experience` | detail | Work experience the ad asks for, as classified by the site. Needs the ad page. |
| `competences` | detail | Skills the site extracted from the ad. Needs the ad page. |
| `summer_job` | detail | True when the site rates the ad as a summer job. Needs the ad page. |
| `apply_to` | detail | Where to apply, exactly as the ad shows it: an email address or a web address. Needs the ad page. |
| `apply_type` | detail | email or url: what apply_to is. Needs the ad page. |
| `contacts` | detail | Contact persons shown on the ad page, as {name, title, role, email, phone}, exactly as displayed. Needs the ad page. |
| `employer_orgnr` | detail | Norwegian organisation number of the employer. Needs the ad page. |
| `employer_website` | detail | Website of the employer. Needs the ad page. |
| `employer_description_html` | detail | Employer description as HTML. Needs the ad page. |
| `employer_description_text` | detail | Employer description as plain text. Needs the ad page. |
| `description_html` | detail | Full ad text as HTML. Needs the ad page. |
| `description_text` | detail | Full ad text as plain text. Needs the ad page. |
| `job_url` | list | Address of the ad on arbeidsplassen.nav.no. |
| `details_fetched` | list | True when the ad page was read for this row. |
| `search_query` | list | Keyword that found the ad, or "all jobs" for a search without keyword. |
| `source` | list | Site the ad comes from. |
| `scraped_at` | list | Time of the scrape, ISO 8601 UTC. |

### Pricing

Price: $0.001 start fee per run, then $0.0009 per job result ($0.90 per 1,000 jobs).

The start fee is the apify-actor-start event. Each ad row is one job-result event. includeDetails does not change the price. The run stops when your spending limit is reached and keeps the rows already delivered.

**New to Apify?** Every account gets a $5 free monthly platform credit, enough to try this actor at no cost.

### Related Actors

- [Finn.no Scraper: Norway Classifieds, Jobs, Homes & Cars](https://apify.com/santamaria-automations/finn-no-scraper): Norwegian classifieds site Finn.no, including its job ads.
- [Arbetsförmedlingen Scraper: Platsbanken Swedish Jobs](https://apify.com/santamaria-automations/arbetsformedlingen-se-scraper): Swedish public job board Platsbanken, run by the employment agency.
- [Jobindex.dk Job Scraper - Danish Jobs](https://apify.com/santamaria-automations/jobindex-dk-scraper): Danish jobs from Jobindex.dk.
- [Indeed Jobs Scraper - 60+ Countries, $0.06 per 1,000 Jobs](https://apify.com/santamaria-automations/indeed-http-scraper): Indeed jobs in over 60 countries.

### FAQ

**Is this allowed?** The data is public job ads that anyone can read on the site without logging in. Contact persons are only included when the ad displays them publicly. Check your own rules for processing personal data.

**Why are some columns empty?** Ads fill only what the employer entered. Columns marked detail need includeDetails.

**Why do I get fewer rows than the site total?** The site lists at most 400 pages per search and listings change quickly, so the same ad can show on two pages (it is delivered once).

**What does a search with no hits do?** It finishes without error, 0 rows, and the run status says "0 jobs found for <query>.".

**Is the text translated?** No. Titles and descriptions stay in the language of the ad, mostly Norwegian.

### Support

Something broken, or a field you wish this Actor returned? Open a ticket on the Actor's [Issues tab](https://apify.com/santamaria-automations/arbeidsplassen-jobs-scraper/issues) or email contact@nanoscrape.com. We usually respond within one working day.

# Changelog

This Actor's version history is a separate document: https://apify.com/santamaria-automations/arbeidsplassen-jobs-scraper/changelog.md

# Actor input Schema

## `searchQueries` (type: `array`):

Keywords such as sykepleier, tømrer, utvikler or butikkmedarbeider. Each keyword runs as its own search; an ad found by several keywords is returned once. Leave empty to list the newest ads (or the ads of the chosen counties).

## `counties` (type: `array`):

Only ads in these counties (fylke): Agder, Akershus, Buskerud, Finnmark, Innlandet, Møre og Romsdal, Nordland, Oslo, Rogaland, Svalbard, Telemark, Troms, Trøndelag, Vestfold, Vestland or Østfold. Names without æ, ø and å work too (Trondelag). Each county is its own search; an ad found twice is returned once. A name that is no county is ignored; if none is left the run returns 0 jobs.

## `maxResultsPerQuery` (type: `integer`):

Maximum number of ads per keyword and county combination (or in total when no keyword is set). 0 = up to 1000. The site lists at most 10 000 ads per search.

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

Maximum number of ads in the dataset across all searches. 0 = no limit.

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

Read each ad page for the full description, employer description, conditions (extent, engagement type, work hours and days, languages, start date, positions), home office, application address and the contact persons the ad shows. Turn on when you need more than the list fields; the run is slower.

## Actor input object example

```json
{
  "maxResultsPerQuery": 50,
  "maxResults": 0,
  "includeDetails": false
}
```

# Actor output Schema

## `jobs` (type: `string`):

Dataset with the scraped Arbeidsplassen job ads.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("santamaria-automations/arbeidsplassen-jobs-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("santamaria-automations/arbeidsplassen-jobs-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 '{}' |
apify call santamaria-automations/arbeidsplassen-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,santamaria-automations/arbeidsplassen-jobs-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/GvTuckEwo9IPBSBCd/builds/hkga18Sk9QV1ICLZq/openapi.json
