NAV Arbeidsplassen Scraper — Norway Jobs & Employers

Export every publicly advertised job in Norway from NAV's official Arbeidsplassen feed — employer, location, sector, requirements and deadlines — to JSON, CSV or Excel.

What does NAV Arbeidsplassen Scraper do?

NAV, the Norwegian Labour and Welfare Administration, publishes every vacancy advertised on arbeidsplassen.nav.no through a keyless public endpoint. This Actor reads that feed directly: no API key, no login, no cookies.

Roughly 14 000 ads are live at any moment. The endpoint caps deep paging on a single query, so a naive scraper stalls after a few hundred rows. This Actor detects when a request exceeds that ceiling and splits the run across Norway's 17 counties, paginating each slice separately and de-duplicating on the ad UUID. That is what turns a capped query into a full-market export.

Each row carries 38 fields — employer name, municipality and county, sector, employment extent, required education and experience, work language, application deadline and NAV's generated summary of the role.

Who is it for?

• Recruitment and staffing agencies tracking which Norwegian employers are hiring, and where.
• B2B sales teams using hiring signals to spot companies that are growing.
• Job boards and aggregators that need a licence-free Norwegian feed.
• Labour-market analysts measuring demand by county, sector and occupation.
• HR-tech vendors prospecting employers who post roles regularly.

Use cases

• Build a weekly list of every employer hiring nurses in Vestland, with ad links.
• Detect the moment a target account posts its first engineering role.
• Compare public-sector versus private-sector hiring volume across counties.
• Feed a niche Norwegian job board without negotiating a data licence.
• Track which education levels and work languages employers actually require.

Why use this Actor?

• Keyless — nothing to sign up for, nothing to configure.
• 38 structured fields per ad, including sector, extent and requirements.
• Passes the paging cap by splitting the country into counties automatically.
• Real filters — keyword, county, municipality, remote-only, published-in-last-N-days.
• Official source — NAV's own feed, not a brittle HTML page.
• Honest columns — every field is populated from the feed; nothing is shipped as a permanently empty column.

What data can you extract?

Field	Type	Description
jobId	string	NAV ad UUID
title	string	Job title as advertised
jobTitle	string	Normalised job title
employerName	string	Employer name
businessName	string	Business/trading name
employerDescription	string	About-the-employer text
occupationLevel1	string	Broad occupation group
occupationLevel2	string	Specific occupation
categories	string	NAV/ESCO/STYRK category labels
municipality	string	Municipality (kommune)
city	string	City
county	string	County (fylke)
country	string	Country
streetAddress	string	Workplace address
postalCode	string	Postal code
remote	string	Remote/home-office flag
engagementType	string	Permanent, temporary, seasonal …
extent	string	Full-time or part-time
positions	string	Number of positions
sector	string	Public or private sector
workLanguage	string	Required work languages
education	string	Required education
experience	string	Required experience
needDriversLicense	string	Driving licence requirement
keywords	string	Employer keywords
searchTags	string	NAV search tags
aiTags	string	NAV-generated topic tags
summary	string	Short generated summary
applicationDue	string	Application deadline
applicationEmail	string	Application e-mail
hasInterestForm	boolean	Interest form available
source	string	Origin system of the ad
medium	string	Publishing medium
reference	string	Employer reference
published	string	Publication timestamp
expires	string	Expiry timestamp
adUrl	string	Public ad page
scrapedAt	string	Run timestamp (ISO 8601)

Example output

{
  "jobId": "168c3ffc-5d26-4143-a8d2-58ae0dd81ecf",
  "title": "Welders for rotational work",
  "employerName": "LYS BEMANNING AS",
  "occupationLevel1": "Håndverkere",
  "occupationLevel2": "Platearbeider og sveiser",
  "municipality": "NAMSOS",
  "county": "TRØNDELAG",
  "country": "NORGE",
  "workLanguage": "Norsk, Engelsk, Skandinavisk",
  "summary": "Welders needed for workshop work with rotation options.",
  "aiTags": "MAG-sveising, Sveiser, rotasjonsarbeid, stålkonstruksjon",
  "published": "2026-08-07T18:24:25+02:00",
  "expires": "2026-08-28T00:00:00+02:00",
  "adUrl": "https://arbeidsplassen.nav.no/stillinger/stilling/168c3ffc-5d26-4143-a8d2-58ae0dd81ecf",
  "source": "Stillingsregistrering"
}

