# No Fluff Jobs Scraper (`reventadata/nofluffjobs-scraper`) Actor

Scrapes No Fluff Jobs IT job ads in Poland, Hungary, Czechia, Slovakia and Ukraine: title, company, skills, seniority, salary range and contract type, work mode, cities, posting date. Filter by keyword, category, level, contract, city and salary. No proxy needed.

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

## Pricing

from $1.00 / 1,000 jobs

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## No Fluff Jobs Scraper

> **Unofficial.** This Actor is not affiliated with, authorised by, endorsed by, or in any
> way officially connected to No Fluff Jobs. "No Fluff Jobs" is a trademark of its
> respective owner and is used here only to describe what this tool reads. It reads the same
> public pages a browser does.

Collects IT job ads from nofluffjobs.com with the pay range, contract type, seniority, skills,
work mode and office locations as separate fields, ready for a spreadsheet or a database.

### What does it do?

Searches No Fluff Jobs the way the site's own filters do and returns one row per job ad:
title, company, category, seniority, skill tags, pay range with currency and period, contract
type (B2B, permanent, mandate), remote/hybrid/onsite, cities with address and coordinates,
and the posting and renewal dates. Switch on **Include full job details** to also get the
description, requirements, daily tasks, benefits, company size and expiry date.

### Why use it?

- **Pay as numbers.** Salary comes as `salaryFrom`, `salaryTo`, `salaryCurrency` and
  `salaryPeriod` (Month, Hour or Day), not as text. Ads that reveal pay only at an interview
  stage are marked `salaryPublished: false` instead of being given a made-up range.
- **Filters the site really applies:** keyword or technology, 35 categories, seniority,
  contract type, city or work mode, and a salary amount.
- **Beyond the first 100 jobs.** One site search shows at most 100 jobs to a plain page
  request, so a larger run is split automatically by category, then seniority, then contract
  type, and duplicates are removed by the ad reference.
- **No proxy needed.** The Actor reads only the public search and job pages. It does not use
  the site's `/api/` paths, which its robots.txt disallows.

### How to use it

1. Add keywords or technologies to `searchQueries`, or leave it empty and use the filters.
2. Optionally set categories, seniority, contract types and cities (`remote` and `hybrid`
   work as city entries).
3. Set `maxItems` and run. Download JSON, CSV or Excel from the dataset.

#### Input

| Field | Type | Description |
|---|---|---|
| `searchQueries` | array | Keywords or technologies, one search each (for example `python`, `senior java developer`). |
| `categories` | array | Only these site categories (backend, devops, data, and so on). |
| `seniority` | array | trainee, junior, mid, senior, expert, lead. |
| `employmentTypes` | array | b2b, permanent, zlecenie. |
| `cities` | array | City slugs such as `warszawa`, plus `remote` or `hybrid`. Any match is kept. |
| `salaryAmount`, `salaryCurrency`, `salaryPeriod` | integer, string, string | Jobs whose published range includes this amount. This is the site's own match, not a minimum, and it also matches ads that reveal pay later. |
| `country` | string | Site market: `pl`, `hu`, `cz`, `sk`, `ua`. |
| `onlyWithSalary` | boolean | Drop ads without a published range. |
| `postedWithinDays` | integer | Only ads posted or renewed in the last N days. |
| `includeDetails` | boolean | One extra request per job for the full ad. |
| `maxItems` | integer | Most jobs to return. |

#### Sample input

```json
{
    "searchQueries": ["python"],
    "seniority": ["senior"],
    "onlyWithSalary": true,
    "maxItems": 20
}
```

#### Output

Each row holds `id`, `url`, `title`, `company`, `category`, `technology`, `seniority`,
`skills`, `jobLanguages`, `contractType`, `salaryFrom`, `salaryTo`, `salaryCurrency`,
`salaryPeriod`, `salaryPublished`, `salaryDisclosedAt`, `workMode`, `fullyRemote`,
`locations`, `provinces`, `postedAt`, `renewedAt`, `regions`, `search` and `scrapedAt`.
With `includeDetails`: `description`, `requirementsText`, `mustHaveSkills`,
`niceToHaveSkills`, `dailyTasks`, `benefits`, `officePerks`, `companySize`, `companyWebsite`,
`requiredLanguages`, `expiresAt`, `applyType` and `salaryTypes`.

### How much does it cost to scrape No Fluff Jobs?

Pay-per-event: **$0.001 per job ad** saved to the dataset (**$1.00 per 1,000 job ads**), plus **$0.00005** charged once when the run starts. No subscription. Only rows saved to the dataset are charged.

### Limits

- Each distinct search returns at most 100 jobs. A run that needs more is split as above; if a
  search is still cut off after splitting, the log names it and you can narrow it with cities
  or a keyword.
- `salaryAmount` matches the site's own definition, so results can include ads whose range
  merely contains the amount.
- Czechia and Slovakia show the same pool of jobs as Poland; Hungary and Ukraine add their own.

### Privacy and compliance

Rows carry public job-ad data: company names, titles, pay, locations of company offices and
dates, as the site shows them. Nothing behind a login is read. Job pages do not show the
application email address (applications go through the site's own form), so rows have none.
The site's terms restrict systematic downloading of its job database; you are responsible for
how you use the data and for complying with the site's terms and applicable law.

# Actor input Schema

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

Optional keywords or technologies, one search per entry, for example python, kubernetes or senior java developer. Words in one entry are combined. Leave empty to list jobs by the filters below only.

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

Optional. Only jobs in these No Fluff Jobs categories. Leave empty for every category.

## `seniority` (type: `array`):

Optional. Only jobs for these levels.

## `employmentTypes` (type: `array`):

Optional. Only jobs offering these contract types: B2B, permanent employment (UoP) or mandate contract (zlecenie).

## `cities` (type: `array`):

Optional. Site city slugs such as warszawa, krakow, wroclaw or budapest, plus remote or hybrid for work mode. A job matching any entry is kept. A slug the site does not know returns no jobs.

## `salaryAmount` (type: `integer`):

Optional. Only jobs whose published pay range includes this amount, in the currency and period below. Jobs that reveal pay only at an interview stage are also matched by the site. This is not a minimum.

## `salaryCurrency` (type: `string`):

Currency of the salary amount.

## `salaryPeriod` (type: `string`):

Whether the salary amount is per month or per hour.

## `country` (type: `string`):

Which No Fluff Jobs market to search. Poland is the main one; Czechia and Slovakia show the same pool of jobs as Poland, Hungary and Ukraine add their own.

## `onlyWithSalary` (type: `boolean`):

Keep only jobs whose pay range is shown on the ad. Jobs that reveal pay only at an interview stage are dropped.

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

Optional. Keep only jobs posted or renewed in the last N days, for monitoring new ads.

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

Also open each job page for the description, requirements, daily tasks, benefits and company size. Slower: one extra request per job.

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

Most jobs to return across all searches. One search URL can show the site's first 100 jobs; larger runs are split into narrower searches by category, seniority and contract type.

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

Not needed: the site is reachable without a proxy. Leave off unless you want to route requests through Apify Proxy.

## Actor input object example

```json
{
  "searchQueries": [
    "python"
  ],
  "salaryCurrency": "pln",
  "salaryPeriod": "month",
  "country": "pl",
  "onlyWithSalary": false,
  "includeDetails": false,
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `dataset` (type: `string`):

Items scraped from the target website.

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

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

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

```

## MCP server setup

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