# NoFluffJobs Jobs Scraper (`datawatcher/nofluffjobs-scraper`) Actor

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.

- **URL**: https://apify.com/datawatcher/nofluffjobs-scraper.md
- **Developed by:** [DataWatcher](https://apify.com/datawatcher) (community)
- **Categories:** Jobs
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.34 / 1,000 job results

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

## Nofluffjobs Jobs Scraper

Scrape **NoFluffJobs jobs** from [nofluffjobs.com](https://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](https://apify.com/datawatcher/aplikuj-scraper), [Bluelionjob](https://apify.com/datawatcher/bluelionjob-scraper), [Bulldogjob](https://apify.com/datawatcher/bulldogjob-scraper), [Hollylist](https://apify.com/datawatcher/hollylist-scraper), [Jobs-cz](https://apify.com/datawatcher/jobs-cz-scraper), [Just Join IT](https://apify.com/datawatcher/justjoin-scraper), [Pracuj](https://apify.com/datawatcher/pracuj-scraper), [Reed](https://apify.com/datawatcher/reed-scraper), [RocketJobs.pl](https://apify.com/datawatcher/rocketjobs-scraper), [Skillshot](https://apify.com/datawatcher/skillshot-scraper), [theprotocol.it](https://apify.com/datawatcher/theprotocol-scraper)) 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:

```text
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)](#-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:

```json
{
  "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; 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 |
| `withSalaryOnly` | `false` | Only offers that show a salary (matched by the actor on the rows it gets) |
| `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 read in full. A filter whose field the listing lacks still reads that offer's page to decide |
| `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 |

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.

| Mode | You give | Rows | Offer pages read |
| --- | --- | --- | --- |
| 🟢 **1. Default search** | nothing (empty input) | Offers across 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 | Read in full either way |
| 🧩 **6. URLs + filters** | `startUrls` plus filters | Only rows matching the filters | Offer URLs in full; listed offers only with `extractFullDetails` on |

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

#### 🟢 1. Default search

```json
{"maxResults": 3}
```

#### 🔤 2. Keyword search

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

#### 🎛️ 3. Filtered search

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

#### 🔗 4. Listing / search URL

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

#### 📄 5. One offer URL

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

#### 🧩 6. URLs + filters

```json
{"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):

```json
{
  "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)

| Event | Price | Trigger |
| --- | --- | --- |
| Job result (`job-scraped`) | $0.40 per 1,000 | One job offer returned by the Actor |
| Job details (`job-details-scraped`) | $1.50 per 1,000 | Additional 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 health | What it means | What you do |
|---|---|---|
| `site down: <request> answered 500, 502-504, 520-526` | The 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 page | The 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 429` | The site asks for fewer requests. The actor waits and slows down by itself. | If it keeps happening, lower `maxRequestsPerMinute`. |
| `gone: <request> answered 404, 410` | The 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)

- [Aplikuj Job Scraper](https://apify.com/datawatcher/aplikuj-scraper)
- [Bluelionjob Jobs Scraper](https://apify.com/datawatcher/bluelionjob-scraper)
- [Bulldogjob Jobs Scraper](https://apify.com/datawatcher/bulldogjob-scraper)
- [Just Join IT Jobs Scraper](https://apify.com/datawatcher/justjoin-scraper)
- [Pracuj Job Scraper](https://apify.com/datawatcher/pracuj-scraper)
- [RocketJobs.pl Jobs Scraper](https://apify.com/datawatcher/rocketjobs-scraper)
- [Skillshot Jobs Scraper](https://apify.com/datawatcher/skillshot-scraper)
- [theprotocol.it Jobs Scraper](https://apify.com/datawatcher/theprotocol-scraper)

### 🔗 Other job scrapers (same schema)

- [Hollylist Jobs Scraper](https://apify.com/datawatcher/hollylist-scraper)
- [Jobs-cz Jobs Scraper](https://apify.com/datawatcher/jobs-cz-scraper)
- [Reed Jobs Scraper](https://apify.com/datawatcher/reed-scraper)

### 💬 Feedback and custom work

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

# Changelog

This Actor's version history is a separate document: https://apify.com/datawatcher/nofluffjobs-scraper/changelog.md

# Actor input Schema

## `maxResults` (type: `integer`):

Maximum number of offers returned, in total. 0 = no limit (the run timeout still applies). Free plan Apify users get at most 1000 offers per run, whatever is set here (paying users have no cap).

## `startUrls` (type: `array`):

URLs from which the actor starts scraping, instead of a search: a listing/search URL is read as that listing, a specific offer URL is read directly. locations, categories, contractTypes, workType, experience and withSalaryOnly still apply: rows that do not match are dropped. searchQueries is not applied (a warning says so). NoFluffJobs search pages (the filters in the URL path and ?criteria= are read exactly as given, nothing is added to them) or job pages (https://nofluffjobs.com/pl/job/<slug>). The URL's own market prefix (/pl/, /cz/...) decides the market of that search.

## `searchQueries` (type: `array`):

Keywords to search for, one search per line (a technology or a job title). Empty - every offer. `react OR angular` runs both and merges the results.

## `locations` (type: `array`):

Only offers in these cities, written as normal city names; accents and case do not matter (Krakow = Kraków = KRAKÓW). A city the portal does not know gives a warning and no search for it, never an unfiltered search. Empty - anywhere. Polish cities only (about 40 of them); English spellings (Warsaw, Cracow) also work. All cities go in one search (any of them).

## `categories` (type: `array`):

Only offers in these categories (the output's `categories[].value` values). Empty - all.

## `contractTypes` (type: `array`):

Only offers that allow one of these contracts (the output's `contractTypes` values). Empty - all.

## `workType` (type: `array`):

Only offers with one of these work types (the output's `workType[].type` values). Empty - all. Applied to the rows after they arrive, not by the site. The site has no `mobile` value: it is ignored (a warning says so); with only that value, no search is made.

## `experience` (type: `array`):

Only offers for these experience levels (the output's `experience.levels[].value` values). Empty - all. NoFluffJobs words: `intern` is trainee, `manager` and `executive` are head.

## `withSalaryOnly` (type: `boolean`):

Only offers that show a salary (the output's `salaries` is not empty). Off - all offers. Applied to the rows after they arrive, not by the site.

## `extractFullDetails` (type: `boolean`):

Fetch each offer's own page (and its company once per run) and return the full data: the description, skills, benefits, languages, company details. Off - listing-level data only, cheaper and faster. An offer start URL is always read. A filter whose field the listing lacks still reads that offer's page to decide.

## `maxConcurrency` (type: `integer`):

Maximum number of searches/details processed in parallel.

## `maxRequestsPerMinute` (type: `integer`):

Maximum HTTP request rate, for the whole run.

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

Proxy settings, especially useful when many detail pages are requested.

## `maxRequestRetries` (type: `integer`):

Number of retries after a failed HTTP request.

## Actor input object example

```json
{
  "maxResults": 10,
  "searchQueries": [
    "python"
  ],
  "withSalaryOnly": false,
  "extractFullDetails": false,
  "maxConcurrency": 1,
  "maxRequestsPerMinute": 60,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "maxRequestRetries": 2
}
```

# Actor output Schema

## `results` (type: `string`):

One row per item; a search that failed completely adds one unbilled recordType "diagnostic" row.

## `runSummary` (type: `string`):

Rows, requests and budget, retries, failures, early stop, warnings, billing events, data-rule problems.

## `runHealth` (type: `string`):

{status, reason}: ok, degraded, or failed (health-check mode only).

# 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 = {
    "maxResults": 10,
    "searchQueries": [
        "python"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("datawatcher/nofluffjobs-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 = {
    "maxResults": 10,
    "searchQueries": ["python"],
}

# Run the Actor and wait for it to finish
run = client.actor("datawatcher/nofluffjobs-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 '{
  "maxResults": 10,
  "searchQueries": [
    "python"
  ]
}' |
apify call datawatcher/nofluffjobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,datawatcher/nofluffjobs-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/gg28cXFMkOZibcBlT/builds/G418Q6KiQwmovzeF8/openapi.json