# Jobs.cz Scraper - Czech Job Listings by Region & Keyword (`listingworks/jobs-cz-scraper`) Actor

Scrape Jobs.cz listings: title, company, town, region, published salary and posting date. No proxy needed, one flat price per result, no contact details collected.

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

## Jobs.cz Scraper — Czech job listings by keyword, region and town

Jobs.cz is the Czech Republic's largest job site. This Actor turns its search
results into a clean table: the job title, the company, where it is, and the
salary when the advertiser publishes one.

Press Start. The defaults sweep all fourteen Czech regions and return the
newest listings from each, with no configuration needed.

### What a row looks like

```json
{
  "title": "Skladník/skladnice – ranní směny",
  "company": "Příklad Logistika s.r.o.",
  "location": "Brno – Slatina",
  "salary_min": 32000,
  "salary_max": 38000,
  "salary_currency": "CZK",
  "salary_period": "month",
  "posted_at": "2026-09-17",
  "source_url": "https://www.jobs.cz/rpd/2001234567/",
  "external_id": "2001234567"
}
```

Company names are included. Contact persons, email addresses and phone
numbers are never collected — this Actor reads the search results only and
never opens the job text, which is where personal contact details live.

### What people use it for

Tracking which companies in a region or a town are hiring, week by week.
Salary research, since Jobs.cz shows a published range on roughly four
listings in ten. Feeding a job board or a newsletter with Czech openings in a
niche. And labour-market research that needs structured rows rather than a
page of links.

### Input

| Field | What it does |
|---|---|
| `searchTerms` | Keywords. Jobs.cz matches them literally, so use the Czech job title people actually write (`skladník`, `účetní`, `programátor`). Leave empty for everything. |
| `location` | A Czech region slug such as `praha`, `jihomoravsky-kraj` or `vysocina-kraj`, or a town such as `Brno`. Towns are matched within the town itself, not the 50 km radius Jobs.cz adds by default. Leave empty to sweep all regions. |
| `maxItems` | Hard stop, so your bill is predictable. |
| `proxyConfiguration` | Off by default. Most runs do not need one. |

There is no `postedAfter` input for this site. Jobs.cz shows a first-posting
date on only about one listing in five; the rest show a re-publication date,
a bare date that could be either, or nothing. Filtering on that would count
old listings as new, so the Actor refuses the input rather than quietly
returning the wrong rows. `posted_at` is filled only where the card says
"Přidáno" (added) with a date. To find what is new, compare `external_id`
against your previous run.

### How much one run returns

Jobs.cz serves 30 listings per page and stops at page 45, so one search
returns at most 1,350 listings. To go beyond that, split by keyword, region
or town 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. Employment type,
workload, application deadline, category and the job text are not on that
page, so they are not in the output. `remote` appears only on listings Jobs.cz
tags as mostly home-office, where it is `true`; other rows have no such field.

Jobs.cz answers some mistakes with a normal page instead of an error — a
profession typed into the location box becomes a keyword search, an unknown
filter value is silently dropped, and a page past the last one returns the
last page again. This Actor checks the search conditions Jobs.cz echoes back
against the ones you asked for and fails the run if they differ, rather than
charging you for the wrong rows. An unknown town gives a clear failure.

If Jobs.cz 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 data, other countries

This Actor shares its output shape with the Jobindex Scraper (Denmark) and
the jobs.ch Scraper (Switzerland). A parser you write for one keeps working
on the others.

### 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. skladník, řidič, c++. jobs.cz matches them literally. Leave empty for all postings, region by region.

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

One of jobs.cz's regions (e.g. Praha, Jihomoravský kraj, Vysočina) or a town (e.g. Brno, Ústí nad Labem). A town means that town only, without jobs.cz's default 50 km radius. Leave empty for the whole country. An unknown place fails the run instead of returning unfiltered results.

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

Stop after this many postings. jobs.cz serves at most 45 pages (1,350 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": "",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

All Czech job postings from this run: what the job is, who is hiring, where, and the pay when it is published.

## `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/jobs-cz-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/jobs-cz-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/jobs-cz-scraper --silent --output-dataset

```

## MCP server setup

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