# Jobs.ch Lookup: Swiss Job Postings by Keyword and Region (`accountable_eel/jobs-ch-lookup`) Actor

Jobs.ch scraper without login: search jobs.ch, Switzerland's largest job board, by keyword and region and get one row per posting: title, company, place, canton, workload, link. Monitor mode returns only new postings since the last run. Pay per posting returned; empty searches are free.

- **URL**: https://apify.com/accountable_eel/jobs-ch-lookup.md
- **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.90 / 1,000 job posting returneds

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

## Jobs.ch Lookup: Swiss Job Postings by Keyword and Region

**Get Swiss job postings from jobs.ch by keyword and region, one row per posting, no login.**
Each row has the job title, company, place, canton where jobs.ch gives one, workload range, publication date and the posting link. Turn on monitoring mode and run it on a schedule to get only the postings that are new since your last run.

**Who uses it:** recruiters and sourcers tracking who is hiring in Switzerland, sales teams selling to companies that are growing a team, job-board aggregators, and labour-market analysts. Run it from n8n, Make, Clay or Google Sheets, or let an AI agent call it.

**Price:** $1.80 per 1,000 job postings returned on the free plan, less on paid Apify plans. A search with no postings and a run with nothing new cost only the $0.003 start fee.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `searches` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~jobs-ch-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"searches":["python"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "searches": [
    "python"
  ]
}
```

One search per line. Write it as "keywords @ location", or just the keywords and set a location below. Accepted formats: data engineer @ Zürich, Pflegefachperson, python @ Basel.

Write each search as `keywords @ location` (for example `data engineer @ Zürich`), or just keywords and set a default location. jobs.ch shows 20 postings per page; the actor reads up to 10 pages (200 postings) per search. Keyword filters on title and company run before anything is billed or remembered.

### Output

One row per job posting, for example:

```json
{
  "jobId": "ee70758e-a666-4b6b-8c76-e213b7943f3e",
  "title": "Data Scientist - Recommender Systems (w/m) 80-100%",
  "companyName": "NZZ",
  "location": "Zürich",
  "canton": "ZH",
  "workloadMinPercent": 80,
  "workloadMaxPercent": 100,
  "publishedAt": "2026-09-08T16:32:24+02:00",
  "jobUrl": "https://www.jobs.ch/en/vacancies/detail/ee70758e-a666-4b6b-8c76-e213b7943f3e/"
}
```

Every row also carries the search it came from, `isNew` and `firstSeenAt` (set when monitoring or a watchlist name is on, `null` otherwise) and `scrapedAt`. A value jobs.ch does not give is `null`, never `0` or an empty string. `canton` and `postalCode` come from the posting's address block, which jobs.ch only fills for some postings (about half in a 40-posting check), so they are `null` for the rest; `location` is always the place name jobs.ch prints.

| query | found | status | searchKeywords | searchLocation | jobCount | totalAvailable | truncated | jobs | jobId | title | companyName | location | canton | postalCode | workloadMinPercent | workloadMaxPercent | publishedAt | firstPublishedAt | postedAgo | jobUrl | isNew | firstSeenAt | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| python | true | OK | <keywords searched> | <location searched> | <postings returned> | <total matching on jobs.ch> | <more results were available> | \<all postings found (full list)> | \<jobs.ch job id> | <job title> | <company> | <place> | <canton> | <postal code> | \<workload from (%)> | \<workload to (%)> | <published> | <first published> | \<posted (as jobs.ch words it)> | <job link> | \<is this posting new?> | <first seen on a run> | 1970-01-01T00:00:00.000Z |

A search jobs.ch answers with no postings comes back as a row with `"found": false` and is never charged. jobs.ch search is fuzzy, so even a nonsense word usually returns its closest matches; read `totalAvailable` to see how many postings matched.

### Pricing

- **Job posting returned**: $1.8 per 1,000 job postings

Plus a $0.003 start fee per run. Each event above is billed independently, only when it actually returns data — misses (`found:false`) are never charged.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~jobs-ch-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"searches":["python"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~jobs-ch-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"searches":["python"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~jobs-ch-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"searches":["{{search}}"]}`, mapping the row's search into the `searches` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "jobs.ch scraper" — the agent will find and run this actor.

### Example runs

Paste any of these into the Input tab and press Start. All three return rows with no key, no token and no account of your own beyond an Apify login.

**Python jobs anywhere in Switzerland.** The default shape.

