# jobup.ch Scraper - Romandie & Swiss Job Listings by Region (`listingworks/jobup-ch-scraper`) Actor

Scrape jobup.ch listings: title, company, town, region, employment type, workload and posting date. Sister site of jobs.ch for French-speaking Switzerland. No proxy needed, one flat price per result, no contact details.

- **URL**: https://apify.com/listingworks/jobup-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

## jobup.ch Scraper — Swiss job listings from French-speaking Switzerland

jobup.ch is the leading job site of French-speaking Switzerland, and the
sister site of jobs.ch (both are run by JobCloud). 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

```json
{
  "title": "Ingénieur logiciel backend (80-100%)",
  "company": "Exemple SA",
  "location": "Lausanne",
  "employment_type": "Permanent position",
  "workload": "80-100%",
  "posted_at": "2026-09-15T08:00:00+02:00",
  "source_url": "https://www.jobup.ch/fr/emplois/detail/…",
  "external_id": "5d3f9c2a-…"
}
```

Company names are included where jobup.ch shows them (a few listings are
posted anonymously and come back with an empty `company`). Contact persons,
email addresses and phone numbers are never collected — this Actor reads the
search results only and never opens the job text.

### What people use it for

Tracking which companies in Geneva, Vaud or the rest of Romandie are hiring,
week by week. Feeding a job board or a newsletter with openings in
French-speaking Switzerland. 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, in French or any other language. jobup.ch search is semantic, so a broad term returns related jobs too. Leave empty for everything. |
| `location` | One of jobup.ch's regions (by name in French, German or English, or by its ID), a canton (a code such as `VD`, or `Canton de Vaud`, `Kanton Waadt`, `Canton of Vaud`), or a town name such as `Genève`. A bare name such as `Vaud` is searched as a town name, 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. |
| `maxItems` | Hard stop, so your bill is predictable. |
| `proxyConfiguration` | Off by default. Most runs do not need one. |

### How much one run returns

jobup.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.

### 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 jobup.ch.

jobup.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 jobup.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 jobup.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

jobup.ch and jobs.ch are separate boards with their own listings: on the day
this Actor was built, their first pages of results had no job in common, and
jobs.ch carried about twice as many. This Actor shares its output shape with
the jobs.ch Scraper and the Jobindex Scraper (Denmark), so 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. comptable, informatique. jobup.ch's search is semantic, so it also returns related postings. Leave empty for all postings.

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

A town as you would type it on jobup.ch (e.g. Lausanne, Genève, Fribourg), a canton (e.g. VD, Canton de Vaud), or one of the site's regions (e.g. Région lausannoise, Suisse romande). Leave empty for the whole country. A town that returns nothing fails the run instead of returning unfiltered results.

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

Return only postings first published at or after this date-time, e.g. 2026-09-01T00:00:00Z. Re-published older ads are left out.

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

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

## `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 jobup.ch 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/jobup-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/jobup-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/jobup-ch-scraper --silent --output-dataset

```

## MCP server setup

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