NoFluffJobs Jobs Scraper: nofluffjobs.com offers · Apify
NoFluffJobs Jobs Scraper avatar

NoFluffJobs Jobs Scraper

Pricing

from $0.34 / 1,000 job results

Go to Apify Store
NoFluffJobs Jobs Scraper

NoFluffJobs Jobs Scraper

Scrapes job offers from nofluffjobs.com, a Polish IT job board, through its public JSON API: salaries per contract type, skills with a must-have flag, seniority, locations, company and the full description. Same output schema as our other job portal actors.

Pricing

from $0.34 / 1,000 job results

Rating

0.0

(0)

Developer

DataWatcher

DataWatcher

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

14 hours ago

Last modified

Categories

Features

Limited permissions

Share

Scrape NoFluffJobs jobs from nofluffjobs.com, a Polish IT job board, and get the data as JSON, CSV or Excel, or fetch it with the Apify API: salaries, skills with a must-have flag, seniority, contract types, locations and company.

🔎 What does Nofluffjobs Jobs 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.

⭐ 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 (Aplikuj, Bluelionjob, Bulldogjob, Hollylist, Jobs-cz, Just Join IT, Pracuj, Reed, RocketJobs.pl, Skillshot, theprotocol.it) 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.00 per 1,000, and 24 of 30 add a start fee. You pay only for rows you get.
  • Salaries per month, plus the employer's own figures. A pay range given per hour also gets a monthly entry, and the employer's own figures stay as a second entry (isOriginal true). Each entry has min, max, currency, period, contractType and grossNet.
  • Skills with a must-have flag. Each skill comes with whether it is required, and whether the portal or the description named it.
  • Work mode as the site labels it. The work type follows the site's own remote, hybrid or onsite label, and remote offers list the countries a remote worker may live in (remoteCountries).
  • Company data: with details on, the company's size, address, profile link and number of active offers are added where the site shows them (read once per company per run).

🚀 How to scrape NoFluffJobs jobs

  1. Open the actor on Apify and click Try for free.
  2. Fill in keywords, cities and filters, or paste a nofluffjobs.com listing or offer URL into startUrls.
  3. Click Start.
  4. Download the NoFluffJobs jobs data as JSON, CSV or Excel from the Output tab, or fetch it with the Apify API.

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 Jobs Scraper to find senior Python offers in Warsaw or fully remote that show a salary. Show the 10 highest-paid, with company, salary, period and link.

🔌 Run it your way

  • Schedule it with Apify schedules.
  • Call it from the Apify API and its clients (Python, JavaScript).
  • Connect it to Make, n8n, Zapier, webhooks or Google Sheets.
  • Ask an AI agent to run it: see Use with AI agents (MCP).

⚙️ Input

Our job actors take 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
}
FieldDefaultNotes
maxResults50Offers in total; 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 read directly. The URL's market prefix (/pl/, /cz/...) decides the market of that search. The filters below still apply: rows that do not match are dropped. searchQueries is not applied with startUrls (a warning says so)
searchQueries–Keywords, one search per line (a technology or a job title); react OR angular runs both and merges the results. Empty: no keyword
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 the portal does not know gives a warning and no search for it. 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, production, logistics, legal, administration, consulting, education, healthcare, construction, hospitality
contractTypes–employment, b2b, mandate, specific-task, internship
workType–remote, hybrid, onsite, mobile. Matched by the actor on the rows it gets, not by the site
experience–intern, junior, mid, senior, expert, lead, manager, executive. NoFluffJobs words: intern is trainee, manager and executive are head
withSalaryOnlyfalseOnly offers that show a salary (matched by the actor on the rows it gets)
extractFullDetailsfalseOff: 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 read in full. A filter whose field the listing lacks still reads that offer's page to decide
maxConcurrency1Searches and detail pages processed in parallel
maxRequestsPerMinute60Request rate for the whole run
proxyConfigurationoffApify Proxy settings, useful when many detail pages are requested
maxRequestRetries2Retries after a failed request

The site has no mobile work type, so a mobile entry in workType matches nothing and a warning says so.

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.

ModeYou giveRowsOffer pages read
🟢 1. Default searchnothing (empty input)Offers across nofluffjobs.com, in the site's own order, up to maxResultsOnly with extractFullDetails on
🔤 2. Keyword searchsearchQueriesOne search per keywordOnly with extractFullDetails on
🎛️ 3. Filtered searchone or more filters, keywords optionalOffers matching the filtersOnly with extractFullDetails on
🔗 4. Listing / search URLstartUrls with a listing URLThat listing, as the site shows itOnly with extractFullDetails on
📄 5. One offer URLstartUrls with an offer URLThat one offerRead in full either way
🧩 6. URLs + filtersstartUrls plus filtersOnly rows matching the filtersOffer URLs in full; listed offers only with extractFullDetails on

