# Four-Day Week Jobs Scraper (`jobsapi/four-day-week-jobs-search-scraper`) Actor

Extracts verified reduced-hours jobs from the official 4dayweek.io public API.

- **URL**: https://apify.com/jobsapi/four-day-week-jobs-search-scraper.md
- **Developed by:** [Jobs API](https://apify.com/jobsapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.99 / 1,000 4 day week job records

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Four-Day Week Jobs Scraper

Extract complete public reduced-hours job records from the official, no-auth `4dayweek.io` v2 jobs API. The default `schedule=4_day_week` filter is source-provided evidence that the role belongs to the site's four-day-week collection.

### Input

| Field | Default | Description |
| --- | --- | --- |
| `query` | `""` | Optional full-text role, skill, or company query. |
| `category` | `""` | Optional category slug or comma-separated slugs. |
| `schedule` | `4_day_week` | Source schedule slug or comma-separated slugs. |
| `workArrangement` | `""` | Optional `remote`, `hybrid`, `onsite`, or comma-separated values. |
| `country` | `""` | Optional country filter. |
| `maxItems` | `25` | Maximum complete public API records, from 1 to 500. |
| `maxPages` | `10` | Pagination safety cap, from 1 to 50. |

```json
{
  "query": "",
  "schedule": "4_day_week",
  "workArrangement": "remote",
  "maxItems": 25,
  "maxPages": 10
}
```

### Output

Each item is built from a complete public API record and contains the title, employer, public employer profile, structured locations, schedule and weekly-hour bounds, work arrangement, salary when published, categories, role/level, contract type, skills, tools, markdown description with sections and readable text, requirements/responsibilities/benefits where headings expose them, dates, search filters, and canonical job URL. Source request receipts and run diagnostics are kept in KVS rather than duplicated in new dataset rows. Source fields that are absent are omitted. Records contain more than 20 populated meaningful fields.

Chrome comparison showed that a fresh public detail page can expose title, hours, schedule, location, and a short role/company description while gating the company identity, full description, requirements, benefits, and application link behind the site's Pro subscription. The API does not publish an employer application URL, so `application.available` and `application.urlPublished` are `false` and no `applyUrl` is fabricated.

The actor writes `OUTPUT_SUMMARY`, `REQUEST_RECEIPTS`, `RUN_DIAGNOSTICS`, `RUN_HEALTH`, and `OUTPUT` to the default key-value store. `OUTPUT.status` is platform state (`SUCCEEDED` or `FAILED`); `OUTPUT.resultStatus` is data disposition (`COMPLETE`, `LIMITED`, `SKIPPED`, `DEFERRED`, `NO_DATA`, or `FAILED`). Complete records already stored remain `SUCCEEDED` / `LIMITED` if a later write or finalization step fails. Diagnostics and dummy rows are never pushed to the dataset. Raw API objects and contact details are not emitted; contact-like text in public descriptions is redacted.

### Access policy

Requests use ordinary direct HTTPS with fixed timeouts, no proxy, no stealth or fingerprint changes, no alternate identity, and no retries. An explicit HTTP 401/403/429/451 response or human-verification/access-denial challenge stops the run, discards buffered rows, and reports `SUCCEEDED` / `SKIPPED`; HTTP 407, redirects, invalid JSON, or another unverified source/transport response is `DEFERRED`. A clean empty API response is `NO_DATA`; a fatal zero-row error is `FAILED` / `FAILED`. Rows gathered before a generic later failure may be stored as genuine jobs and reported `SUCCEEDED` / `LIMITED`.

# Actor input Schema

## `query` (type: `string`):

Optional full-text role, skill, or company query.

## `category` (type: `string`):

Optional category slug or comma-separated category slugs.

## `schedule` (type: `string`):

Schedule slug or comma-separated slugs. Defaults to source-verified four-day-week jobs.

## `workArrangement` (type: `string`):

Optional onsite, hybrid, remote, or comma-separated values.

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

Optional office or remote-allowed country.

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

Maximum complete public API records to save.

## `maxPages` (type: `integer`):

Pagination safety cap.

## Actor input object example

```json
{
  "query": "",
  "category": "",
  "schedule": "4_day_week",
  "workArrangement": "",
  "country": "",
  "maxItems": 25,
  "maxPages": 10
}
```

# Actor output Schema

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

No description

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

No description

## `requestReceipts` (type: `string`):

No description

## `diagnostics` (type: `string`):

No description

## `output` (type: `string`):

No description

## `health` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jobsapi/four-day-week-jobs-search-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("jobsapi/four-day-week-jobs-search-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 '{}' |
apify call jobsapi/four-day-week-jobs-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jobsapi/four-day-week-jobs-search-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/0y3pDo3hRJFK8k7cc/builds/Q0Fo0sOo52uT3F9s7/openapi.json