# Karriere.at Multi-Query Austrian Vacancy Export (`jpmarketdata/karriere-at-multi-query-vacancy-export`) Actor

Export public Austrian karriere.at vacancies across job-role searches. Deduplicate source IDs and get company, exact source dates, original salary amount/unit/floor, optional contact-minimized text and explicit bounded coverage.

- **URL**: https://apify.com/jpmarketdata/karriere-at-multi-query-vacancy-export.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** Jobs, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 unique vacancy delivereds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Karriere.at Multi-Query Austrian Vacancy Export

Export current public Austrian karriere.at vacancies for up to three role phrases in one location. One stable source ID becomes one row, with employer, exact source dates where present, original salary wording and unit, source provenance, and optional contact-minimized description. Schedule the same input and compare IDs with your own snapshots. Independent tool; not affiliated with karriere.at.

### Input

`queries`:1–3 nonempty job-role phrases, default\["python","data analyst"]. `location`: one city/region text, default"Wien"; blank searches across Austria. `maxItemsPerQuery`:1–25,default10; each query inspects at most two15-job pages. Every selected query is inspected and overlapping IDs are merged. `includeDescription`:true by default; false suppresses description output while detail pages still supply dates and salary semantics. No pasted URLs, authentication, contact lookup or application actions.

### Output

One unique source vacancy per dataset row. Employer/advertiser name and company profile link; location text and source city/region/country; source employment type, exact datePosted and optional validThrough; salaryRaw, source numeric amount/min/max/currency/unit and lower-bound flag; source home-office boolean; optional contact-minimized plain description; public apply target; matchedQueries/sourceSearchUrls/rank, outputLimited and observedAt. Missing source values remain null or empty arrays. Source amount is not an annual salary or guaranteed final pay. An `ab` amount is a floor, never an equal min/max range. COVERAGE in key-value storage reports each query, inspected pages/IDs, source count, limits, delivered counts and delivery state. The full export is bounded to the inspected pages, not all Austria or all matches. Relevance/promoted ordering is source-defined. This Actor does not maintain history or detect changes itself.

### Pricing

$0.0015 per successfully delivered unique `vacancy-delivered` dataset row ($1.50/1000). No start, search, detail, default-dataset, coverage, empty or failed-row event. Default at most20 unique jobs costs at most$0.03; maximum75 costs at most$0.1125 before any platform-specific presentation/discount. No separate Actor trial item allowance; ordinary Apify credit and user spending caps apply equally to FREE accounts. Descriptions do not add a second event.

### Limits

Normal HTTPS only, no browser/proxy/login/paid API. 256MB; at most3queries,2pages/query,25selectedjobs/query and75uniquejobs/run;90HTTPattempts,64MiB decompressed aggregate,2MiB/page,10secondrequest timeout and240second acquisition deadline. Requests start at least1second apart, concurrency1; at most2 transient retries per request within90attempts. Planned item/page caps return explicit partial coverage. Authentication, rate limit exhaustion, unexpected positive-count empty/malformed pages, detail identity mismatch, source structure change, repeated page or runtime byte/time/request exhaustion fail before any rows or billable event. Individual clearly removed vacancies are withheld and counted; other detail failures fail the staged acquisition. An all-zero eligible union fails NO_MATCHES, with uncharged coverage. Successful query zero may coexist with positive others. Source/source-parse failures stage before charging. SDK delivery is not atomic: spending caps or later delivery/report failures can leave earlier rows delivered/charged. Never promise rollback or an entirely free failed run; reconcile dataset/PPE before retry after an ambiguous acknowledgement. COVERAGE explicitly marks partial delivery and cap reason where possible.

### Privacy

No candidate profiles, CVs, applications, personal accounts, recruiter/contact fields, employer-site crawling, email/phone extraction or raw response storage. Descriptions remove obvious contact sections, mailto/tel links, email addresses and phone patterns; arbitrary names in running prose can remain, so this is contact minimization rather than guaranteed anonymization. Descriptions can be disabled. Fixtures contain synthetic organization/text examples, no live personal names or contacts. The source terms restrict automated evaluation and limit information use to personal job search/private use; this tool does not grant permission to reuse source content. Retain source links/attribution; no licence or endorsement is claimed.

# Actor input Schema

## `queries` (type: `array`):

One to three nonempty role/skill phrases. Every selected phrase is searched in the chosen location; source relevance order and matching-query provenance are retained.

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

One source location term, e.g.Wien or Graz. Blank means Austria-wide; no inferred country/location coverage.

## `maxItemsPerQuery` (type: `integer`):

1..25 selected unique jobs per phrase,default10; at most2sourcepages of~15jobs each. Union capped75. Explicit partial coverage when source has more.

## `includeDescription` (type: `boolean`):

Include contact-minimized plain text up to 12,000 characters. Disable to omit text; company, date and salary still come from the vacancy detail. No extra event.

## Actor input object example

```json
{
  "queries": [
    "python",
    "data analyst"
  ],
  "location": "Wien",
  "maxItemsPerQuery": 10,
  "includeDescription": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `coverage` (type: `string`):

No description

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jpmarketdata/karriere-at-multi-query-vacancy-export").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("jpmarketdata/karriere-at-multi-query-vacancy-export").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 '{}' |
apify call jpmarketdata/karriere-at-multi-query-vacancy-export --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/karriere-at-multi-query-vacancy-export"
        }
    }
}
```

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/APLuCoefzQOIHSMEP/builds/ATOl4TIiSpxmrxs5v/openapi.json