# Europe Job Search – 7 job boards in one run (PL DK UK LV HR PK) (`listingworks/europe-jobs-search`) Actor

Extract job postings from 7 national job boards (Praca.pl, Jobindex, Reed, CV.lv, Posao.hr, MojPosao, Rozee.pk) by keyword and location: title, employer, location, country, board, salary where shown, posting date, URL.

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

## Pricing

$1.50 / 1,000 result items

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

## Europe Job Search – 7 job boards in one run

Extract job postings from 7 national job boards (Praca.pl, Jobindex, Reed, CV.lv, Posao.hr, MojPosao, Rozee.pk) by keyword and location: title, employer, location, country, board, salary where shown, posting date, URL.

### Three rows from a real run

| Board | Country | Title | Employer | Salary |
| --- | --- | --- | --- | --- |
| praca.pl | PL | Specjalista / Specjalistka do spraw cyberbezpieczeństwa – be… | Centrum Informatyki Statystycznej | 8000–11500 PLN per month |
| reed.co.uk | GB | Python Developers | INTEC SELECT LIMITED | 650–750 GBP per day |
| cv.lv | LV | DevOps | Decta SIA | 4500–5500 EUR per month |

A run with `keywords: ["python"]`, `maxItemsPerBoard: 500` and `countries: ["pl", "dk", "uk", "lv", "hr", "pk"]` on 2026-10-14 returned 786 postings in 105 seconds and would cost about $1.18 at the current price. Full fields for every row are shown below.

One input, one dataset, one column layout for Poland, Denmark, the United Kingdom, Latvia, Croatia and Pakistan. Each row says which board and country it came from, so you can compare markets without stitching seven exports together.

### What you get

