NoFluffJobs Scraper — IT Jobs with Salaries
Pricing
Pay per usage
NoFluffJobs Scraper — IT Jobs with Salaries
Extract IT vacancies from NoFluffJobs, the Polish/CEE board where every posting must publish a salary range. Records include title, company, salary min/max, seniority, tech stack, remote status and apply URL. The best source for honest CEE salary data.
Scrape IT and business openings with mandatory salary transparency from NoFluffJobs — a single unified CEE/EU search index that already includes postings located in Poland, Czechia, Hungary, Slovakia, Ukraine, Netherlands and more (see the region field below for why there's nothing to select there).
What NoFluffJobs data does this scraper extract?
Each result is one flat JSON record per job posting:
| Field | Meaning |
|---|---|
id | Stable source-side identifier (alias of externalId) |
externalId | Stable source-side identifier |
source | Always "nofluffjobs" — which scraper produced this record |
title | Job title as posted |
company | Hiring company / organisation |
location | Location / duty station (may include remote hints) |
url | Direct link to the posting |
category | NoFluffJobs category slug the posting was fetched under |
seniority | Seniority levels listed on the posting |
skills | Must-have skills/tech stack |
postedAt | Posting date where the source provides it (ISO 8601) |
salary | Salary text where the source provides it, e.g. "B2B 25000–32000 PLN" |
salaryMin | Structured minimum salary (number, or null) |
salaryMax | Structured maximum salary (number, or null) |
salaryCurrency | Currency of salaryMin/salaryMax (or null) |
salaryPeriod | Always "month" when salary numbers are present (NoFluffJobs is always queried with a monthly period), else null |
snippet | Short description excerpt |
How to scrape NoFluffJobs with this Actor
- Click Try for free / Run — no login to the target site, no cookies, no proxies to configure.
- Adjust the input (keyword, filters,
maxItems) or keep the defaults. - Run it and export the dataset as JSON, CSV or Excel, or read it over the API.
Run it from your own code:
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_TOKEN>")run = client.actor("nomad-agent/nofluffjobs-scraper").call(run_input={"maxItems": 50})for item in client.dataset(run["defaultDatasetId"]).iterate_items():print(item["title"], "—", item["company"], item["url"])
Or a single HTTP call that runs the Actor and returns items in one response:
curl -X POST \"https://api.apify.com/v2/acts/nomad-agent~nofluffjobs-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \-H "Content-Type: application/json" \-d '{"maxItems": 50}'
Input
| Field | Type | Default | Notes |
|---|---|---|---|
categories | array (select, multi) | ["frontend"] | NoFluffJobs categories to fetch. Closed list verified live against the search API: backend, frontend, fullstack, mobile, embedded, testing, devops, architecture, security, game-dev, artificial-intelligence, data, sys-administrator, pm, agile, product-management, project-manager, business-intelligence, business-analyst, ux, support, erp, electronics, telecommunication, electrical-eng, automation, mechanics, sales, marketing, office-administration, hr, finance, consulting, customer-service, law, logistics, other, plus legacy alias ai-data. |
maxItems | integer | 100 | Maximum total number of postings to return across all categories. Set 0 for no limit. |
maxPages | integer | 5 | Maximum number of result pages to fetch per category (each page contains up to 50 postings). |
salaryCurrency | string (select) | "EUR" | Currency in which salary ranges are returned. NoFluffJobs converts all salaries to this currency. |
region | string (select) | "pl" | Kept for backward compatibility only. NoFluffJobs' public search API currently ignores this query parameter — verified by comparing result counts across pl/hu/cz/sk/ua/nl and an invalid value, all identical. All CEE/EU postings already come from one unified index regardless of this setting; "pl" is the only enum value today. |
postedSince | integer (days) | 0 | Drop postings older than N days (based on postedAt). 0 disables the filter. Postings with a missing/unparseable postedAt always pass through. |
titleExclude | array | [] | Drop postings whose title contains any of these strings (case-insensitive substring match). |
companyExclude | array | [] | Drop postings whose company name contains any of these strings (case-insensitive substring match). |
cacheTtlSeconds | integer | 1800 | Cache the upstream fetch in the key-value store for this many seconds; re-runs within the window skip the network call. Set 0 to disable. |
Output example
{"id": "rust-developer-ocado","externalId": "rust-developer-ocado","source": "nofluffjobs","title": "Rust Developer","company": "Ocado Technology","location": "Kraków (Hybrid)","url": "https://nofluffjobs.com/job/rust-developer-ocado","category": "backend","seniority": "Mid, Senior","skills": "Rust, Kubernetes, AWS","salary": "B2B 25000–32000 PLN","salaryMin": 25000,"salaryMax": 32000,"salaryCurrency": "PLN","salaryPeriod": "month","postedAt": "2026-06-29T10:15:17+00:00","snippet": "level=Mid, Senior; skills=Rust, Kubernetes, AWS; salary=B2B 25000–32000 PLN"}
Integrations
Export results as JSON, CSV or Excel; connect via Make, Zapier or n8n; call directly with run-sync-get-dataset-items; or plug into AI agents through the Apify MCP server.
Pricing
Pay per event: $0.05 per Actor start and $0.004 per job returned. 100 jobs ≈ $0.45. No subscription, no rental — you pay only for what you fetch.
Use cases
- Salary-transparency analytics for CEE
- Tech job boards and alert bots
- Compensation benchmarking by stack and seniority
- Sourcing in Poland and CEE
FAQ
Is it legal to scrape NoFluffJobs? This Actor reads only publicly available job postings — data any visitor can see without logging in. No personal data behind authentication is touched. Review the target site's terms and your local regulations for your specific use case.
Do I need an account on the target site? No. Postings are fetched from public pages/APIs — no login, cookies or session tokens.
How fresh is the data?
Every run fetches live listings. Results are cached for cacheTtlSeconds (default 30 min, set 0 to always hit the source live).
How many jobs can I get?
maxItems caps the run (set 0 where supported for no cap). Most sources paginate from newest to oldest.
Something broken or missing? Open an issue on the Actor's Issues tab — it is monitored and reliability fixes ship fast.