# Jobware Scraper - German Job Listings · $1.5/1K (`listingworks/jobware-scraper`) Actor

Job postings from jobware.de with title, employer, place, employment type and posting time.

- **URL**: https://apify.com/listingworks/jobware-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 $0.75 / 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

## Jobware Scraper — German job listings by keyword and place

Jobware is one of Germany's long-running job boards, with around 340,000 live
postings, many of them from engineering, IT, healthcare and the public sector.
This Actor turns its search results into a clean table: the job title, the
employer, the place, full-time or part-time, home office, and when the posting
went online.

Press Start. The defaults return the site's current list across Germany, with
no configuration needed.

### What a row looks like

```json
{
  "title": "Pflegefachkraft (m/w/d) Dialyse Tag- oder Nachtdienst",
  "company": "Nephrocare Hamburg-Süderelbe GmbH Medizinisches Versorgungszentrum",
  "location": "Hamburg",
  "remote": null,
  "employment_type": "Full-time, Part-time",
  "posted_at": "2026-09-19T07:00:00+02:00",
  "source_url": "https://www.jobware.de/job/pflegefachkraft-m-w-d-dialyse-tag-oder-nachtdienst-2038086315",
  "external_id": "2038086315"
}
```

`company` is the employer as the list shows it, sometimes a staffing agency.
Contact persons, email addresses and phone numbers are never collected — this
Actor reads the search results only and never opens the job text.

`remote` is `true` when the posting carries Jobware's "Home-Office" label, and
empty otherwise: no label does not mean the job is on-site.

### When a posting went online

Every card on Jobware carries a timestamp. For recent postings it is exact
("vor 22 Minuten"); for postings a few days old the site shows only the date,
and the timestamp is early morning German time on that day (07:00 in summer). `posted_at` is the
timestamp on German time. `postedAfter` compares German calendar days, so a
cutoff of 2026-09-19 keeps everything posted on the 19th, whatever the hour.

### What people use it for

Tracking which companies in a region are hiring, week by week. Feeding a job
board or a newsletter with German openings in a niche. Watching which staffing
agencies are recruiting for what. Research on the German labour market that
needs structured rows rather than a page of links.

### Input

| Field | What it does |
|---|---|
| `searchTerms` | Keywords, e.g. `pflege`, `informatik`, `SAP`. Each keyword is its own search. Leave empty for everything. |
| `location` | A town or postcode as you would type it on Jobware: `Hamburg`, `München`, `Frankfurt am Main`, `80331`. The site includes nearby towns. Leave empty for the whole country. |
| `postedAfter` | Only keep postings from this date on. The run then asks Jobware for newest first and stops once the list is older. Handy for daily runs that should return just what is new. |
| `maxItems` | Hard stop, so your bill is predictable. |
| `proxyConfiguration` | Off by default. Most runs do not need one. |

### How much one run returns

Jobware serves 20 listings per page and its pager stops at page 250, so one
search returns at most 5,000 listings. To go beyond that, split by keyword or
place across runs; duplicates are removed within a run.

### Pricing

$1.50 per 1,000 listings, dropping to $0.75 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 pages (`/jobs?…`), which
Jobware's robots.txt allows. The paths it disallows — `/api/`, accounts,
applications, job alerts — are never requested, and neither is the job text.
Salary is behind a "show salary" button and the job description is on the
posting page, so neither is read. The catalogue-wide columns `workload`,
`salary_*`, `apply_url` and `categories` still ship, always empty, so that one
parser works across every job Actor here.

Jobware searches places, not a fixed list of towns: a place it does not know
returns no postings, as it does on the site, rather than the whole country.
Every page is checked against what you asked for — keyword, place, order and
page number — and if the site answered something else, the run fails rather
than returning rows you did not ask for and charging you for them.

If Jobware 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 "100 rows of 1,872 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 shape, other sites

This Actor shares its output shape with the jobs.ch, jobup.ch and JobScout24
Scrapers (Switzerland), the Jobindex Scraper (Denmark) and the Jobs.cz Scraper
(Czech Republic). A parser you write for one keeps working on the others, and
on the countries added next.

### 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. pflege, informatik. Each keyword is its own search. Leave empty for all postings.

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

A German town or postcode as you would type it on Jobware (e.g. Hamburg, München, 80331). The site includes nearby towns. Leave empty for all of Germany. A place the site does not know returns no postings (the site's own answer), not unfiltered results.

## `postedAfter` (type: `string`):

Return only postings from this date on (German calendar day), e.g. 2026-09-20. The run then asks the site for newest first and stops once the list is older.

## `sinceDays` (type: `integer`):

Keep only listings posted in the last N days, counted in UTC from the day the run starts: 1 = yesterday and today. Made for a daily schedule. Ignored when Posted after is set.

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

Stop after this many postings. Jobware serves at most 250 pages (5,000 postings) per search, so larger numbers are reached with more keywords or places.

## `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": "",
  "postedAfter": "",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

All German job postings from this run: what the job is, who is hiring, and where.

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

```

## MCP server setup

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