# Denmark Job Market Stats – Jobindex job counts by region (`listingworks/denmark-job-market-stats`) Actor

Counts of Danish job postings on Jobindex.dk by region (the 5 regioner) and job category, read from the site's region pages and 30 occupation searches. Aggregates only, no postings or names. Read live from list pages on each run.

- **URL**: https://apify.com/listingworks/denmark-job-market-stats.md
- **Developed by:** [Yusuke Suda](https://apify.com/listingworks) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 listing analyzeds

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

## Denmark Job Market Stats – Jobindex job counts by region

How many jobs are advertised on Jobindex.dk in each of Denmark's five regions (Hovedstaden, Sjælland, Syddanmark, Midtjylland, Nordjylland) and in 13 job categories. Counts only: Jobindex.dk shows no pay on its list pages. A sample, not the whole market: see How the counts are made.

### Example

| Site | Region | Postings | With pay | Median pay (lower bound) |
|---|---|---:|---:|---:|
| jobindex.dk | Hovedstaden | 223 | 0 | – |
| jobindex.dk | Midtjylland | 130 | 0 | – |
| jobindex.dk | Syddanmark | 103 | 0 | – |

Default input, run on 22 October 2026: 182 listings read in 1.9 minutes, 59 aggregate rows; at $1.50 per 1,000 listings read the run cost $0.27.

### What you get, and what you don't

- **Counts, not listings.** The run returns aggregate rows only: no titles, no advertisers, no addresses, no texts,
  no links, no contact details, no person's name. Nothing about an individual listing leaves the run.
- **List pages only.** The run reads the site's public search-result pages, paced as the site's own Actor in this
  catalogue is (one request every 2 seconds), and never opens a listing's own page.
- **A sample of the newest listings.** The site lists newest first; the run counts up to `maxListings` of them. The
  summary row says how many were read and, where the site shows it, the site's own total.
- **Medians need 5 values.** A median is shown only where at least 5 postings have the value; otherwise it is empty.
- The last row of every run is a `summary` per site: postings read, the site's own total where shown, whether the run
  stopped at `maxListings`, and any warning (an unknown place, a blocked page).

### Input

| Field | What it does |
|---|---|
| `maxListings` | Postings to read and count at most (default 1,000, up to 10,000). |
| `region` | One region only (see below). Empty: the whole country. |
| `category` | One job category only: it, finance_admin_hr, sales_customer, production, engineering_technical, transport_logistics, construction, health_care, education, hospitality_food, cleaning_security, management, other. |
| `keyword` | Count only the postings the site finds for this word. |
| `occupationSearches` | Off (default): the site's 10 region pages only, about 200 postings in about 2 minutes. On: also 30 occupation searches, about 800 postings at most in all, several minutes more. |

Example: `{"region": "Midtjylland", "category": "health_care"}`. An input the run cannot use (an unknown region, a keyword with no result) ends
SUCCEEDED with no rows and the reason in the status message and the run report (`RUN_REPORT`).

### Output

| Field | Meaning |
|---|---|
| `level` | `region` (one row per region), `region_category` (per region and job category) or `summary`. |
| `date` | Day of the run (UTC). |
| `source` | The site counted. |
| `region` | Region, `abroad` or `unmapped`. |
| `category` | Job category (`all` on `region` rows). |
| `postings` | Postings read in this group. |
| `postings_with_pay` | Of them, postings that state pay. |
| `pay_unit`, `currency` | The pay period and currency of this row's median. A group with several units has one row per unit. |
| `postings_with_this_unit` | Postings with pay in this unit and currency. |
| `median_pay_lower` | Median of the lower bound of the advertised pay; empty below 5 postings. |

### How the counts are made

Jobindex.dk's robots.txt lets a reader see the first 20 postings of a search and no second page, so the run reads the site's 10 region pages (about 200 postings) and, with `occupationSearches` on, 30 occupation searches as well: about 800 postings at most, of the roughly 19,000 the site held on 15 October 2026. The summary row says so. The place each posting shows is put in its region with a table of about 300 Danish towns; a place not in the table stays `unmapped` (13 % in the example run). With `region` set, the same searches are read and only that region is kept; with `keyword`, the keyword is searched on each of the 10 region pages.

Jobindex.dk shows no pay on its list pages: `postings_with_pay` is 0 and the pay columns are empty.

Job categories are found from keywords in the job title (English and the site's language), first match wins, `other` when nothing matches: approximate. Share of `other` in the example run: 12 %.

### Pricing

$1.50 per 1,000 postings read (event `listing-analyzed`), no start fee. The aggregate rows themselves
are free: a default run reads up to 1,000 postings and costs at most $1.50. Set a maximum charge per run
in the run options to cap it.

### Good to know

- The data is what Jobindex.dk shows on its public list pages on the day of the run.
- Run it on a schedule (daily or weekly) and keep the datasets for a time series; each row carries its `date`.
- Questions or a missing region: open an issue on this Actor.

# Actor input Schema

## `maxListings` (type: `integer`):

How many listings the run reads and counts at most (charged per listing read). The counts are a sample of the newest listings, not the whole market, unless the site holds fewer.

## `region` (type: `string`):

Count only this region, one of: Hovedstaden, Sjælland, Syddanmark, Midtjylland, Nordjylland. Empty: the whole country, every region.

## `category` (type: `string`):

Count only postings of this category (from keywords in the job title; approximate). Only postings of the category are read into the counts and charged.

## `keyword` (type: `string`):

Count only postings the site finds for this search word, e.g. chauffør.

## `occupationSearches` (type: `boolean`):

Off: the site's 10 region pages only (about 200 postings, about 2 minutes). On: also 30 occupation searches (about 800 postings at most in all, several minutes more).

## Actor input object example

```json
{
  "maxListings": 1000,
  "region": "",
  "category": "",
  "keyword": "",
  "occupationSearches": false
}
```

# Actor output Schema

## `overview` (type: `string`):

The aggregate rows of the run.

## `summary` (type: `string`):

One row per site: listings read and warnings.

## `runReport` (type: `string`):

Every search made, with its verdict.

# 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("listingworks/denmark-job-market-stats").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("listingworks/denmark-job-market-stats").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 listingworks/denmark-job-market-stats --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,listingworks/denmark-job-market-stats"
        }
    }
}
```

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/pc59f7doZO6XW9UAG/builds/vbkEDcEJ89NH2EZYh/openapi.json