Jobs.at Scraper - Austrian Job Listings · $1.5/1K
Pricing
from $0.75 / 1,000 result items
Jobs.at Scraper - Austrian Job Listings · $1.5/1K
Extract job postings from jobs.at (Austria) by keyword and location: title, employer, place, working time, minimum salary, posting time, URL.
Pricing
from $0.75 / 1,000 result items
Rating
0.0
(0)
Developer
Yusuke Suda
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
Jobs.at Scraper — Austrian job listings by keyword and place
Extract job postings from jobs.at (Austria) by keyword and location: title, employer, place, working time, minimum salary, posting time, URL.
Three rows from a real run
| Title | Employer | Location | Salary | Posted |
|---|---|---|---|---|
| ZERSPANUNGSTECHNIK DREHEREI (M/W/D) | RO-RA Aviation Systems GmbH | Schörfling Am Attersee | 3600 EUR per month | 2026-10-10T06:30:17+02:00 |
| Techniker*in (m/w/d) Instandhaltungs- & Servicetechnik Logis… | Österreichische Post AG | Oberwang | 2752.47 EUR per month | 2026-10-10T06:30:17+02:00 |
| KFZ -Techniker:in Tamsweg (m/w/d) | ÖAMTC Salzburg | Litzelsdorf, Tamsweg | 3118 EUR per month | 2026-10-10T06:30:17+02:00 |
A run with maxItems: 10 on 2026-10-13 returned 10 postings in 5 seconds and would cost about $0.02 at the current price. Full fields for every row are shown below.
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. 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.
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.
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 | About 3 in 10 (32 of 100) |
employment_type | Working time | Always |
salary_min, salary_currency, salary_period | Salary from; Salary currency; Salary period | Nearly all (99 of 100) |
posted_at | Posted | Always |
source_url, external_id | Posting URL; Posting ID | Always |
salary_max, application_deadline, company_url, company_rating, workplace_postal_code, workplace_address, latitude, longitude | Catalogue-wide columns; jobs.at's list does not show them | Always empty here |
Fill rates are from a 100-row run on 28 September 2026.
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. |
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 | 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.
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. jobs.at does not list
strictly newest first, so the run reads the whole search and keeps what is
new; nothing newer further down the list is missed. A daily task for pflege
in Wien returned 39 new postings on 29 September 2026 and left out 344 older
ones.
How this compares
Another Actor on the Store covers jobs.at, together with karriere.at. Checked on 2 October 2026 from its Store description and input form:
- Results page only. It can fetch each posting's full details. This Actor never opens a posting: it reads the search results only.
- No personal data. It does not advertise contact persons. This Actor
collects no contact person, e-mail address or phone number;
companyis the employer's name only. - One price per row. It also charges per row. Here every row costs the same, and you pay only for rows you receive.
- Daily new postings. It has no date filter. Here
sinceDaysis a rolling window you set once on a scheduled task.
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 ends with no rows and a warning. 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. The Actor then reads its own example search: if that works, the site is fine and your search has nothing, so the run succeeds with no rows and says so in the log; if the example fails too, the site is the problem and the run fails.
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.