# Praca.pl Scraper - Polish Job Listings · $1.5/1K (`listingworks/praca-scraper`) Actor

Extract job postings from Praca.pl (Poland) by keyword and location: title, employer, place, contract type, salary range, posting date, URL, newest first.

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

## Pricing

from $0.75 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Praca.pl Scraper — Polish job listings by keyword and town

Extract job postings from Praca.pl (Poland) by keyword and location: title, employer, place, contract type, salary range, posting date, URL, newest first.

Praca.pl is one of Poland's established job boards, with around 18,000 live
postings: over 1,300 in Kraków alone, and large numbers in Warszawa, Wrocław,
Poznań and Gdańsk. This Actor turns its search results into a clean table: the
job title, the employer, the workplace, the contract and working time, the
salary the employer states, the day the posting went online, and the link to
the posting.

Press Start. The prefilled input searches for `kierowca` (driver) in Warszawa,
so the first run needs no configuration.

### What a row looks like

```json
{
  "title": "Operator wózka widłowego (K/M)",
  "company": "Operis HR sp. z o.o.",
  "location": "Warszawa",
  "employment_type": "umowa o pracę, pełny etat",
  "salary_min": 11000,
  "salary_max": 15000,
  "salary_currency": "PLN",
  "salary_period": "month",
  "posted_at": "2026-09-22",
  "source_url": "https://www.praca.pl/operator-wozka-widlowego-k-m_11492461.html",
  "external_id": "11492461"
}
```

`company` is the employer as the list shows it. When the employer hides its
name (the site then shows "Klient portalu Praca.pl"), `company` is empty.
Contact persons, email addresses and phone numbers are never collected. This
Actor reads the search results only and never opens the job text.

`location` is the workplace the posting names: a town, a district
("Warszawa, Ursynów"), a voivodeship, or the employer's street address. A
posting offered in several places ("3 regiony" on the site) is several postings,
each with its own ID and link, and each becomes its own row. `remote` is `true`
when the posting says fully remote work ("praca zdalna"), and empty otherwise.

`employment_type` is the contract and the working time as praca.pl writes them,
in Polish: `umowa o pracę` (employment contract), `umowa zlecenie` (civil-law
contract), `kontrakt B2B`, `pełny etat` (full-time), `część etatu`
(part-time). `salary_*` is the pay the employer states, in złoty, per month or
per hour as the posting says. Where the employer states nothing, the columns
are empty.

### Posting dates

praca.pl shows each posting's age ("3 godz.", "2 dni"), not a date. `posted_at`
is the Polish calendar day on which that age began. Because the site rounds
ages down, a posting shown as "1 dni" gets the later of its two possible days.
A "posted after" filter therefore never drops a posting that may belong inside
it. The filter compares days, not times.

### What people use it for

- Tracking which companies in a Polish city are hiring, week by week.
- Salary benchmarking from the ranges employers state, by contract type.
- Feeding a job board or a newsletter with Polish openings in a niche, such as
  drivers, warehouse staff or accountants.
- Research on the Polish labour market that needs structured rows rather than
  a page of links.

### Input

| Field | What it does |
|---|---|
| `searchTerms` | Keywords, e.g. `kierowca`, `księgowa`, `magazynier`. Each keyword is its own search. Leave empty for everything. |
| `location` | A Polish town or voivodeship, with or without Polish letters: `Warszawa`, `Kraków`, `Bielsko-Biała`, `mazowieckie`. Leave empty for the whole country. |
| `postedAfter` | Only postings from this day on, e.g. `2026-09-20`. |
| `maxItems` | A hard stop, so your bill is predictable. |
| `proxyConfiguration` | Off by default. Most runs do not need a proxy. |

### How much one run returns

praca.pl serves 50 cards per page, newest first, and the run follows the site's
own "next page" link until the list ends or `maxItems` is reached. The site
states how many postings a search holds, and the run report shows that number
next to the rows delivered. The site's pager stops at page 255. A search larger
than that is reported as capped, and more keywords or towns reach the rest. If
you search several keywords, a posting that matches more than one is delivered
only once per run.

### Pricing

$1.50 per 1,000 postings, falling to $0.75 per 1,000 on higher Apify plans,
plus $0.005 each time a run starts. Platform usage is not passed on to you.

You are charged only for rows you actually receive. If you set a maximum charge
for the run, it stops cleanly at that limit instead of going over it.

### Scope and limits

The Actor reads public listings only, from the search results pages. praca.pl's
robots.txt allows these for all crawlers. No API is called, and job pages are
not opened. The promoted "week offers" above the results and the labour-office
list below them are not part of your search and are not delivered.

A town that praca.pl does not recognise fails the run with a clear message. On
the site, an unknown town looks like a search with no results, and this Actor
will not report that as an honest zero.

Every page is checked against what you asked for: keyword, town, page number
and date order. If the site answered something else, the run fails rather than
return rows you did not ask for and charge you for them.

If praca.pl changes its page structure, the run goes red. It does not return
zero rows and report success. A silent scraper is worse than a broken one,
because you only find out weeks later.

A run that is blocked or cut short partway also goes red, even though the rows
it did collect are in the dataset and yours to keep. Red here means "this is
not the complete answer", not "you lost the data". On a schedule, a run that
quietly came back short is the thing you most need to hear about.

### Same shape, other sites

This Actor shares its output shape with:

- the Jobware Scraper (Germany)
- the jobs.ch, jobup.ch and JobScout24 Scrapers (Switzerland)
- the Jobindex Scraper (Denmark)
- the Jobs.cz Scraper (Czech Republic)
- the BestJobs Scraper (Romania)

A parser you write for one keeps working on the others, and on the countries
added next.

### Support

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

# Actor input Schema

## `searchTerms` (type: `array`):

Keywords to search for, e.g. kierowca, księgowa, magazynier. Each keyword is its own search. Leave empty for all postings.

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

A Polish town or voivodeship, with or without Polish letters (e.g. Warszawa, Kraków, Bielsko-Biała, mazowieckie). Leave empty for all of Poland. A town the site does not know fails the run instead of returning an empty or unfiltered list.

## `postedAfter` (type: `string`):

Return only postings from this day on (Polish calendar day), e.g. 2026-09-20. praca.pl shows each posting's age, not its time, so the day is what is compared.

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

Keep only listings posted in the last N days, counted in UTC from the day the run starts: 1 = yesterday and today. Made for a daily schedule. Ignored when Posted after is set.

## `maxItems` (type: `integer`):

Stop after this many postings. praca.pl serves at most 255 pages of 50 cards per search, so larger numbers are reached with more keywords or towns.

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

Off by default. Turn on (residential, in the site's country) only if runs start getting blocked with 403/429.

## Actor input object example

```json
{
  "searchTerms": [
    "kierowca"
  ],
  "location": "Warszawa",
  "postedAfter": "",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

All Polish job postings from this run: what the job is, who is hiring, where, the stated pay and the day it was posted.

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

The same postings ordered around who is hiring.

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

Pages read, records delivered, errors, and the verdict (ok, degraded or broken).

# 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 = {
    "searchTerms": [
        "kierowca"
    ],
    "location": "Warszawa",
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("listingworks/praca-scraper").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 = {
    "searchTerms": ["kierowca"],
    "location": "Warszawa",
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("listingworks/praca-scraper").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 '{
  "searchTerms": [
    "kierowca"
  ],
  "location": "Warszawa",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call listingworks/praca-scraper --silent --output-dataset

```

## MCP server setup

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

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/q6KmpnUfjNDxeE90N/builds/vk66LApeWrR5G8y7f/openapi.json