Pracuj.pl Scraper: Poland Jobs and Salaries

What you get

Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API.

The main fields of each row:

• title
• company
• Workplace (location)
• Salary (salaryText)
• Level (positionLevels)
• Contract (contractTypes)
• Work mode (workModes)
• Posted (postedAt)
• Expires (expiresAt)
• Posting (url)

What people use it for

• Polish salary benchmarks: collect gross and net pay by contract type, level and city for any job title.
• B2B and IT rates: compare hourly and monthly B2B rates with the technologies each posting asks for.
• Recruitment agencies and HR: see which employers hire directly, with contract types and benefits.
• Job boards and newsletters: a daily feed of new Polish postings with posting and expiry dates.

Run it on Apify

1. Open pracuj-pl-scraper on Apify and sign in, or make an Apify account.
2. On the Input tab, fill in the fields listed below. The form opens with example values filled in.
3. Click Start. Rows appear on the Output tab while the run works.
4. Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
5. To run it again on a schedule, save the input as a task and add a schedule in the Apify Console.

What you can set

• Search terms (keywords): Job titles or words such as księgowa, kierowca or Java developer. One search per term; leave empty with a city to list every posting there.
• City (location): Optional city or town such as Warszawa, Kraków or Gdańsk. Applies to every search term.
• Distance (km) (distanceKm): How far from the city postings may be. pracuj.pl uses 0, 10, 20, 30, 50 or 100 km; other numbers are rounded down to one of those. Used only with a city. Default: 30.
• Posted within (postedWithin): Only postings published in that period. Options: Any time, Last 24 hours, Last 3 days, Last 7 days, Last 14 days, Last 30 days. Default: any.
• Position levels (positionLevels): Optional. Only these levels; empty means all. Options: Intern, Assistant, Junior, Mid, Senior, Expert, Team leader or coordinator, Manager, Director, President, Manual worker.
• Contract types (contractTypes): Optional. Only these contract types; empty means all. Options: Employment contract, Contract for specific work, Mandate contract, B2B, Replacement contract, Agency contract, Temporary employment, Internship.
• Work schedules (workSchedules): Optional. Only these schedules; empty means all. Options: Full time, Part time, Additional or temporary.
• Work modes (workModes): Optional. Only these work modes; empty means all. Options: On site, Hybrid, Remote, Mobile.
• With a salary only (salaryOnly): Only postings that show a salary. Default: false.
• Search URLs (searchUrls): Search result pages copied from your browser, for example https://www.pracuj.pl/praca/kierowca;kw/gdansk;wp?rd=30 . Filters in the URL are kept.
• Include posting details (includeDetails): Read each posting's page for the salary per contract type, the workplace address, category, technologies, responsibilities, requirements, benefits and the description. Switch it off for a faster run that reads only the search pages. Default: true.
• Maximum results (maxItems): The run stops after this many result rows. It also caps what one run can cost. Default: 100.
• Proxy configuration (proxyConfiguration): Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.

Example input

This is the input the actor is tested with every day.

{
  "keywords": [
    "księgowa"
  ],
  "location": "Warszawa",
  "includeDetails": true,
  "maxItems": 20
}

Run it from Python

The official apify-client package starts the run, waits for it and reads the rows. It needs your own Apify API token.

# pip install apify-client
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")  # your own API token, from the Apify Console
run_input = {
    "keywords": ["księgowa"],
    "location": "Warszawa",
    "includeDetails": True,
    "maxItems": 20,
}
run = client.actor("v0iddo/pracuj-pl-scraper").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Limits

• One search runs per search term, with the city, distance and filters you chose. Pasted search URLs keep their own filters. Postings are unique by ID across the whole run.
• One row is one posting. A posting offered in several towns lists them all in locations; location is the first, and the address fields are those of the first workplace.
• salaryText is the salary as the search shows it. salaryMin, salaryMax, salaryCurrency, salaryInterval (month or hour) and salaryKind (gross, net or net plus VAT) come from the posting page with details on (salaries lists them per contract type) and are read from salaryText otherwise.
• positionLevels, contractTypes, workSchedules and workModes are in English (for example junior, B2B, full time, remote); category, the posting's own text and the summary stay in Polish as published.
• With posting details on, each posting is read once more for the salary per contract type, the address with coordinates, the category, technologies, responsibilities, requirements, nice to have, benefits and the description. directEmployer is false for postings by a recruitment agency.
• Contact phone numbers and recruiter names are not collected. E-mail addresses, phone numbers and handles are removed from the text.
• Not affiliated with pracuj.pl or Grupa Pracuj.
• Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
• The actor reads only pages that the site's robots.txt leaves open to automated access.
• Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
• Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Questions

Do I need an account on pracuj.pl, cookies or an API key?

No. The actor reads only what every visitor of pracuj.pl can see, without logging in. You only need an Apify account to start it.

How many results can one run return?

Up to 10,000 rows per run. Without a limit it stops at 100. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.

Why did my run return no results?

The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

More

• Computrabajo Scraper: LATAM Jobs and Salaries
• Instahyre Jobs Scraper: India Jobs, Skills
• All our scrapers on the Apify Store