NoFluffJobs Scraper

Scrape job offers from nofluffjobs.com, a Polish IT job board, into clean JSON, CSV or Excel: salaries (also normalised per month), skills with a must-have flag, seniority, contract types, locations and company. No browser, no login: it uses nofluffjobs.com's own public JSON API.

🔎 What does NoFluffJobs Scraper do?

• Searches nofluffjobs.com by keywords, cities, categories, work type, experience level, contract type and "with salary only", or reads any listing or offer URL you paste.
• Returns one row per offer. With extractFullDetails on, each offer's own page is read too: full description (text and HTML), skills, benefits, languages and company profile.
• Runs on a schedule for daily new-job feeds, from the API, or from an AI agent.

⭐ Why this one

1️⃣ One schema across job portals. All our job actors share one output schema and one input schema. Build your pipeline once: our other job actors (Just Join IT, Bulldogjob, RocketJobs.pl, theprotocol.it, Hollylist) take the same input and return the same fields, so adding a portal means changing the actor name, not your code.

• Low price, no start fee. $0.40 per 1,000 offers; the median nofluffjobs.com scraper charges $2.50, and 19 of 23 add a start fee. You pay only for rows you get.
• Salaries per month, plus the employer's own figures. Each pay range starts with a monthly entry; a pay per hour or day also keeps the employer's own figures as a second entry (isOriginal true). Each entry has min, max, currency, period, contractType and grossNet.
• Skills with a must-have flag. Every skill comes with whether it is required, and whether the portal or the description named it.
• Filters buyers ask for: search words, locations, categories, work type, experience level, contract type and "with salary only". Or paste any nofluffjobs.com listing or offer URL.
• Company data: with details on, each row has the company's size, profile link and number of active offers (read once per company per run).
• Honest runs: a run summary and a health status. A search that fails writes an unbilled diagnostic row instead of silently returning nothing.
• Fast and cheap: public JSON API, no browser.

Data

This actor returns only what the site shows publicly at run time. We don't store or keep that data and are not its controller — you decide how you use it.

This is an independent tool, not affiliated with or endorsed by nofluffjobs.com; trademarks belong to their owners. It reads only public job pages: no login, no recruiter accounts. You are responsible for following nofluffjobs.com's terms and data-protection law (GDPR and others).

🤖 Use with AI agents (MCP)

AI assistants (Claude, ChatGPT, Cursor…) can run this actor through Apify's MCP server. Connect the server in your assistant, then ask, for example:

Use the NoFluffJobs Scraper to find senior Python offers in Warsaw or fully remote that show a salary. Show the 10 best-paid, with company, salary, period and link.

⚙️ Input

Every job actor of ours takes the same inputs. Example: Python offers in Warsaw, B2B or employment, remote or hybrid, mid or senior, with full details:

{
  "searchQueries": ["python"],
  "locations": ["Warszawa"],
  "contractTypes": ["b2b", "employment"],
  "workType": ["remote", "hybrid"],
  "experience": ["mid", "senior"],
  "maxResults": 50,
  "extractFullDetails": true
}

