# Stellenanzeigen.de Scraper - German Job Listings · $1.5/1K (`listingworks/stellenanzeigen-scraper`) Actor

Extract job postings from stellenanzeigen.de (Germany) by keyword and state: title, employer, place, job type, salary range, posting date, URL, newest first.

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

## Stellenanzeigen.de Scraper — German job listings by keyword and Bundesland

Extract job postings from stellenanzeigen.de (Germany) by keyword and state: title, employer, place, job type, salary range, posting date, URL, newest first.

stellenanzeigen.de is one of Germany's long-running job boards, run by
stellenanzeigen.de GmbH & Co. KG in Munich, with close to 30,000 postings
online at any time. This Actor turns its search results into a clean table:
the job title, the employer, the town, full- or part-time, the salary range
where the posting shows one, and the day it went online.

Press Start. The defaults return the newest Pflege postings across Germany,
with no configuration needed.

### What a row looks like

```json
{
  "title": "Pflegefachkraft (m/w/d) als Nachtwache für die Versorgung von Menschen mit Behinderung - Gestalte mit uns die Zukunft!",
  "company": "Stiftung Innovation & Pflege - Herrenberg - GWW",
  "location": "Sindelfingen",
  "employment_type": "Full-time, Part-time",
  "salary_min": 4050,
  "salary_max": 4550,
  "salary_currency": "EUR",
  "salary_period": "month",
  "posted_at": "2026-09-23T02:00:00+02:00",
  "source_url": "https://www.stellenanzeigen.de/job/pflegefachkraft-m-w-d-als-nachtwache-fuer-die-versorgung-von-menschen-mit-behinderung-gestalte-mit-uns-die-zukunft-sindelfingen-sde-112249/",
  "external_id": "SDE-112249"
}
```

`company` is the employer as the site names it, often a care provider, a
public employer or a recruitment agency. Contact persons, email addresses and
phone numbers are never collected. The site's own data carries the
application email for every posting, and this Actor does not read it. It also
leaves out the office postcode and map point, and never opens the job text.
Where the site hides the employer ("Unternehmen aus dem Bereich: …"), `company`
is empty.

A posting in several places lists each town once. A posting for all of
Germany says `Deutschland`, and those postings also come up in a Bundesland
search, because the site includes them there.

### Only what you searched for

Below its matches, stellenanzeigen.de shows "ähnliche Jobs": similar postings
that did not match your keyword. Under "Pflege" that can mean an export clerk
or a sales manager. This Actor stops where the matches end, and the count it
reports is the site's count of matches. So a search that finds nothing returns
no rows, not a page of similar jobs.

### When a posting went online

`posted_at` is the day the posting shows on the site, on German time. Many
postings carry only the day, which appears as midnight German time, or 02:00
in summer when the site stamps midnight UTC. So `postedAfter` compares by day.
The list is read newest first, so a run with `postedAfter` stops as soon as the
postings are older. A posting the employer published again shows the new day.

### What people use it for

Tracking which employers in a Land are hiring, for a trade or a skill, week by
week. Salary benchmarks from the ranges employers publish (about six in ten
care postings show one). Feeding a job board or a newsletter with German
openings in a niche. Labour-market research that needs structured rows, not a
page of links.

### Input

| Field | What it does |
|---|---|
| `searchTerms` | Keywords, e.g. `Pflege`, `Python`, `Buchhaltung`. Each keyword is its own search. Leave empty for everything. |
| `location` | A Bundesland: `Bayern`, `Nordrhein-Westfalen` (or `NRW`), `Berlin`, `Baden-Württemberg` and so on. Or one of the site's own place ids, as its search URL shows them after `locationIds=`, e.g. `M-DE-1494` for Stuttgart, which the site widens by 30 km. Leave empty for all of Germany. |
| `postedAfter` | Only keep postings from this day on, e.g. `2026-09-20`. Handy for daily runs that should return just what is new. |
| `sinceDays` | The same, as a rolling window: `1` keeps yesterday and today, `7` the last week. Set it once on a scheduled task and never edit the date again. |
| `maxItems` | Hard stop, so your bill is predictable. |
| `proxyConfiguration` | Off by default. Most runs do not need one. |

Town names are not accepted as text, because the site searches by its own
place ids and its place lookup is not open to crawlers. A Bundesland or an id
from the site's URL always works.

### How much one run returns

stellenanzeigen.de serves 25 postings per page and at most 10,000 per search
(400 pages). A search that reaches that limit is reported as capped, not as
complete. To go beyond it, split by keyword or Bundesland across runs.

The site does not keep a fixed order for postings from the same day between
one page and the next. A posting can come back on two pages, and this Actor
removes the repeat, so a long crawl can miss a few postings from the same day.
A daily run with `postedAfter` — or `sinceDays: 1` on a scheduled task — is
the reliable way to catch everything new.

### 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 (`/suche/`), which
stellenanzeigen.de's robots.txt allows. The paths it disallows (place
suggestions, job views, print pages, application flows, tracking) are never
requested, and neither is the job text. `remote`, `workload`, `apply_url` and
`categories` ship always empty, so that one parser works across every job
Actor here.

Every page is checked against what you asked for: the keyword, the place, the
newest-first order and the page number. The site answers an unknown place id
with postings from all of Germany. When a place id is unknown, or a Bundesland
comes back under another name, the run fails rather than return rows you did
not ask for and charge you for them.

If stellenanzeigen.de 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 434 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 Jobware Scraper (Germany), the
jobs.at Scraper (Austria), the jobs.ch and JobScout24 Scrapers (Switzerland)
and the Jobindex Scraper (Denmark). 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, Python, Buchhaltung. Each keyword is its own search. Leave empty for all postings.

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

A Bundesland (e.g. Bayern, Nordrhein-Westfalen, Berlin), or one of stellenanzeigen.de's own place ids as its search URL shows them after locationIds= (e.g. M-DE-1494 for Stuttgart; the site adds 30 km around a town). Leave empty for all of Germany. A place id the site does not know fails the run instead of returning postings from all of Germany.

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

Return only postings from this date on (German calendar day), e.g. 2026-09-20. The list is read newest first, so the run stops once it 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. stellenanzeigen.de serves at most 10,000 postings (400 pages) 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": [
    "Pflege"
  ],
  "location": "Bayern",
  "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, where, and the pay the posting shows.

## `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": [
        "Pflege"
    ],
    "location": "Bayern",
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("listingworks/stellenanzeigen-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": ["Pflege"],
    "location": "Bayern",
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("listingworks/stellenanzeigen-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": [
    "Pflege"
  ],
  "location": "Bayern",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call listingworks/stellenanzeigen-scraper --silent --output-dataset

```

## MCP server setup

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