No Fluff Jobs Search Scraper

This Apify Actor collects publicly available No Fluff Jobs postings from the official nofluffjobs.com site. It uses the official HTTPS posting JSON endpoint and the official search page's structured SSR state. It does not use browser automation, residential proxies, third-party mirrors, or access-control bypasses.

What it returns

Each dataset item is a source-verified job record. When published by No Fluff, the record includes:

• stable posting reference and canonical detail URL;
• title, company, company URL/logo/size, category, seniority, and technology;
• every published location, city, province, address, country, coordinates, remote level, and workplace type;
• all published salary options, currencies, periods, contract types, holiday information, and disclosure status;
• description HTML and text, section headings, bullets, daily tasks, requirements, skills, methodology, benefits, equipment, and recruitment details;
• source record, field coverage, request receipts, and verification flags.

Missing source values are omitted. The Actor never writes null, blank, or placeholder fields and does not put diagnostics in the dataset. Structured diagnostics and run health are written to RUN_DIAGNOSTICS, RUN_SUMMARY, RUN_METADATA, and RUN_HEALTH in the default key-value store.

Modes

search is the default and accepts query, optional location, and language. Simple technology queries use the corresponding official category route; other searches use the official keyword search route.

single accepts one exact detail URL in url. multiple accepts exact detail URLs in urls. searchMultiple accepts an array such as { "query": "javascript", "location": "Warszawa" } in searches. startUrls accepts a mixture of official listing and detail URLs in startUrls.

All modes share maxItems, maxPages, maxCandidates, maxRequests, timeoutMs, and deadlineMs bounds. The default input is deliberately small so local QA completes quickly:

{
  "mode": "search",
  "query": "javascript",
  "language": "pl",
  "maxItems": 3,
  "maxPages": 1,
  "maxCandidates": 30,
  "maxRequests": 12,
  "timeoutMs": 15000,
  "deadlineMs": 150000
}

Local development

npm ci
npm run check
npm test
npx apify-cli validate-schema .actor/input_schema.json
npm run validate -- storage-validation

For a local Actor run, first confirm a new actor-relative storage directory is absent, set APIFY_LOCAL_STORAGE_DIR to that fresh relative path, and use apify run --resurrect --input-file INPUT.json. Do not use --purge or reuse a dataset directory.

Local and Apify Cloud runs use the same bounded official-source workflow and expose truthful localOnly provenance.

Source boundary and responsible use

Only ordinary direct HTTPS access to official nofluffjobs.com URLs is accepted. Search pages provide candidate slugs; each saved record is verified against the official posting API or the same posting's public SSR state after a non-blocking API parse/not-found response. HTTP 401, 403, 429, or 451, or visible source-authored denial, CAPTCHA, human-verification, or security-challenge content stops requests, discards staged rows, preserves receipts and diagnostics, and records SKIPPED. HTTP 407 and unverified transport failures are recorded as DEFERRED; the Actor does not change routes after those failures. The Actor uses no proxy, cookies, identity changes, fingerprint changes, retry, or custom user-agent. Use the data lawfully, respect the site's terms and robots directives, and do not use this Actor to collect candidate or recruiter personal data.