Field	Default	Notes
maxResults	50	Offers in total. 0 = no limit (the run timeout still applies)
startUrls	–	nofluffjobs.com listing pages (https://nofluffjobs.com/pl/devops) or offer pages (https://nofluffjobs.com/pl/job/...). A listing URL is read as that listing; an offer URL is always read from its own page. The URL's market prefix (/pl/, /cz/...) decides the market of that search. searchQueries is not applied (a warning says so). The filters below still apply: rows that do not match are dropped
searchQueries	–	Keywords, one search per line (a technology or a job title); react OR angular runs both and merges the results. Empty: every offer
locations	–	Polish city names (about 40); accents and case do not matter (Krakow = Kraków = KRAKÓW), English spellings (Warsaw, Cracow) also work. A city nofluffjobs.com does not know gives a warning and no search for it, never an unfiltered search. All cities go in one search (any of them). Empty: anywhere
categories	–	backend, frontend, fullstack, mobile, devops, data, ai-ml, testing, security, it-admin, support, embedded, gamedev, erp, architecture, project-management, product, ux-ui, business-analysis, sales, marketing, hr, finance, customer-service, engineering, logistics, legal, administration, consulting
contractTypes	–	employment, b2b, mandate, specific-task, internship
workType	–	remote, hybrid, onsite
experience	–	intern, junior, mid, senior, expert, lead, manager, executive
withSalaryOnly	false	Only offers that show a salary
extractFullDetails	false	Off: listing-level rows, cheaper and faster. On: each offer's own page (and its company, once per run) is read for the description, skills, benefits, languages and company details. An offer URL is always read in full
maxConcurrency	1	Searches and detail pages processed in parallel
maxRequestsPerMinute	60	Request rate for the whole run
proxyConfiguration	off	Apify Proxy settings, useful when many detail pages are requested
maxRequestRetries	2	Retries after a failed request

One job offered in several offices is one row; its other office links are in extensions.allOfferUrls.

🧭 Input modes: what you give, what you get

One actor, six ways to use it. The mode follows from what you fill in.

Mode	You give	Rows	Offer pages read
🟢 1. Default search	nothing (empty input)	Offers across all of nofluffjobs.com, in the site's own order, up to maxResults	Only with extractFullDetails on
🔤 2. Keyword search	searchQueries	One search per keyword	Only with extractFullDetails on
🎛️ 3. Filtered search	one or more filters, keywords optional	Offers matching the filters	Only with extractFullDetails on
🔗 4. Listing / search URL	startUrls with a listing URL	That listing, as the site shows it	Only with extractFullDetails on
📄 5. One offer URL	startUrls with an offer URL	That one offer	Always (a full row either way)
🧩 6. URLs + filters	startUrls plus filters	Only rows matching the filters	Offer URLs always; listed offers only with extractFullDetails on

Minimal input for each mode (real inputs from our test runs). Add "extractFullDetails": true to any of them for full rows.

🟢 1. Default search

{"maxResults": 3}

🔤 2. Keyword search

{"searchQueries": ["python"], "maxResults": 3}

🎛️ 3. Filtered search

{"searchQueries": ["python"], "locations": ["Warszawa"], "contractTypes": ["b2b", "employment"], "workType": ["remote", "hybrid"], "experience": ["mid", "senior"], "maxResults": 3}

🔗 4. Listing / search URL

{"startUrls": [{"url": "https://nofluffjobs.com/pl/devops"}], "maxResults": 3}

📄 5. One offer URL

{"startUrls": [{"url": "https://nofluffjobs.com/job/senior-sre-acdc-platform-infrastructure-automation-link-group-remote?lang=pl"}]}

🧩 6. URLs + filters

{"startUrls": [{"url": "https://nofluffjobs.com/pl/devops"}, {"url": "https://nofluffjobs.com/job/senior-sre-acdc-platform-infrastructure-automation-link-group-remote?lang=pl"}], "categories": ["devops"], "experience": ["senior"], "withSalaryOnly": true, "maxResults": 3}

With details off, no offer page is read to check a filter: a row the listing alone cannot confirm is left out, and a warning in the run log says how many. Turn on extractFullDetails to check them.

📦 Output

A real row from a keyword search with details on (shortened; empty fields left out):

{
  "recordType": "job",
  "source": "nofluffjobs",
  "id": "EEJXFOGR",
  "url": "https://nofluffjobs.com/pl/job/senior-automation-engineer-python-ai-scalo-krakow",
  "title": "Senior Automation Engineer (Python, AI)",
  "company": {
    "id": "scalo-sfruv7ym",
    "name": "Scalo",
    "profileUrl": "https://nofluffjobs.com/company/scalo-sfruv7ym",
    "size": "500 - 999",
    "activeOffersCount": 203
  },
  "locations": [{"city": "Kraków", "region": "małopolskie", "countryCode": "PL"}],
  "workType": [{"type": "remote", "remotePercent": 100, "remoteCountries": ["PL"]}],
  "categories": [{"value": "backend", "original": "Backend"}],
  "experience": {"levels": [{"value": "senior", "original": "Senior"}]},
  "contractTypes": [{"value": "b2b", "original": "b2b"}],
  "salaries": [
    {"contractType": "b2b", "currency": "PLN", "grossNet": "net", "min": 21000, "max": 22680, "period": "month", "isOriginal": false},
    {"contractType": "b2b", "currency": "PLN", "grossNet": "net", "min": 125, "max": 135, "period": "hour", "isOriginal": true}
  ],
  "skills": [
    {"name": "Python", "required": true, "source": "portal"},
    {"name": "REST API", "required": true, "source": "portal"},
    {"name": "Scrum", "required": true, "source": "description"}
  ],
  "benefits": ["Sport subscription", "Training budget", "Private healthcare"],
  "languages": {"offer": "pl", "requirements": [{"code": "en", "required": true}, {"code": "pl", "required": true}]},
  "description": {"text": "…", "html": "…"},
  "dates": {"posted": "2026-09-25", "renewed": "2026-10-09", "expires": "2026-10-25", "scraped": "2026-10-09T07:18:56Z"},
  "extensions": {"remoteInterview": false, "mainTechnology": "Python", "contractStart": "ASAP"}
}

Missing data is null, never a guess.

Run status. After each run, open the run's key-value store (Storage tab) to see how it went:

• RUN_HEALTH: ok, or degraded with the reason (no rows, a failed request, a warning, or a row that broke a data rule).
• RUN_SUMMARY: the run's numbers: rows, requests, retries, failed requests, warnings and billed events.

💰 Pricing (Pay-Per-Event)

Event	Price	Trigger
Result row (job-scraped)	$0.0004 (= $0.40 / 1,000)	Per offer returned
Details row (job-details-scraped)	+$0.0015 (= +$1.50 / 1,000)	Per offer whose own page was read (extractFullDetails on, or an offer URL)

No start fee: a run costs only the rows it returns. Diagnostic rows are never billed. Example: 1,000 offers with details = $0.40 + $1.50 = $1.90.

🎯 Use cases

• Track new IT openings for a role or stack on a daily schedule.
• Feed a job board aggregator or a personal job-search dashboard.
• Compare pay by contract type, city and experience level, in the employers' own currencies.
• Market research: which skills and seniority levels are in demand.
• Lead lists of hiring companies.
• Run the same pipeline over several Polish job portals, since they share one schema.

❓ FAQ

How many offers can I get?

As many as maxResults says (0 = no limit). For a bigger slice, split it by city, category or filter and run several searches.

Why is the salary empty for some offers?

Not every employer publishes pay. Then salaries is an empty list, never a guess. Turn on withSalaryOnly to get only offers with a salary.

What is the monthly salary?

Each pay range starts with a monthly item (period "month"). If the employer gives pay per hour, day, week or year, we compute it: hour × 168, day × 21, week × 52 / 12, year / 12, rounded to a whole unit. The employer's own figures follow it with isOriginal true.

Can I combine it with other portals?

Yes. All our job actors share one output schema and one input schema, so rows from different portals fit one table. See the list below.

Can I run it on a schedule, through the API or from an AI agent?

Yes to all three: use Apify schedules, the Apify API and clients, or the MCP server (see "Use with AI agents" above).

What if my search finds nothing?

You pay nothing: no rows, no charge, and RUN_HEALTH says degraded (no rows). If the search failed (the site did not answer), you also get one unbilled diagnostic row (recordType "diagnostic") with the search and the reason in errorMessage.

🔗 Other Polish job scrapers (same schema)

• Just Join IT Jobs Scraper
• Bulldogjob Jobs Scraper
• RocketJobs.pl Jobs Scraper
• theprotocol.it Jobs Scraper
• Hollylist Jobs Scraper (US entertainment jobs)

💬 Feedback

Found a missing field or a bug? Open an issue on the Issues tab.