Arbetsformedlingen.se Scraper
Pricing
Pay per usage
Arbetsformedlingen.se Scraper
Scrape Swedish job listings from Arbetsförmedlingen.se instantly. Extract job titles, companies, locations & salary data. Residential proxy required for reliable data collection. Perfect for job market analysis, recruitment automation & labor intelligence.
Pricing
Pay per usage
Rating
0.0
(0)
Developer

Shahid Irfan
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Arbetsförmedlingen Platsbanken Scraper
Scrape live job listings from Arbetsförmedlingen Platsbanken. This actor collects structured job ad data and saves it to your Apify dataset.
Features
- Scrapes current Platsbanken ads with keyword and location filtering.
- Supports paginated collection with configurable limits.
- Optional detailed mode for richer ad fields.
- Returns normalized output suitable for analysis, alerts, and integrations.
Use Cases
- Monitor new job opportunities by role or location.
- Build internal job dashboards and BI reports.
- Track hiring demand trends over time.
- Export ad data into automation workflows.
Input Parameters
| Field | Type | Description |
|---|---|---|
startUrl | string | Optional direct JobSearch API search URL used as base filters. |
keyword | string | Keyword for job search, for example undersköterska. |
location | string | Optional location term, for example Stockholm. |
collectDetails | boolean | If true, loads full ad details for each result. |
results_wanted | integer | Maximum number of ads to return. Default: 20. |
max_pages | integer | Safety cap on paginated requests. Default: 10. |
proxyConfiguration | object | Optional proxy settings. |
Output Data
| Field | Type | Description |
|---|---|---|
id | string | Platsbanken ad ID |
title | string | Job headline |
company | string | Employer name |
occupation | string | Occupation label |
occupation_group | string | Occupation group label |
municipality | string | Municipality |
region | string | Region |
city | string | City |
employment_type | string | Employment type |
working_hours_type | string | Working hours type |
duration | string | Employment duration |
number_of_vacancies | integer | Number of vacancies |
publication_date | string | Publication timestamp |
application_deadline | string | Application deadline timestamp |
salary_description | string | Salary info text |
description_text | string | Job description text |
description_html | string | Sanitized job description HTML (p, br, strong, ul, li, etc.) |
webpage_url | string | Public ad URL |
Usage Example
{"keyword": "undersköterska","location": "Stockholm","results_wanted": 20,"max_pages": 5,"collectDetails": true}
Sample Output
{"id": "30691734","title": "Boendestödjare","company": "Hässleholms kommun","occupation": "Stödassistent","municipality": "Hässleholm","region": "Skåne län","number_of_vacancies": 2,"publication_date": "2026-03-04T10:41:00","application_deadline": "2026-03-18T23:59:59","webpage_url": "https://arbetsformedlingen.se/platsbanken/annonser/30691734"}
Tips
- Keep
results_wantedandmax_pagesrealistic for faster runs. - Enable
collectDetailswhen full-text fields are needed. - Output automatically excludes
nullvalues from dataset items.
Integrations
- Apify Dataset API
- Apify Webhooks
- Zapier, Make, and custom ETL pipelines
FAQ
Why are fewer ads returned than requested?
The available ads for your filters may be fewer than results_wanted, or pagination may hit max_pages.
Should I always use collectDetails?
Use it when you need richer per-ad fields. Disable it for faster lightweight collection.
Legal Notice
You are responsible for complying with applicable laws, regulations, and website terms when using extracted data.