# Arbeidsplassen Scraper — Norwegian Jobs & Full Ads, No Phones (`highbrow_fame/arbeidsplassen-nav-jobs`) Actor

Job ads from Arbeidsplassen (NAV), Norway's public job board: title, employer, place, occupation, employment type, full-/part-time, sector, dates, apply link, full text. No contacts, no phones.

- **URL**: https://apify.com/highbrow_fame/arbeidsplassen-nav-jobs.md
- **Developed by:** [yestrue](https://apify.com/highbrow_fame) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.90 / 1,000 job delivereds

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 — Norwegian Jobs & Full Ads, No Phones

Get job ads from Arbeidsplassen (arbeidsplassen.nav.no), the public job board of NAV, the Norwegian Labour and Welfare Administration: title, employer and its organisation number, municipality and county, occupation, employment type (fast, vikariat, …), full- or part-time, public or private sector, publication date, application deadline, the employer's apply link and the full ad text. Paste your Arbeidsplassen search links — or type keywords, places and occupations.

**Why this one**

- 🔗 **Your search, as you set it up.** Set the filters you like on arbeidsplassen.nav.no/stillinger and paste the link. Or type keywords (sykepleier, utvikler, lærer), places (Oslo, Bergen, Vestland, Tromsø, "Utland") and occupations here, and choose full- or part-time, type of employment, sector and "published" below.
- 📄 **The whole ad, not just the list.** Every job comes with what only the ad page has: employment type, full-/part-time and percentage, number of positions, shift pattern, remote work, start date, the employer's organisation number, sector and website, the apply link and the full text.
- ⚡ **Steady and polite.** Arbeidsplassen limits how fast one visitor may ask (a faster pace drew "too many requests" within 35 seconds), so the Actor keeps one steady pace: a live run read four searches — 1,000 jobs in Oslo, 359 private full-time IT jobs, public-sector health jobs in Bergen (97) and Trondheim (69) — 1,525 jobs in 19 minutes without a single refusal. The daily test search (30 nurse jobs in Oslo) takes about 30 seconds.
- 🏛️ **The official source.** The same ads, and the same counts, as the Arbeidsplassen website — NAV publishes them as open data under the Norwegian Licence for Open Government Data (NLOD).
- 🔒 **No contact persons, no phones.** The ad's contact list and its application e-mail address are never read, street addresses are left out, and names, phone numbers and e-mail addresses are taken out of the ad texts (of the 150 newest ads, 102 named a contact person, 35 had an e-mail address and 36 a phone number in the text). In the 1,525 jobs of the live run, no record carried an e-mail address or a phone number.
- 💸 **You pay only for jobs delivered.** A link that is not an Arbeidsplassen search, or a place or occupation Arbeidsplassen does not know, comes back as a free record with the reason.

### What you get

For every job:

| Field | What it is |
|---|---|
| `title`, `jobTitle`, `summary`, `description` | the ad's headline, the position's title, NAV's two-sentence summary and the full ad text (contact persons, phones and e-mails taken out) |
| `employer`, `employerOrgNumber`, `employerWebsite`, `sector` | the employer as the ad names it (often with the department), its organisation number, website, and Offentlig (public) or Privat (private) |
| `location`, `city`, `municipality`, `county`, `postcode`, `country`, `allLocations` | where the job is — municipality and county, no street address; an ad can list several places |
| `occupation`, `occupations`, `occupationTags`, `competences` | the occupation in the Norwegian standard classification (STYRK-08, e.g. Sykepleiere), Arbeidsplassen's own occupation tags and the skills it found in the ad |
| `engagementType`, `extent`, `jobPercentage`, `positions`, `workSchedule`, `workDays`, `workHours`, `remote`, `startDate`, `workLanguages` | the terms: Fast / Vikariat / Engasjement / …, Heltid or Deltid and how much, how many people are hired, shifts (Turnus, Skift, Vakt), days and hours, home office, start, working language |
| `publishedAt`, `updatedAt`, `expiresAt`, `applicationDeadline` | dates; the deadline is a date or the employer's words ("Snarest") |
| `url`, `applicationUrl`, `applyOnArbeidsplassen`, `originalAdUrl`, `source`, `jobId` | the ad on Arbeidsplassen, the employer's apply link, whether you can apply on Arbeidsplassen itself, and where the ad came from (FINN, an applicant tracking system, or registered on Arbeidsplassen) |
| `input`, `place`, `position`, `scrapedAt`, `status`, `error` | which search it came from, and why a search gave nothing |

#### Example

A real record from a live run — nurse jobs in Oslo, 26 September 2026 (lists and the text are shortened here):

```json
{
  "jobId": "d9bf0bd0-318c-468b-8378-47ed64699805",
  "title": "Er du sykepleier og vil bidra til trygg ivaretakelse av beboere ved Bekkelagshjemmet?",
  "jobTitle": "Sykepleier, Bekkelagshjemmet",
  "employer": "Lovisenberg Omsorg AS",
  "employerOrgNumber": "983373127",
  "employerWebsite": "https://www.lovisenbergomsorg.no/",
  "sector": "Privat",
  "location": "Oslo, Oslo",
  "municipality": "Oslo",
  "county": "Oslo",
  "postcode": "1178",
  "country": "Norge",
  "occupation": "Sykepleiere",
  "occupationTags": ["Sykepleier"],
  "competences": ["sykepleier", "eldreomsorg", "geriatrisk sykepleie", "…"],
  "engagementType": "Fast",
  "extent": "Heltid",
  "jobPercentage": "100%",
  "positions": 1,
  "workSchedule": "Turnus",
  "workLanguages": ["Norsk"],
  "publishedAt": "2026-09-08T00:00:00+02:00",
  "expiresAt": "2026-09-29T00:00:00+02:00",
  "applicationDeadline": "2026-09-29",
  "url": "https://arbeidsplassen.nav.no/stillinger/stilling/d9bf0bd0-318c-468b-8378-47ed64699805",
  "applicationUrl": "https://candidate.webcruiter.com/cv?advertid=5174622916&language=nb&link_source_id=17&utm_medium=talentech_publishing&utm_source=nav",
  "applyOnArbeidsplassen": false,
  "source": "IMPORTAPI",
  "summary": "Fast stilling som sykepleier med ansvar for oppfølging, behandling og veiledning i eldreomsorg. Norsk autorisasjon og gode norskferdigheter kreves.",
  "description": "Vil du bli en del av gruppen som jobber aktivt og målrettet for at de som bor hos oss opplever trygghet og får gode dager? Vi har ledig 100% og 80% fast stilling for sykepleier, for tiden på dag og kveld med arbeid hver tredje helg. …",
  "input": "https://arbeidsplassen.nav.no/stillinger?q=sykepleier&county=OSLO",
  "status": "OK"
}
```

### How to use it

1. Paste **Search links** from arbeidsplassen.nav.no/stillinger, one per line — or type **Keywords**, **Places** and **Occupations**. Each keyword is searched in each place.
2. Narrow it down if you like: **Full- or part-time**, **Type of employment**, **Sector**, **Published** (today, last 3 days, last 7 days) and **Order**, and set **Max jobs per search**.
3. Press **Start**, and download the results from the **Output** tab as JSON, CSV or Excel.

To follow new jobs, save your input as a task with **Published** set to "Today" and schedule it daily. The "Published" choice works for links too.

Places are matched to Arbeidsplassen's own list of counties and municipalities: "Bergen", "Tromso" and "Vestland" work; two municipalities share the names Herøy and Våler — "Herøy" searches both, "Herøy, Nordland" one. "Utland" gives the jobs abroad. Occupations are matched to Arbeidsplassen's occupation list: a field ("IT", "Helse og sosial") or an occupation ("Sykepleier", "Utvikling") is that one; otherwise every occupation that contains what you typed. The run log says what each one matched.

You can also call it from the Apify API, from Make, Zapier or n8n, or from an AI agent through the Apify MCP server.

### Pricing

You are charged **per job delivered** — see the price on this page. Links that are not Arbeidsplassen searches, and places or occupations Arbeidsplassen does not know, are free.

### FAQ

**How many jobs per search?** As many as you ask for. Arbeidsplassen had 14,272 ads in all on 26 September 2026; Oslo 2,545, Bergen 1,024, and all full-time jobs 10,070. The site shows at most 10,000 ads of one search, so a bigger one (only all of Norway, or all full-time jobs, is that big) is read county by county, repeats left out.

**How fast is it?** About 80 jobs a minute (1,525 jobs in 19 minutes in a live run). Every job needs its own ad page, and Arbeidsplassen answers "too many requests" to anyone who asks much faster; the Actor keeps below that, and if the site asks it to slow down anyway, it waits and goes on more slowly.

**Which Arbeidsplassen links work?** Results pages (arbeidsplassen.nav.no/stillinger?…) with any of the website's filters — search words, county and municipality, occupation, full-/part-time, type of employment, sector, published, home office, abroad, distance from a postcode and the sort order. The link is asked as it is, so it gives what the website shows. A link to a single ad is not a search.

**Why is a job outside the place I searched?** An ad can list several places of work and is found under each of them: in a live run 40 of 1,525 jobs had more than one, and one Bergen job had Haugesund first. `allLocations` lists them all.

**Where do the ads come from?** From NAV's Arbeidsplassen, which also shows ads from FINN.no and other job sites: in the live run, 802 of 1,525 jobs came from FINN (`source` is FINN, and `originalAdUrl` links the original ad). NAV publishes the job ads as open data under the Norwegian Licence for Open Government Data (NLOD).

**Why no phone numbers or contact names?** They are personal data. Every ad has its `url` and, mostly, an `applicationUrl`; applicants reach the employer there. Sentences that ask you to contact a named person are taken out of the text, and so are "Kontaktinformasjon" blocks; the rest of the ad stays (on a sample of 150 ads, 97.8% of the text was kept).

**Why is the employer sometimes a department?** Arbeidsplassen shows the name the ad was published under — often a department with its organisation ("Fødeavdelingen, Oslo universitetssykehus"). `employerOrgNumber` is the organisation's number in the Brønnøysund register.

**Is this affiliated with NAV or Arbeidsplassen?** No. This is an independent tool that reads NAV's public job ads.

**Like it?** A short review on the Store page helps other people find this Actor. Something missing or broken? Tell us on the Issues tab — we read every one.

# Actor input Schema

## `searchUrls` (type: `array`):

Set up a search on arbeidsplassen.nav.no/stillinger with the filters you want and paste the address of the results page. One per line.

## `keywords` (type: `array`):

Or search here without a link: job titles, skills or employers (sykepleier, utvikler, lærer, Equinor). Each keyword is searched in each place below, or in all of Norway when there is no place. The filters below apply.

## `locations` (type: `array`):

Norwegian counties (fylker) or municipalities (kommuner): Oslo, Bergen, Vestland, Trondheim, Tromsø; "Herøy, Nordland" when two counties have a municipality by that name; "Utland" for jobs abroad. A place without keywords gives all its jobs.

## `occupations` (type: `array`):

Optional: only jobs in these occupations, as Arbeidsplassen names them: a field (IT; Helse og sosial; Bygg og anlegg) or an occupation (Sykepleier; Helsefagarbeider; Utvikling). Otherwise every occupation that contains the text. The run log says what each one matched.

## `extent` (type: `string`):

Optional: only full-time (heltid) or only part-time (deltid) jobs.

## `engagementTypes` (type: `array`):

Optional: only these types of employment (ansettelsesform).

## `sector` (type: `string`):

Optional: only public-sector or only private employers.

## `published` (type: `string`):

Optional: only ads published today, in the last 3 days or in the last 7 days (the site's own choices). Works for links too.

## `sortBy` (type: `string`):

For keyword and place searches.

## `maxListingsPerSearch` (type: `integer`):

Stops each search after this many jobs.

## `maxConcurrency` (type: `integer`):

How many searches to work on at the same time. The whole run keeps one polite pace towards the site either way.

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

Used only when a request fails to connect: the requests go out directly first.

## Actor input object example

```json
{
  "searchUrls": [
    "https://arbeidsplassen.nav.no/stillinger?q=sykepleier&county=OSLO"
  ],
  "extent": "any",
  "sector": "any",
  "published": "any",
  "sortBy": "relevance",
  "maxListingsPerSearch": 30,
  "maxConcurrency": 3,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Every result as a JSON record, with a status for each input.

## `resultsCsv` (type: `string`):

The same records as CSV, for a spreadsheet.

# 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 = {
    "searchUrls": [
        "https://arbeidsplassen.nav.no/stillinger?q=sykepleier&county=OSLO"
    ],
    "maxListingsPerSearch": 30,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("highbrow_fame/arbeidsplassen-nav-jobs").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 = {
    "searchUrls": ["https://arbeidsplassen.nav.no/stillinger?q=sykepleier&county=OSLO"],
    "maxListingsPerSearch": 30,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("highbrow_fame/arbeidsplassen-nav-jobs").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 '{
  "searchUrls": [
    "https://arbeidsplassen.nav.no/stillinger?q=sykepleier&county=OSLO"
  ],
  "maxListingsPerSearch": 30,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call highbrow_fame/arbeidsplassen-nav-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,highbrow_fame/arbeidsplassen-nav-jobs"
        }
    }
}
```

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/khsjKnrQ2vdDkuQRL/builds/DXEuehrWYhwGF9wB7/openapi.json