# jobup.ch Jobs Scraper (`scrapyx/jobup-jobs-scraper`) Actor

Swiss job listings from jobup.ch: search by keyword and location, with full job details on request — description, salary, benefits, required skills, employer overview and precise canton/postcode location.

- **URL**: https://apify.com/scrapyx/jobup-jobs-scraper.md
- **Developed by:** [Ibnu Adzim](https://apify.com/scrapyx) (community)
- **Categories:** Jobs, Business, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.84 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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 Jobs Scraper

Scrapes job listings from [jobup.ch](https://www.jobup.ch), one of
Switzerland's largest job boards. Search by keyword and canton/city, then
optionally pull the full job detail: description, salary, benefits,
required skills, employer overview and precise canton/postcode location.

***

### What you get

One `JOB` row per posting, plus a `SEARCH_SUMMARY` row per query.

#### From the search page (always)

`jobId` · `title` · `url` · `description` (short, generic) · `datePosted` ·
`employmentType` · `companyName` · `companyUrl` · `locationCountry`

#### From the detail page (`includeJobDetails`, on by default)

`description` (full HTML job ad) · `disambiguatingDescription` ·
`jobStartDate` · `jobImmediateStart` · `workHours` · `employmentUnit` ·
`totalJobOpenings` · `locationRegion` (canton) · `locationPostalCode` ·
`locationStreetAddress` · `industry` · `occupationalCategory` ·
`baseSalary` · `jobBenefits` · `skills` · `employerOverview` ·
`applicationContact` · `directApply`

***

### Input

```jsonc
{
  "queries": [
    { "term": "developer", "location": "zürich" }
  ],
  "includeJobDetails": true,
  "maxItemsPerQuery": 50
}
```

Each entry in `queries` needs at least a `term` or a `location`.

#### `term` is fuzzy relevance search, not exact matching

A nonsense term returns a small, genuinely related result set (not zero,
not the whole catalogue) — normal search-engine behaviour, documented as-is
rather than defended against.

#### `location` is free text, and that's safe here

Real values are Swiss place-name slugs (`zürich`, `bern`, `basel`,
`genève`, `lausanne`, `luzern`, `winterthur`, `zug`, `st. gallen`, and
others not listed). There's no lookup endpoint to validate against — but
unlike most location filters in this portfolio, an unrecognised value here
is **honest**: it answers a genuinely empty result (`totalMatches: 0`), not
a silent fallback to the unfiltered baseline. A typo costs you nothing
misleading.

***

### Read this before trusting a large `maxItemsPerQuery`

**Pagination clamps back to page 1 past the real last page.** jobup.ch's
own pages walk honestly and with zero overlap up to the true end of a
query's results — but one page further, it re-serves page 1's exact result
list, byte-for-byte, instead of an empty page or an error. The actor's stop
condition is "this page contributed zero new job ids", never "the page was
empty", so this is handled correctly and the summary row reports
`paginationClampHit: true` when it happens — but it means you cannot detect
a mid-crawl failure by watching for an empty page; watch `paginationClampHit`
and `jobsReturned` vs `totalMatches` instead.

***

### Known limits

**1. Job descriptions are raw HTML**, not plain text — passed through
verbatim (raw passthrough) rather than stripped, since stripping would lose
formatting some consumers want (lists of requirements, headed sections).
**On a small number of postings, `title` carries stray HTML too** —
confirmed live on a cloud run: a recruiting agency's own CMS export leaked
`<div class=C_PTITLEHTML><h1>...</h1></div>` markup straight into the
`title` field, not just `description`. This is upstream data quality, not
a parsing defect (verified against the raw JSON-LD jobup.ch itself serves)
— passed through as-is rather than "cleaned," for the same raw-passthrough
reason as point 1.

**2. `baseSalary` is often an empty shell.** The `MonetaryAmount`/
`QuantitativeValue` structure is present on essentially every job, but the
actual `value`/`minValue`/`maxValue` numbers are only filled in when the
employer chose to disclose a salary. An empty object is a genuine "not
disclosed", not a parse failure.

**3. Aggregation-based location counts don't have to match the actor's own
totals exactly.** jobup.ch's own facet sidebar (e.g. "Bern: 24" for one
measured query) reflects a slightly different scope than filtering
directly by that location (`location=bern` on the same query measured
**10**) — both are genuine site behaviour, not a bug in this actor.

***

### Anti-bot posture

**None observed.** 8/8 TLS profiles clean on BOTH the search and detail
pages during recon — the cleanest surface measured anywhere in this
portfolio (most targets need at least a narrowed profile pool). The actor
still ships a rotating profile pool, a retry ladder and challenge-marker
detection, and paces requests by default, since a target being clean
locally has not always meant the same from Apify's cloud egress elsewhere
in this portfolio.

### Policy

`robots.txt` (`User-agent: *`, mirrored for `Googlebot`) names no
`ClaudeBot`/`anthropic-ai`/`GPTBot` group. It disallows `/api/`,
`/api_proxy/`, the login/register/auth flows, the apply flow
(`/*/application/*`), and a `feat=` query parameter — none of which overlap
`/en/jobs/` search or `/en/jobs/detail/`, the two surfaces this actor
fetches. `SemrushBot` gets a blanket `Disallow: /`, which is irrelevant
here.

# Actor input Schema

## `queries` (type: `array`):

One crawl per entry, each with its own SEARCH_SUMMARY row. Each item: {"term": "developer", "location": "zürich"} -- at least one of the two is required. 'term' is free-text relevance search (a nonsense term returns a small, genuinely related result set, not zero and not the whole catalogue). 'location' is a Swiss place-name slug (examples: zürich, bern, basel, genève, lausanne, luzern, winterthur, zug); there's no lookup endpoint to validate it against, but jobup.ch is honest about a miss (a real empty result), so free text is safe here unlike most location filters in this portfolio.

## `includeJobDetails` (type: `boolean`):

Fetch each job's detail page for the full description, salary, benefits, required skills, employer overview and precise canton/postcode location. Search rows already carry title, employer, a short generic description, url, date posted and employment type. One extra request per job when on.

## `maxItemsPerQuery` (type: `integer`):

Stop each query after this many jobs. Set to 0 for unlimited -- jobup.ch's pagination is genuinely honest up to the real last page, but past it the site CLAMPS back to page 1's exact result list rather than answering empty (see the summary row's 'paginationClampHit' flag), so an unlimited crawl still terminates correctly.

## `maxConcurrency` (type: `integer`):

How many requests may be in flight at once. This absorbs latency variance; it is NOT the throttle -- the crawl rate is set by 'Minimum interval between requests' below.

## `minRequestInterval` (type: `number`):

The actual speed control: the shortest gap between two requests, across all workers. jobup.ch showed no bot mitigation at all during recon (8/8 TLS profiles clean on both search and detail pages), so this is set lower than more defended targets in this portfolio.

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

Residential with no country pin is the cloud default. No WAF was observed anywhere during recon, so there's no known reason to narrow the exit-IP pool -- kept wide in case a cloud-only block shows up that local recon didn't catch.

## Actor input object example

```json
{
  "queries": [
    {
      "term": "developer",
      "location": "zürich"
    }
  ],
  "includeJobDetails": true,
  "maxItemsPerQuery": 50,
  "maxConcurrency": 6,
  "minRequestInterval": 0.3,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `items` (type: `string`):

One row per scraped record. See the dataset's default view for field definitions.

# 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 = {
    "queries": [
        {
            "term": "developer",
            "location": "zürich"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/jobup-jobs-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 = { "queries": [{
            "term": "developer",
            "location": "zürich",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/jobup-jobs-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 '{
  "queries": [
    {
      "term": "developer",
      "location": "zürich"
    }
  ]
}' |
apify call scrapyx/jobup-jobs-scraper --silent --output-dataset

```

## MCP server setup

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