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

{
  "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.