# Jobs.at Scraper - Austrian Job Listings · $1.5/1K (`listingworks/jobs-at-scraper`) Actor

Job postings from jobs.at with title, employer, place, working time, salary floor and posting time.

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

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

```json
{
  "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.

# Actor input Schema

## `searchTerms` (type: `array`):

Keywords to search for, e.g. pflege, verkauf, buchhaltung. Each keyword is its own search. Leave empty for all postings.

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

An Austrian town, district or state as jobs.at writes it (e.g. Wien, Linz, Graz, Niederösterreich). Leave empty for all of Austria. A place the site does not know fails the run instead of returning an empty or unfiltered list.

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

Return only postings from this date-time on, e.g. 2026-09-20T00:00:00+02:00. jobs.at lists by relevance, not by date, so a run with a cutoff reads the whole search and keeps the newer postings.

## `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. jobs.at serves 15 postings a page and every page of a search can be read.

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

# Actor output Schema

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

All Austrian 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": [
        "pflege"
    ],
    "location": "Wien",
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("listingworks/jobs-at-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": "Wien",
    "proxyConfiguration": { "useApifyProxy": False },
}

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

```

## MCP server setup

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