```json
{
  "searches": ["python"],
  "maxJobsPerQuery": 40
}
```

**Data engineer roles in Zürich, without internships.**

```json
{
  "searches": ["data engineer @ Zürich"],
  "excludeTitleKeywords": ["praktikum", "intern", "werkstudent"],
  "maxJobsPerQuery": 40
}
```

**Daily new-postings monitor for several roles.** Run it on a schedule; the first run returns everything and remembers it, later runs return only postings it has not returned before.

```json
{
  "searches": ["devops engineer @ Basel", "devops engineer @ Bern"],
  "onlyNewSinceLastRun": true,
  "deltaName": "devops-basel-bern"
}
```

# Actor input Schema

## `searches` (type: `array`):

One search per line. Write it as "keywords @ location", or just the keywords and set a location below. Accepted formats: data engineer @ Zürich, Pflegefachperson, python @ Basel. You're only charged for the ones we actually find — a miss costs nothing.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

## `maxResults` (type: `integer`):

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `defaultLocation` (type: `string`):

Used for any line that is just keywords. Write it the way jobs.ch does: "Zürich", "Bern", "Basel", "Genève". Leave empty to search all of Switzerland.

## `maxJobsPerQuery` (type: `integer`):

jobs.ch shows 20 postings per page. This actor reads up to 10 pages (200 postings) per search. You pay per posting returned, so this is also your budget control.

## `titleKeywords` (type: `array`):

Optional. Keep only roles whose title contains at least one of these words. Case doesn't matter and partial words work. Leave empty to keep every role.

## `excludeTitleKeywords` (type: `array`):

Optional. Drop any role whose title contains one of these words, e.g. "Praktikum", "Trainee". Applied after the include list above.

## `companies` (type: `array`):

Optional. Keep only roles at companies whose name contains one of these. Partial matches work.

## `excludeCompanies` (type: `array`):

Optional. Drop roles at companies whose name contains one of these, handy for filtering out recruitment agencies you already know.

## `onlyNewSinceLastRun` (type: `boolean`):

Turns this actor into a monitor. A posting counts as new when its jobs.ch ID has not been returned by a previous run of the same watchlist. Already-seen postings are dropped before you are billed, so a run with nothing new costs only the run fee. The first run returns everything and remembers it.

## `deltaName` (type: `string`):

Leave empty and we derive one from this run's settings, so two schedules with different settings keep separate memories. Type your own name to keep one memory across a settings change, or to share one between schedules. Naming a watchlist with the checkbox above off returns every result but still marks each one 'Is this new?' and 'First seen'.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each job posting found gets its own row instead of being grouped under its search. You're still only charged once per search, no matter how many rows it produces.

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

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

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

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "searches": [
    "python"
  ],
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "defaultLocation": "",
  "maxJobsPerQuery": 40,
  "titleKeywords": [],
  "excludeTitleKeywords": [],
  "companies": [],
  "excludeCompanies": [],
  "onlyNewSinceLastRun": false,
  "deltaName": "",
  "columns": [
    "searchKeywords",
    "searchLocation",
    "jobCount",
    "totalAvailable",
    "truncated",
    "jobs",
    "jobId",
    "title",
    "companyName",
    "location",
    "canton",
    "postalCode",
    "workloadMinPercent",
    "workloadMaxPercent",
    "publishedAt",
    "firstPublishedAt",
    "postedAgo",
    "jobUrl",
    "isNew",
    "firstSeenAt"
  ],
  "expandRows": true,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "searches": [
        "python"
    ],
    "includeKeywords": [],
    "excludeKeywords": [],
    "titleKeywords": [],
    "excludeTitleKeywords": [],
    "companies": [],
    "excludeCompanies": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/jobs-ch-lookup").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 = {
    "searches": ["python"],
    "includeKeywords": [],
    "excludeKeywords": [],
    "titleKeywords": [],
    "excludeTitleKeywords": [],
    "companies": [],
    "excludeCompanies": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/jobs-ch-lookup").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 '{
  "searches": [
    "python"
  ],
  "includeKeywords": [],
  "excludeKeywords": [],
  "titleKeywords": [],
  "excludeTitleKeywords": [],
  "companies": [],
  "excludeCompanies": []
}' |
apify call accountable_eel/jobs-ch-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/jobs-ch-lookup"
        }
    }
}
```

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/Y2p2FRyMBuDKFM6Jy/builds/acmEgHdFqr9G5yiJh/openapi.json