# jobs.ch Multi-Query Swiss Vacancy Export (`jpmarketdata/jobs-ch-multi-query-vacancy-export`) Actor

Export current jobs.ch Swiss vacancy search results for up to three role queries in one deduplicated, privacy-minimized dataset with exact displayed work locations.

- **URL**: https://apify.com/jpmarketdata/jobs-ch-multi-query-vacancy-export.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 91.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.90 / 1,000 unique swiss vacancy delivereds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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 Multi-Query Swiss Vacancy Export

Export current public jobs.ch Swiss vacancies for up to three role searches in one low-cost, deduplicated dataset. Recruiters and hiring-market analysts can schedule a role watchlist and compare the returned rows with their own prior snapshots. This Actor does not maintain history or claim to find changes by itself. It is an independent tool, not affiliated with JobCloud.

### Input

`queries` takes one to three role phrases; default `data analyst` and `nurse`. `maxItemsPerQuery` takes 1–40, default 10. Each search is source-ordered and capped to two public 20-result pages. Empty or unsupported selectors fail; no pasted URL or hidden source API is accepted.

### Output

One row per unique source posting ID across all selected searches. Each row has title, published organization, exact displayed work location, employment type, original posted timestamp, optional workload, source rank, matching queries and public job URL. `locationText` is `null` when the source displays an empty Place of work value; the vacancy is retained and charged once like other delivered rows. A missing location label or changed card structure still fails. No city or remote eligibility is inferred. Organization may be an advertiser or agency; no true-employer inference. No salary, full description, contact, application, applicant or personal profile. `reportedTotal` is the source search count for the first matching query; `outputLimited` flags selected caps. Current source relevance order is not a newest-first guarantee.

### Pricing

$0.0009 per delivered unique `vacancy-delivered` row on FREE. No start, search, detail, default-dataset or summary event. The default two-query run should yield up to 20 billable rows ($0.018); the three-query maximum yields at most 120 ($0.108). Duplicate postings and failed/undelivered rows are not charged.

### Limits

Public jobs.ch search HTML/Schema.org JSON-LD only, with no login, proxy, browser or paid API. Current robots rules are checked on every run. At most six search pages plus robots, 2 seconds between requests, 4 MiB per response, 120 seconds and 256 MB. A requested page or search failure aborts before output/charge. A total verified zero job union fails rather than masquerading as a successful export. JobCloud terms restrict scraping and resale; source attribution and links must be retained. No endorsement or legal permission is claimed.

### Privacy

Only public listing title, organization, location, contract, date and link are exported. The Actor does not collect applicant data, recruiter names, contact fields, descriptions, cookies, applications or profiles. Search pages are queried anonymously and source attribution is retained.

# Actor input Schema

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

One to three role phrases searched on public jobs.ch English vacancy pages. Queries are unioned and repeated posting IDs are charged once.

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

Take the first 1–40 public search results per role; at most two 20-result pages per role. This is a capped source-ordered sample, not all matching jobs.

## Actor input object example

```json
{
  "queries": [
    "data analyst",
    "nurse"
  ],
  "maxItemsPerQuery": 10
}
```

# 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 = {
    "queries": [
        "data analyst",
        "nurse"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpmarketdata/jobs-ch-multi-query-vacancy-export").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": [
        "data analyst",
        "nurse",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("jpmarketdata/jobs-ch-multi-query-vacancy-export").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": [
    "data analyst",
    "nurse"
  ]
}' |
apify call jpmarketdata/jobs-ch-multi-query-vacancy-export --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/jobs-ch-multi-query-vacancy-export"
        }
    }
}
```

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/40TBkbAxkhcqgJKHc/builds/9LEEPDc9qqCMifPTu/openapi.json
