jobs.ch Scraper — Swiss job listings by keyword, region and town

Extract job postings from jobs.ch (Switzerland) by keyword and location: title, employer, place, employment type, workload, posting date, URL, newest first.

Three rows from a real run

Title	Employer	Location	Posted
Compensation Specialist	LGT Capital Partners AG	Pfäffikon	2026-10-09T06:00:00+02:00
Pflanzenschutzberater/-in für die Nord-Ostschweiz	Schneiter AGRO AG	Seon	2026-10-09T06:00:00+02:00
Applied AI Engineer - Mission à 100%	SpeciTec SA	Genève	2026-10-13T07:54:05+00:00

A run with maxItems: 10 on 2026-10-13 returned 10 postings in 5 seconds and would cost about $0.04 at the current price. Full fields for every row are shown below.

jobs.ch is Switzerland's largest job site. This Actor turns its search results into a clean table: the job title, the company, where it is, the employment type and workload, and when it was first posted.

Press Start. The defaults return the newest listings across Switzerland, with no configuration needed.

What a row looks like

{
  "title": "Software Engineer Backend (80-100%)",
  "company": "Beispiel AG",
  "location": "Zürich",
  "employment_type": "Permanent position",
  "workload": "80-100%",
  "posted_at": "2026-09-15T08:00:00+02:00",
  "source_url": "https://www.jobs.ch/de/stellenangebote/detail/…",
  "external_id": "5d3f9c2a-…"
}

Company names are included where jobs.ch shows them (a few listings are posted anonymously and come back with an empty company). Business names only: where the site marks the advertiser as a private person, or the name on the card is or contains a person's name (a sole trader's trade name), the field is left empty. Contact persons, email addresses and phone numbers are never collected — this Actor reads the search results only and never opens the job text.

Every row also carries source_site and scraped_at.

Field	What it holds	How often it is filled
title, company, location	Job title; Employer; Location	Always
employment_type	Employment type	About 9 in 10 (86 of 100)
workload	Workload	Always
posted_at	Posted	Always
source_url, external_id	Posting URL; Posting ID	Always
application_deadline, company_url, company_rating, workplace_postal_code, workplace_address, latitude, longitude	Catalogue-wide columns; jobs.ch's list does not show them	Always empty here

Fill rates are from a 100-row run on 28 September 2026.

What people use it for

Tracking which companies in a region or a town are hiring, week by week. Feeding a job board or a newsletter with Swiss openings in a niche. Watching a competitor's hiring. And research on the Swiss labour market that needs structured rows rather than a page of links.

Input

Field	What it does
searchTerms	Keywords. jobs.ch search is semantic, so a broad term returns related jobs too. Leave empty for everything.
location	One of jobs.ch's regions (by name in German, French or English, or by its ID), a canton (a code such as BE, or Kanton Bern, Canton de Berne, Canton of Bern), or a town name such as Lugano. A bare name such as Bern is searched as a town, not as the canton. Leave empty for the whole country.
postedAfter	Only keep listings first posted on or after this date (ISO 8601). Handy for daily runs that should return just what is new.
sinceDays	The same, as a rolling window: 1 keeps yesterday and today, 7 the last week. Set it once on a scheduled task and never edit the date again.
maxItems	Hard stop, so your bill is predictable.
proxyConfiguration	Off by default. Most runs do not need one.

How much one run returns

jobs.ch serves 20 listings per page and stops at page 100, so one search returns at most 2,000 listings. To go beyond that, split by keyword, region or canton across runs; duplicates 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.

Daily new listings

Make a task from this Actor, set sinceDays to 1 with your search, and schedule it each morning. Every run then returns only what was posted since the previous day, in the same columns as a full run. The list is read newest first, so the run stops once the postings are older than the cutoff. A daily task for informatik in Zürich returned 12 new postings on 2 October 2026 and left out 51 older ones.

How this compares

Other jobs.ch Actors are on the Store. Checked on 2 October 2026 against the two most used, from their own Store descriptions and input forms:

• Results page only. One of them can open each posting for its full details. This Actor never opens a posting: it reads the search results only.
• No personal data. Neither advertises contact persons. This Actor collects no contact person, e-mail address or phone number; company is the employer's name only.
• One price per row. One of them charges a separate event for each posting it opens, on top of the listed result. Here every row costs the same, and you pay only for rows you receive.
• Daily new postings. Both have a publication-date filter. Here sinceDays is a rolling window you set once on a scheduled task.

Scope and limits

Public listings only, from the search results page. Salary, application deadline, remote flag, category and the job text are not on that page, so nothing is read for them. The catalogue-wide columns salary_min, salary_max, salary_currency, salary_period, employment_type and apply_url still ship, always empty, so that one parser works across every job Actor here; remote and categories are left out of the row entirely. Use source_url to reach the posting on jobs.ch.

jobs.ch answers an unknown town with an empty result rather than an error, and silently drops filters it does not understand. This Actor checks that the filters jobs.ch echoes back match the ones you asked for, and fails the run if they do not, rather than returning rows you did not ask for and charging you for them. Because an unknown town and a town with no matching jobs look the same, a town that returns nothing fails the run with a message saying so.

If jobs.ch 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 jobup.ch Scraper (French-speaking Switzerland, a separate board with its 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.