| Country | Board | What the board shows on its results pages |
|---|---|---|
| Poland (PL) | [Praca.pl](https://www.praca.pl) | title, employer, town, posting date, salary on a few postings |
| Denmark (DK) | [Jobindex](https://www.jobindex.dk) | title, employer, place, posting date |
| United Kingdom (GB) | [Reed](https://www.reed.co.uk) | title, employer, town, posting date, salary on most postings |
| Latvia (LV) | [CV.lv](https://www.cv.lv) | title, employer, town, posting date, salary on every posting |
| Croatia (HR) | [Posao.hr](https://www.posao.hr) | title, employer, town (no posting dates on this board) |
| Croatia (HR) | [MojPosao](https://mojposao.hr) | title, employer, town, posting date |
| Pakistan (PK) | [Rozee.pk](https://www.rozee.pk) | title, employer, city, posting date, salary on some postings |

A test on 14 October 2026 with the keyword `python` and 500 postings per board returned 786 postings: Reed 500, Rozee.pk 181, Praca.pl 37, CV.lv 36, Jobindex 20, MojPosao 12, Posao.hr 0. Salary was filled on 387 of 500 Reed rows and on all 36 CV.lv rows.

### Input

| Field | What it does |
|---|---|
| `keywords` | Required. What to search for, e.g. `["python"]`, `["nurse", "driver"]`. Each keyword is its own search on each board, in the board's own language: add the local word where it matters, e.g. `driver`, `kierowca` (Polish) and `vozač` (Croatian). |
| `location` | Optional. A town or region, e.g. `Warszawa`, `København`, `London`, `Riga`, `Zagreb`, `Lahore`. A board that does not know the place, or finds nothing there, searches its whole country instead and says so in the run's warnings. Leave empty for whole countries. |
| `countries` | Which boards to search: `pl`, `dk`, `uk`, `lv`, `hr` (both Croatian boards), `pk`. All six by default. |
| `maxItemsPerBoard` | A hard stop on each board, 1 to 500. Default 50, so a default run delivers at most 350 postings. |
| `sinceDays` | Optional. Only postings that went online in the last N days: `1` keeps yesterday and today. Posao.hr shows no posting dates, so it is left out when this is set. |

Example:

```json
{
  "keywords": ["python"],
  "countries": ["pl", "dk", "uk", "lv", "hr", "pk"],
  "maxItemsPerBoard": 50
}
```

On 14 October 2026 this returned 205 postings in 33 seconds.

### Output

One row per posting. Empty fields are left out of a row.

| Field | What it holds |
|---|---|
| `title`, `company`, `location` | Job title, employer, place as the board writes it |
| `country`, `board` | `PL`, `DK`, `GB`, `LV`, `HR`, `PK`; `praca.pl`, `jobindex.dk`, `reed.co.uk`, `cv.lv`, `posao.hr`, `mojposao.hr`, `rozee.pk` |
| `employer_name_withheld` | `true` when the employer was left empty because it is or contains a private person's name (a sole trader's trade name, for example) |
| `salary_min`, `salary_max`, `salary_currency`, `salary_period` | Pay as the board states it, where it does |
| `posted_at` | The day the posting went online, where the board shows it |
| `employment_type`, `workload`, `apply_url`, `application_deadline` | Where the board shows them |
| `source_url`, `external_id`, `source_site`, `scraped_at` | The board's own link and id, and when the row was read (UTC) |

The run's key-value store holds `RUN_REPORT`: rows, pages and verdict per board, and the warnings.

### Daily new postings

Make a task from this Actor with your keywords, set `sinceDays` to `1`, and schedule it every morning. Each run then returns only what went online since the previous day, from every board that shows posting dates, in the same columns as a full run.

### When a board fails

A board that is blocked, changes its pages or does not know your input delivers what it has, often nothing, and the run carries on with the other boards. The run still succeeds, and the warnings say which board and why: in the status line, and in `RUN_REPORT`. A run in which no board found anything also succeeds, with a warning, so you are not charged for an error.

### Pricing

$1.50 per 1,000 postings. Platform usage is included: you pay only for postings you receive, and a run stops cleanly at your maximum charge.

### How it works

The same code as our seven single-board Actors (Praca.pl, Jobindex, Reed, CV.lv, Posao.hr, MojPosao and Rozee.pk Scrapers) runs here in one process, one board after another, each at its own pace. No other Actor is called, so you are not billed twice. Only public search-result pages are read; posting pages are never opened. No contact person, e-mail address or phone number is collected.

### Legal notice

Each board has its own terms of use (read on 14 October 2026). Praca.pl, Reed, CV.lv, Posao.hr and MojPosao restrict copying their content, reusing it commercially or extracting their databases without their consent; Jobindex and Rozee.pk name no such restriction. Read the terms of the boards you use, and make sure that what you do with the rows is allowed by them; that check is yours.

This Actor reads public search-result pages only, on paths each board's robots.txt allows, at each board's own modest pace. You decide what you do with the rows; data-protection and database law where you use them is yours to follow.

### Support

Open an issue on this Actor with the run ID and your input. We answer within one business day.

# Actor input Schema

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

What to search for on every board, e.g. python, nurse, driver. Each keyword is its own search on each board. Use words the boards' own languages understand where it matters (kierowca on Praca.pl, vozač on the Croatian boards); English job titles work on most boards.

## `location` (type: `string`):

A town or region, e.g. Warszawa, København, London, Riga, Zagreb, Lahore. Each board reads it in its own way; a board that does not know the place searches its whole country instead, and the run says so in its warnings. Leave empty for whole countries.

## `countries` (type: `array`):

Which boards to search. Croatia means both Posao.hr and MojPosao. All six by default.

## `maxItemsPerBoard` (type: `integer`):

A hard stop on each board, so the bill is predictable: 50 per board over 7 boards is at most 350 postings.

## `sinceDays` (type: `integer`):

Keep only postings that went online in the last N days, counted in UTC from the day the run starts: 1 = yesterday and today. Made for a daily scheduled task. Posao.hr shows no posting dates and is left out when this is set.

## Actor input object example

```json
{
  "keywords": [
    "python"
  ],
  "location": "",
  "countries": [
    "pl",
    "dk",
    "uk",
    "lv",
    "hr",
    "pk"
  ],
  "maxItemsPerBoard": 50
}
```

# Actor output Schema

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

All postings of the run, with board and country.

## `employers` (type: `string`):

The same postings ordered around who is hiring.

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

Rows, pages and verdict per board, and the warnings (a board that was blocked or did not know the place).

# 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 = {
    "keywords": [
        "python"
    ],
    "countries": [
        "pl",
        "dk",
        "uk",
        "lv",
        "hr",
        "pk"
    ],
    "maxItemsPerBoard": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("listingworks/europe-jobs-search").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 = {
    "keywords": ["python"],
    "countries": [
        "pl",
        "dk",
        "uk",
        "lv",
        "hr",
        "pk",
    ],
    "maxItemsPerBoard": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("listingworks/europe-jobs-search").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 '{
  "keywords": [
    "python"
  ],
  "countries": [
    "pl",
    "dk",
    "uk",
    "lv",
    "hr",
    "pk"
  ],
  "maxItemsPerBoard": 50
}' |
apify call listingworks/europe-jobs-search --silent --output-dataset

```

## MCP server setup

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

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/TdVnjR25TrmGwIswt/builds/Yk0KC34CtKXavDQaz/openapi.json