# jobs.cz Jobs Scraper (`scrapyx/jobscz-jobs-scraper`) Actor

Czech job listings from jobs.cz: search by keyword and locality, with full job details on request — description, required education and languages, employment type, contract length and contact person.

- **URL**: https://apify.com/scrapyx/jobscz-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.56 / 1,000 results

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 Jobs Scraper

Scrapes job listings from [jobs.cz](https://www.jobs.cz), one of the
Czech Republic's largest job boards. Search by keyword and locality, then
optionally pull the full job detail: description, required education and
languages, employment type, contract length and contact person.

***

### What you get

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

#### From the search page (always)

`jobId` · `title` · `url` · `companyName` · `locality`

#### From the detail page (`includeJobDetails`, on by default — read the limit below first)

`description` (full job ad text) · `infoItems` (all the label/value pairs
jobs.cz itself shows — required education, languages, employment type,
contract length, contract form, and whatever else the posting includes) ·
`locationText` (full street address) · `contactPerson` · `breadcrumbs`
(category path)

***

### Input

```jsonc
{
  "queries": [
    { "term": "programátor", "locality": "praha" }
  ],
  "includeJobDetails": true,
  "maxItemsPerQuery": 50
}
```

Each entry needs a `term`; `locality` is optional (omit it for a
nationwide search).

#### One `term` per query, not a list — here's why

jobs.cz's own multi-keyword parameter combines terms as **OR**, not AND:
measured in Prague, `programátor` alone → 494 results, `senior` alone →
686, both together → **1,099** (close to the sum, not an intersection). A
list input here would silently mean "any of these keywords" when "all of
these" is the natural reading — refused by design. Run separate entries in
`queries` for separate searches instead, each with its own honest total.

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

Real values are Czech city/region URL slugs (`praha`, `brno`, `ostrava`,
`plzen`, and others not listed). There's no lookup endpoint to validate
against — but jobs.cz is honest about a miss: an unrecognised slug answers
a clean HTTP 404, not a silent fallback to a nationwide baseline.

***

### Read this before turning on `includeJobDetails`

**A large share of postings from bigger employers cannot be enriched at
all — by design of the site, not a bug here.** Some employers' job ads
redirect from the standard `jobs.cz/rpd/{id}/` detail URL to a
company-branded subdomain (`{company}.jobs.cz`) — a completely different
page template with zero markup overlap with the standard one (no title
heading, no structured fields of any kind). Measured on one small sample:
**4 of 5** detail fetches for a Prague "programátor" search hit this
(ČSOB, Česká spořitelna, and others). Those rows keep every field the
search page already gave them (title, company, locality, url) and carry a
specific `_detailError` naming the branded subdomain they redirected to —
never a silent blank. `includeJobDetails` is still worth turning on: it's
not an all-or-nothing switch, just don't expect 100% enrichment coverage
on a batch that includes large employers.

***

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

**Pagination clamps to the LAST real page past the end** — the opposite
direction from a related actor in this same portfolio
(`jobup-jobs-scraper`, which clamps to page 1). Past the true final page,
jobs.cz re-serves that last page's exact result list rather than an empty
page. The actor's stop condition is "this page contributed zero new job
ids", never "the page was empty", so this is handled correctly regardless
of which direction the clamp goes — and the summary row reports
`paginationClampHit: true` when it happens.

***

### Known limits

**1. Company-branded detail pages are not parsed** (see above) — the
single biggest limitation on this target.

**2. The total-count text uses a non-breaking space as its thousands
separator** ("Našli jsme 1 099 nabídek"), not a comma — handled internally,
mentioned here only because it's the kind of thing that silently breaks a
naive `\d+` regex if you're parsing this site yourself.

***

### Anti-bot posture

**None observed.** 8/8 TLS profiles clean on both the search and detail
surfaces during recon. The actor still ships a rotating profile pool, a
retry ladder and challenge-marker detection, and paces requests by
default — a target being clean in local recon has not always meant the
same from Apify's cloud egress elsewhere in this portfolio.

### Policy

`robots.txt` (`User-agent: *`) names no `ClaudeBot`/`anthropic-ai`/`GPTBot`
group. It disallows `/api/`, `/iapi/`, `/muj/` (account area), `/asmt/`,
`/status/`, `/translations/`, `/js/`, `/nabidky-podle-cv/`,
`/session-log/`, and two tokenised query strings on unrelated paths — none
of which overlap `/prace/` (search) or `/rpd/` (detail), the two surfaces
this actor fetches.

# Actor input Schema

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

One crawl per entry, each with its own SEARCH\_SUMMARY row. Each item: {"term": "programátor", "locality": "praha"} -- 'term' is required, 'locality' is optional (omit it for a nationwide search). Only ONE term per query is accepted, not a list: jobs.cz's own multi-keyword parameter combines terms as OR (measured: 494 + 686 results -> 1,099 combined, not an intersection), so a list here would silently mean 'any of these' when 'all of these' is the natural reading -- run separate queries instead. 'locality' is a Czech city/region URL slug (examples: praha, brno, ostrava, plzen); there's no lookup endpoint to validate it against, but jobs.cz is honest about a miss (a clean 404), so free text is safe here.

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

Fetch each job's detail page for the full description, required education/languages, employment type, contract length, and contact person. Search rows already carry title, company, locality and url. One extra request per job when on.

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

Stop each query after this many jobs. Set to 0 for unlimited -- jobs.cz's pagination is genuinely honest up to the real last page, but past it the site CLAMPS to that last page'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. jobs.cz showed no bot mitigation at all during recon (8/8 TLS profiles clean on both search and detail pages).

## `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.

## Actor input object example

```json
{
  "queries": [
    {
      "term": "programátor",
      "locality": "praha"
    }
  ],
  "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": "programátor",
            "locality": "praha"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/jobscz-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": "programátor",
            "locality": "praha",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/jobscz-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": "programátor",
      "locality": "praha"
    }
  ]
}' |
apify call scrapyx/jobscz-jobs-scraper --silent --output-dataset

```

## MCP server setup

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