Jobs.at Scraper — Austrian job listings by keyword and place

jobs.at is one of Austria's large job boards, with close to 10,000 live postings: nearly 400 nursing jobs in Wien alone, and over 2,400 sales jobs across the country. This Actor turns its search results into a clean table: the job title, the employer, the workplace, the working time, the minimum salary the employer states, when the posting went online, and the link to the posting.

Press Start. The prefilled input searches for pflege (nursing) in Wien, so the first run needs no configuration.

What a row looks like

{
  "title": "Pflegeassistenz bzw. Pflegefachassistenz (m/w/d)",
  "company": "Wiener Rotes Kreuz Pflege und Betreuung GmbH",
  "location": "Wien",
  "employment_type": "Vollzeit",
  "salary_min": 3140,
  "salary_currency": "EUR",
  "salary_period": "month",
  "posted_at": "2026-09-18T15:00:54+02:00",
  "source_url": "https://www.jobs.at/i/7903409",
  "external_id": "7903409"
}

company is the employer as the list shows it. Contact persons, email addresses and phone numbers are never collected. This Actor reads the search results only and never opens the job text.

location is the workplace the posting names: a town, a Vienna district ("Wien 9. Bezirk (Alsergrund)"), a state, or several of them ("Wien, Niederösterreich"). remote is true when the posting offers home office, and empty otherwise.

employment_type is the working time as jobs.at writes it, in German: Vollzeit (full-time), Teilzeit/geringfügig (part-time or marginal employment), Praktika (internship). Austrian postings must state the minimum pay, and jobs.at shows it as "ab 3.140€ pro Monat": salary_min is that minimum, per month, year or hour as the posting says. salary_max stays empty, because the posting gives no upper figure.

Posting dates

posted_at is the time jobs.at gives for the posting, to the second, on Vienna time. A "posted after" filter compares that time with yours.

jobs.at lists by relevance, not by date, and offers no date order. A run with a cutoff therefore reads the whole search and keeps the postings at or after it. It takes longer than a date-ordered site, but no newer posting further down the list is missed.

What people use it for

• Tracking which companies in an Austrian town or state are hiring, week by week.
• Salary benchmarking from the minimum pay Austrian postings must state.
• Feeding a job board or a newsletter with Austrian openings in a niche, such as nursing, retail or hospitality.
• Research on the Austrian labour market that needs structured rows rather than a page of links.

Input

Field	What it does
searchTerms	Keywords, e.g. pflege, verkauf, buchhaltung. Each keyword is its own search. Leave empty for everything.
location	An Austrian town, district or state as jobs.at writes it: Wien, Linz, Graz, Niederösterreich, Wien Innenstadt. Leave empty for the whole country.
postedAfter	Only postings from this time on, e.g. 2026-09-20T00:00:00+02:00.
maxItems	A hard stop, so your bill is predictable.
proxyConfiguration	Off by default. Most runs do not need a proxy.

How much one run returns

jobs.at serves 15 postings per page, and the run reads page after page until the search ends or maxItems is reached. There is no page cap: the last page of a 2,439-posting search was read to its last posting. For a keyword or a place, the site states how many postings the search holds, and the run report shows that number next to the rows delivered. For the unfiltered list the site gives only a rounded figure ("9.750+"), so no count is reported there. If you search several keywords, a posting that matches more than one is delivered only once per run.

Pricing

$1.50 per 1,000 postings, falling 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 only for rows you actually receive. If you set a maximum charge for the run, it stops cleanly at that limit instead of going over it.

Scope and limits

The Actor reads public listings only, from the search results pages. jobs.at's robots.txt allows these for all crawlers. No API is called, and job pages are not opened. The site's own promotions between the results are not postings and are not delivered.

A search with no results fails the run. jobs.at answers an empty search with a "page not found" (HTTP 404), the same answer it gives for a place it does not know. This Actor cannot tell the two apart, so it fails the run rather than report an unknown place as an honest zero. A very narrow keyword on a schedule can therefore go red on a day with no postings.

Every page is checked against what you asked for: keyword, place and position in the list. If the site answered something else, the run fails rather than return rows you did not ask for and charge you for them.

If jobs.at 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 only 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.

Same shape, other sites

This Actor shares its output shape with:

• the Jobware Scraper (Germany)
• the jobs.ch, jobup.ch and JobScout24 Scrapers (Switzerland)
• the Jobindex Scraper (Denmark)
• the Jobs.cz Scraper (Czech Republic)
• the Praca.pl Scraper (Poland)
• the BestJobs Scraper (Romania)

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. We answer within one business day.