Minimal input for each mode. Add "extractFullDetails": true to any of them for full rows.

{"maxResults": 3}
{"searchQueries": ["python"], "maxResults": 3}
{"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}

The site's own search applies locations, categories, experience and contractTypes; the actor matches workType and withSalaryOnly itself. With startUrls, the actor matches the filters on the rows.

📦 Output: NoFluffJobs jobs data

A row from one offer URL (shortened; empty fields left out):

{
"recordType": "job",
"schemaVersion": "1.4.1",
"source": "nofluffjobs",
"id": "XYGLWMEQ",
"url": "https://nofluffjobs.com/pl/job/senior-search-engineer-applied-search-ai-search-iteamly-remote",
"title": "Senior Search Engineer (Applied Search / AI Search)",
"company": {
"name": "iTeamly SP. Z O.O.",
"size": "10 - 49"
},
"locations": [
{
"city": "Kraków",
"region": "małopolskie",
"countryCode": "PL"
}
],
"workType": [
{
"type": "remote",
"remotePercent": 100,
"remoteCountries": ["PL"]
}
],
"categories": [
{
"value": "ai-ml",
"original": "Artificial Intelligence"
}
],
"contractTypes": [
{
"value": "b2b",
"original": "b2b",
"source": "portal"
}
],
"salaries": [
{
"contractType": "b2b",
"currency": "PLN",
"grossNet": "net",
"min": 25000,
"max": 35000,
"period": "month",
"isOriginal": true
}
],
"skills": [
{
"name": "Elasticsearch",
"required": true,
"source": "portal"
},
{
"name": "OpenSearch",
"required": true,
"source": "portal"
},
{
"name": "Vespa",
"required": true,
"source": "portal"
}
],
"benefits": ["Sport subscription", "Training budget", "Private healthcare"],
"dates": {
"posted": "2026-10-23",
"expires": "2026-11-22",
"scraped": "2026-11-13T12:03:02Z"
}
}

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)

EventPriceTrigger
Job result (job-scraped)$0.40 per 1,000One job offer returned by the Actor
Job details (job-details-scraped)$1.50 per 1,000Additional charge for a job offer whose detail page was read

No start fee: a run costs only the rows it returns.

Free plan: each run returns up to 1,000 results; upgrade your Apify plan for more.

🎯 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.

🩺 If a run fails

The run health (the RUN_HEALTH record, RUN_SUMMARY and the last line of the log) names the cause, for example site down: list request answered 500 x3. Find that start of the message in the table.

Error in the log / run healthWhat it meansWhat you do
site down: <request> answered 500, 502-504, 520-526The site is offline or has a fault. The actor waits longer between tries, then stops the run.Try again later.
blocked: <request> answered 401, 403, 1020 or a captcha pageThe site refused the request or showed a captcha page.The actor already retries once through the Apify proxy. If it still fails, turn on the Apify proxy in the input (use the RESIDENTIAL group if it is already on).
rate limited: <request> answered 429The site asks for fewer requests. The actor waits and slows down by itself.If it keeps happening, lower maxRequestsPerMinute.
gone: <request> answered 404, 410The page or offer was removed. The actor skips it and it is not charged.Nothing; this is normal.
network error: <request> failed with timeout (or connection error, DNS error)A timeout or a broken connection. The actor retries with a pause.Try again later.
wrong answer: <request> returned HTML instead of JSON (or an empty body)The site answered with a page that is not data (HTML instead of JSON, an empty body). The site has probably changed.Report it in the Issues tab; we fix it.

❓ FAQ

How many offers can I get?

As many as maxResults says. For a bigger slice, split it by city, category or filter and run several searches.

How do I export NoFluffJobs jobs to Excel or CSV?

Run the actor, open the Output tab and pick Excel or CSV in the export options. JSON, XML and HTML are there too, and the Apify API returns the same data.

How do I get NoFluffJobs salary data?

Offers that show pay have a salaries list with min, max, currency, period, contractType and grossNet. Turn on withSalaryOnly to get only offers that show pay.

Which work modes and countries does a remote offer show?

workType follows the site's own remote or hybrid label. A remote offer lists in remoteCountries the countries where a remote worker may live.

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.

🔗 Other Polish job scrapers (same schema)

🔗 Other job scrapers (same schema)

💬 Feedback and custom work

Need another portal, a field or a custom feed? Open an issue on the Issues tab.