# JobScout24 Scraper - Swiss Job Listings (`listingworks/jobscout24-ch-scraper`) Actor

Job postings from jobscout24.ch with title, employer, place, workload and posting date.

- **URL**: https://apify.com/listingworks/jobscout24-ch-scraper.md
- **Developed by:** [Yusuke Suda](https://apify.com/listingworks) (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.50 / 1,000 result items

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

## JobScout24 Scraper — Swiss job listings by keyword and town

JobScout24 is one of Switzerland's large job boards, run by JobCloud AG — the
same company behind jobs.ch and jobup.ch, but with its own listings and its own
search. This Actor turns its search results into a clean table: the job title,
the employer, the town, the workload, and when the posting went online.

Press Start. The defaults return the site's current list across Switzerland,
with no configuration needed.

### What a row looks like

```json
{
  "title": "Teamleitung Lernwerkstatt und Empfang 80 - 100 %",
  "company": "Bürgerspital Basel",
  "location": "Basel",
  "workload": "80-100%",
  "posted_at": "2026-09-22",
  "source_url": "https://www.jobscout24.ch/de/job/7fde7696-bbfe-448a-9913-ce9ba4a8ca6b/",
  "external_id": "10405545"
}
```

`company` is the employer as the list shows it, often a staffing agency. Contact
persons, email addresses and phone numbers are never collected — this Actor reads
the search results only and never opens the job text.

### When a posting went online

JobScout24's list shows an age, not a date: "New", "3 T" (days), "2 W" (weeks),
"1+M". `posted_at` is that age turned into a date on Swiss time:

| The list says | `posted_at` | Precise to |
|---|---|---|
| New | today | the day (it means posted within the last day) |
| 1 T … 6 T | 1 … 6 days ago | the day |
| 1 W … 4 W | 7 … 28 days ago | the week — a "2 W" posting is 14 to 20 days old |
| 1+M | 30 days ago | "a month or more" |

So `postedAfter` works to the day for the last week, which is what a daily or
weekly schedule needs, and to the week for older cutoffs.

### What people use it for

Tracking which companies in a town are hiring, week by week. Feeding a job
board or a newsletter with Swiss openings in a niche. Watching which staffing
agencies are recruiting for what. Research on the Swiss labour market that needs
structured rows rather than a page of links.

### Input

| Field | What it does |
|---|---|
| `searchTerms` | Keywords, e.g. `pflege`, `informatik`. Each keyword is its own search. Leave empty for everything. |
| `location` | A Swiss town as JobScout24 names it: `Winterthur`, `St. Gallen`, `Zürich`, `Genf`, `Baar ZG`. The site includes nearby towns. Leave empty for the whole country. |
| `postedAfter` | Only keep postings from this date on (ISO 8601). Handy for daily runs that should return just what is new. |
| `maxItems` | Hard stop, so your bill is predictable. |
| `proxyConfiguration` | Off by default. Most runs do not need one. |

### How much one run returns

JobScout24 serves 20 listings per page, plus a few promoted ones at the top and
bottom, and stops at page 100, so one search returns at most about 2,000
listings. To go beyond that, split by keyword or town across runs; duplicates —
including the promoted listings the site repeats on every page — are removed
within a run.

### Pricing

$3.00 per 1,000 listings, dropping to $1.50 per 1,000 on higher Apify plans,
plus $0.005 each time a run starts. Platform usage is not passed on to you.

You are charged for rows you actually receive. If you set a maximum charge for
the run, it stops cleanly at that limit instead of overshooting it.

### Scope and limits

Public listings only, from the search results pages (`/de/jobs/…` and
`/de/jobs-in-<town>/…`), which JobScout24's robots.txt allows. The pages it
disallows — accounts, applications, company profiles, the export feed — are
never requested, and neither is the job text. Salary, application deadline and
the job description are not on the list page, so nothing is read for them. The
catalogue-wide columns `salary_currency`, `salary_period` and `apply_url` still
ship, always empty, so that one parser works across every job Actor here.
`employment_type` is filled only where the card itself carries one ("Festanstellung",
"Temporär / Aushilfe") — rarely, so it is not in the table views.

JobScout24 ignores a region or place sent as a plain parameter and returns the
whole country instead. This Actor searches a town through the site's own town
pages and checks that the page it gets back is that town's, with the keyword and
order you asked for; if not, the run fails rather than returning rows you did
not ask for and charging you for them. A town the site does not know fails the
run.

If JobScout24 changes its page structure, the run goes red. It does not return
zero rows and report success — a silent scraper is worse than a broken one,
because you find out weeks later.

A run that is blocked or cut short partway also goes red, even though the rows
it did collect are in the dataset and yours to keep. Red here means "this is
not the complete answer", not "you lost the data" — on a schedule, a run that
quietly came back short is the thing you most need to hear about.

Every run also publishes the site's own result count next to the rows it
delivered, so you can see "60 rows of 9,969 the site reports" without going
back to the site to check. That number is what the site says, not a promise
about what one run returns.

### Same shape, other sites

This Actor shares its output shape with the jobs.ch Scraper and the jobup.ch
Scraper (the other two JobCloud boards, with their own listings) and the
Jobindex Scraper (Denmark). A parser you write for one keeps working on the
others, and on the countries added next.

### Support

Open an issue on this Actor with the run ID and your input. Answered within
one business day.

# Actor input Schema

## `searchTerms` (type: `array`):

Keywords to search for, e.g. pflege, informatik. Each keyword is its own search. Leave empty for all postings.

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

A Swiss town as JobScout24 names it (e.g. Winterthur, St. Gallen, Zürich, Genf, Baar ZG). The site includes nearby towns. Leave empty for all of Switzerland. A town the site does not know fails the run instead of returning unfiltered results.

## `postedAfter` (type: `string`):

Return only postings from this date on, e.g. 2026-09-20. The site shows an age ('New', '3 T', '2 W') rather than a date, so the cutoff works to the day for the last week and to the week before that.

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

Stop after this many postings. JobScout24 serves at most 100 pages (about 2,000 postings) per search, so larger numbers are reached with more keywords or towns.

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

Off by default. Turn on (residential, in the site's country) only if runs start getting blocked with 403/429.

## Actor input object example

```json
{
  "searchTerms": [],
  "location": "",
  "postedAfter": "",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

All Swiss job postings from this run: what the job is, who is hiring, and where.

## `employers` (type: `string`):

The same postings ordered around who is hiring.

## `runReport` (type: `string`):

Pages read, records delivered, errors, and the verdict (ok, degraded or broken).

# 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 = {
    "searchTerms": [],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("listingworks/jobscout24-ch-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 = {
    "searchTerms": [],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("listingworks/jobscout24-ch-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 '{
  "searchTerms": [],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call listingworks/jobscout24-ch-scraper --silent --output-dataset

```

## MCP server setup

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