How to use it

1. Enter a keyword — or leave it empty to export everything currently online.
2. Optionally filter by county, municipality, remote-only, or a recency window.
3. Set Maximum results. Small runs use one fast query; larger ones slice by county automatically.
4. Run, then export JSON, CSV or Excel, or read the dataset from the Apify API.

Input example

{
  "query": "sykepleier",
  "counties": ["OSLO", "VESTLAND"],
  "publishedAfterDays": 7,
  "maxResults": 3000
}

Notes and limits

• The feed carries ads that are currently published; expired ads drop out. Schedule the Actor to build a history.
• NAV supports 1, 3, 7 and 30-day recency windows. Other values round up to the nearest supported window.
• Applications go through the ad page (adUrl) or NAV's interest form; hasInterestForm tells you which. The feed does not expose a separate direct apply link.
• Data comes from NAV under Norwegian open-data terms. You are responsible for how you use it, including under GDPR.

FAQ

Do I need a NAV account or API key? No. The feed is open and this Actor needs nothing from you.

Can I export more than a few hundred ads? Yes. Raise the maximum and the Actor splits the run across counties to get past the deep-paging cap.

Is the full ad text included? No. NAV's search feed carries a generated summary plus tags and requirements, but the full body loads client-side on the ad page. Use adUrl to open the original when you need the complete text.

How fresh is the data? Ads appear as soon as they are published on Arbeidsplassen.

How am I charged? Pay per result — you pay for the ads delivered, nothing else.

---

*Maintained: last verified 2026-09-01 — checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).

---

Related scrapers

Other Actors from the same collection:

• Platsbanken
• PNet
• Jobberman
• jobs.ch

How much NAV Arbeidsplassen data can you extract in one run?

A single run returned 200 rows in 6 seconds on the example input. That example is deliberately narrow; the result limit and the input list are both yours to widen. That is roughly 2,000 rows a minute.

There is no hard ceiling built into this Actor. What bounds a run is the result limit you set, the breadth of the input you give it, and how much NAV Arbeidsplassen itself publishes. Because billing is per result, a wider run costs proportionally more and a narrow one costs almost nothing — so it is worth starting small and scaling once the output looks right.

NAV Arbeidsplassen scraping — frequently asked questions

Do I need a NAV Arbeidsplassen API key, account or login?

No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.

How do I export NAV Arbeidsplassen data to CSV, Excel, JSON or Google Sheets?

Open the Storage tab after a run and pick the format you want — CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.

Can I schedule this NAV Arbeidsplassen scraper to run daily or hourly?

Yes. Use the Schedules tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the rows you care about really do change that fast.

How many rows can I get, and what does it cost?

See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.

Is scraping NAV Arbeidsplassen legal?

This Actor collects only information that NAV Arbeidsplassen publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.

What happens if NAV Arbeidsplassen blocks the run or changes its layout?

A refused exit IP is swapped for a fresh one within a quarter of a second and retried, and rate limiting is waited out rather than fought. If nothing gets through, the run fails with the reason instead of reporting success with zero rows — so an empty result always means "no matches", never "the source would not answer".

Can I use this with an AI agent, LangChain or an MCP client?

Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.

Legal and compliance

This Actor collects publicly available information from NAV Arbeidsplassen only. It does not log in, does not circumvent access controls, and collects no private data. You are responsible for using the output lawfully, including under GDPR and comparable regimes where the rows contain personal data, and for respecting NAV Arbeidsplassen's terms where they apply to you.