# NoFluffJobs Scraper: Poland Jobs, EUR Salary (`ceejobs/nofluffjobs-scraper`) Actor

Scrape No Fluff Jobs (nofluffjobs.com) listings into clean JSON: title, company, location, salary normalized to EUR/month, posting date, tags, optional full description. Pay per result, no subscription.

- **URL**: https://apify.com/ceejobs/nofluffjobs-scraper.md
- **Developed by:** [CEE Jobs](https://apify.com/ceejobs) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 25.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.70 / 1,000 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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## No Fluff Jobs Scraper — Poland job listings with salary

Extract No Fluff Jobs job listings with salary, location and posting date for Poland market
research, recruiting and lead generation.

### What you get

- Every job on nofluffjobs.com that matches your keywords, as one structured row each: title, company,
  location, employment type, posting date and the canonical job URL — exact matches only, never
  the board's "you might also like" filler.
- Salary normalized to gross **EUR per month** (`salary.minEurMonth` / `salary.maxEurMonth`)
  next to the raw label the board printed, so rows priced in different currencies sort together.
  No Fluff Jobs publishes a range on most postings, which is what makes this board worth scraping.
- A stable `id` of the form `nofluffjobs:<board job id>`, so repeat runs deduplicate against
  your own database instead of against a row number.

### Sample item

```json
{
  "id": "nofluffjobs:mid-software-engineer-python-guidewire-software-krakow-1",
  "url": "https://nofluffjobs.com/pl/job/mid-software-engineer-python-guidewire-software-krakow-1",
  "title": "Mid Software Engineer - Python",
  "company": "Guidewire Software",
  "companyUrl": null,
  "location": { "raw": "Kraków", "city": "Kraków", "country": "PL" },
  "remote": false,
  "employmentType": "FULL_TIME",
  "salary": {
    "min": 18500,
    "max": 22000,
    "currency": "PLN",
    "period": "month",
    "raw": "18 500 – 22 000 PLN / mies.",
    "minEurMonth": 4295,
    "maxEurMonth": 5107
  },
  "postedAt": "2026-07-29",
  "expiresAt": null,
  "description": null,
  "tags": ["Python", "FastAPI", "SQLAlchemy", "Docker", "Mid"],
  "source": {
    "board": "nofluffjobs",
    "boardJobId": "mid-software-engineer-python-guidewire-software-krakow-1",
    "scrapedAt": "2026-08-22T09:14:03.221Z"
  }
}
```

`remote` has three states, and `false` is not the same answer as `null`. It is `true` when the
board's own "fully remote" flag is set or the card's location reads as remote ("Zdalnie",
"Remote"), `false` when the board marks the posting as hybrid or office-based, and `null` when
the posting says nothing about it at all. Filter on `remote === true` for remote-only work, and
do not read a missing flag as an office job.

`description` and `expiresAt` are filled in only when `includeDetails` is on — they live on the
job's own page, not on the listing. `postedAt`, the salary and the skills tags come off the
listing itself, so the cheap run already dates every row. Anything the board did not publish is
`null`, never missing.

### Input

| Field | Type | Default | What it does |
| --- | --- | --- | --- |
| `keywords` | array of strings | `[]` | One search per keyword (job title, skill, company). Empty runs the board's default listing. |
| `location` | string | `""` | City or region, in the board's own language. location is matched client-side against the card's location text (the board has no stable location URL filter); accents are optional, so "krakow" finds Kraków. |
| `maxItems` | integer | `100` | Hard stop after this many jobs. This is the cost dial. |
| `includeDetails` | boolean | `false` | Also open each job's own page for description, expiry date and better salary data. Roughly 10x slower. |
| `postedWithinDays` | integer | `0` | Keep only jobs posted in the last N days. `0` disables the filter. |
| `startUrls` | array | `[]` | Listing URLs on nofluffjobs.com to crawl directly instead of building searches from `keywords`. |
| `extra` | object | `{}` | Board-specific filters. `region`: pl | cz | sk | hu (default pl) — the board's own country prefix. `category`: backend, frontend, fullstack, mobile, devops, testing, data, ai, security, … — crawls that category's listing instead of the region's front page, and combines with `keywords` when both are given. |
| `proxyConfiguration` | object | Apify proxy | Apify datacenter proxy groups only; residential groups and custom proxy URLs are rejected. |

Keywords are applied by the board, not by this actor: they become
`?criteria=keyword%3D<keyword>` on the listing URL, which No Fluff Jobs filters server-side.
That filter answers from the board's Polish index whatever `region` you ask for, so pair
`keywords` with `extra.category` — or leave `region` alone — if you want Czech, Slovak or
Hungarian rows. Each row's `location.country` is the country the board itself files the posting
under, not the region you typed, so a run never labels a Polish job as Czech.

### Pricing

$2 per 1,000 jobs, plus $2 per 1,000 when `includeDetails` is on. No subscription.

### Limitations

Public listing data only — no data behind a login. The crawler obeys nofluffjobs.com's
`robots.txt`, including for URLs you pass in `startUrls`, and runs on datacenter proxies without
any CAPTCHA or challenge circumvention: a challenge page is reported as an error, not retried
through another browser. Apify datacenter proxy groups only; residential groups and custom
proxy URLs are rejected before the run starts. Jobs the board removes between the listing page and the detail fetch
are skipped rather than shipped half-filled.

Descriptions are stripped of e-mail addresses, phone numbers and any line naming a contact
("Kontakt: …"), and capped at 20,000 characters, so no row carries a route to a named recruiter.
That is a filter on the description text, not a guarantee about every field the board prints.

Three things this board does that show up in the data.

- **Deferred salaries.** Some employers hold the range back until an interview. Those cards print
  "Sprawdź wynagrodzenie" and their rows carry a `null` salary rather than an invented one —
  about 30% of the rows on a busy category. The amounts are not in the page at all, hidden or
  otherwise.
- **Day rates.** Plenty of contract postings are quoted **per day**. Those rows keep their
  amounts, their currency and the board's own label, but ship `period: null` and leave
  `minEurMonth` / `maxEurMonth` `null` rather than report a day rate as a monthly wage twenty
  times too small. Read the `raw` label when you need to tell a day rate from an unpriced row.
- **Suggestion cards.** A keyword search that runs out of exact matches fills the rest of the page
  with "you might also like" postings answering a different search. This actor drops them, so a
  narrow keyword run returns fewer rows — and bills for fewer rows — than the page appears to
  show, and stops as soon as the real matches do.

`employmentType` is normalized to the vocabulary the job pages use, so a listing-only run and a
`includeDetails` run agree: the board's `b2b` becomes `CONTRACTOR` and `permanent` becomes
`FULL_TIME`, and anything else is passed through in upper case.

# Actor input Schema

## `keywords` (type: `array`):

One search per keyword; on boards without server-side search the keywords filter the full listing client-side (see the actor README).

## `location` (type: `string`):

City or region in the board's own language (e.g. Bratislava, Praha, Warszawa). Optional.

## `maxItems` (type: `integer`):

Stop after this many jobs. Controls cost: $2 per 1,000 jobs.

## `includeDetails` (type: `boolean`):

Adds description, expiry date and better salary data. Costs an extra $2 per 1,000 jobs and is slower (board-dependent, roughly 1.5–10×).

## `postedWithinDays` (type: `integer`):

Only keep jobs posted in the last N days. 0 = no filter.

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

Listing URLs from the board to crawl directly instead of keywords.

## `extra` (type: `object`):

See the README for the filters this board supports.

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

Apify datacenter proxy groups only; residential groups and custom proxy URLs are rejected. The datacenter pool is enough for this board.

## Actor input object example

```json
{
  "maxItems": 100,
  "includeDetails": false,
  "postedWithinDays": 0,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `jobs` (type: `string`):

No description

## `jobsCsv` (type: `string`):

No description

## `summary` (type: `string`):

No description

# 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 = {
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("ceejobs/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 = { "proxyConfiguration": { "useApifyProxy": True } }

# Run the Actor and wait for it to finish
run = client.actor("ceejobs/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 '{
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call ceejobs/nofluffjobs-scraper --silent --output-dataset

```

## MCP server setup

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