Jobware Scraper — German job listings by keyword and place

Extract job postings from Jobware.de (Germany) by keyword and location: title, employer, place, employment type, posting time, URL.

Three rows from a real run

Title	Employer	Location	Posted
Pflegefachpersonen (m/w/d) für die Pflegebegutachtung	Medizinischer Dienst Baden-Württemberg	Göppingen	2026-10-13T09:44:46+02:00
Bauingenieur*in in der Straßen- und Radwegeplanung (m/w/d)	Landesbetrieb Straßenbau Nordrhein-Westfalen (Straßen.NRW)	Bochum	2026-10-13T09:41:09+02:00
Elektriker in Vollzeit (m/w/d) - mit Option Wechselprämie	CFT GmbH Compact Filter Technic	Hamminkeln	2026-10-13T09:18:10+02:00

A run with maxItems: 10 on 2026-10-13 returned 10 postings in 4 seconds and would cost about $0.02 at the current price. Full fields for every row are shown below.

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

{
  "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. Business names only: where the site marks the advertiser as a private person, or the name on the card is or contains a person's name (a sole trader's trade name), the field is left empty. 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.

Every row also carries source_site and scraped_at.

Field	What it holds	How often it is filled
title, company, location	Job title; Employer; Location	Always
remote	Home office	Few (8 of 100)
employment_type	Employment type	Always
posted_at	Posted	Always
source_url, external_id	Posting URL; Posting ID	Always
application_deadline, company_url, company_rating, workplace_postal_code, workplace_address, latitude, longitude	Catalogue-wide columns; Jobware's list does not show them	Always empty here

Fill rates are from a 100-row run on 28 September 2026.

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

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.

Daily new listings

Make a task from this Actor, set sinceDays to 1 with your search, and schedule it each morning. Every run then returns only what was posted since the previous day, in the same columns as a full run. The list is read newest first, so the run stops once the postings are older than the cutoff. A daily task for pflege in Hamburg returned 54 new postings on 29 September 2026 and left out 46 older ones.

How this compares

Other Jobware Actors are on the Store. Checked on 2 October 2026 against the two most used, from their own Store descriptions and input forms:

• Results page only. Both can open each posting for its full description. This Actor never opens a posting: it reads the search results only.
• No personal data. Both advertise apply e-mail addresses and contact persons. This Actor collects no contact person, e-mail address or phone number; company is the employer's name only.
• One price per row. Both charge a separate event for each posting they open, on top of the listed result. Here every row costs the same, and you pay only for rows you receive.
• Daily new postings. One of them has an age filter in hours, the other none. Here sinceDays is a rolling window you set once on a scheduled task.

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.