# XING Jobs Scraper: DACH Jobs with Salary \[USD 0.75/1K] (`usefulapi/xing-jobs-scraper`) Actor

Scrape XING job ads in Germany, Austria and Switzerland by job title and city: title, employer, place, stated salary with period, employment type, remote/hybrid, career level, discipline, full description and dates. USD 0.75 per 1,000 jobs.

- **URL**: https://apify.com/usefulapi/xing-jobs-scraper.md
- **Developed by:** [Useful API](https://apify.com/usefulapi) (community)
- **Categories:** Jobs, Lead generation, 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 jobs

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

## XING Jobs Scraper: jobs in Germany, Austria and Switzerland

Scrape job ads from **XING**, the professional network of the German-speaking countries, by job title and city: title,
employer, city, region and postcode, salary stated by the employer (with its period), employment type, remote /
hybrid / on-site, career level, discipline, industry, full description, publication and expiry dates, and the apply
link. Export to CSV, Excel or JSON, or use the API.

**USD 0.75 per 1,000 jobs.** No login, no browser.

### What you get

- **Stated salaries only, by default.** XING shows its own salary estimates on most list entries; they are kept apart
  in `extra.salaryEstimate` (or put in the salary fields if you switch on "include salary estimates"), never mixed in
  silently.
- **Work place option** (remote, hybrid, on-site), career level and discipline from each job page.
- **Full description** and exact dates from the job page's structured data.

### Input examples

Nurses in Berlin:

```json
{ "keywords": ["Pflegefachkraft"], "locations": ["Berlin"], "maxJobs": 50 }
```

Software developers in several cities, new jobs only (daily schedule):

```json
{ "keywords": ["Softwareentwickler"], "locations": ["München", "Hamburg", "Wien", "Zürich"], "onlyNewJobs": true }
```

### Good to know

XING shows readable jobs on its city job pages (keyword in a city), about 20 per page, and hides some entries from
visitors who are not logged in. This scraper reads those public pages, so give one or more cities for each job title
(if you give none, it searches nine large DACH cities). Very broad searches return the newest part of XING's results
per city, not every job XING lists.

### Who uses it

- **Recruiters and staffing agencies in DACH:** new vacancies by title and city every morning.
- **Salary research:** employer-stated salaries by role and region.
- **Sales teams:** companies hiring in your market (company data only, no personal data).

### Output: one row per job

Every Actor in this family writes the same columns, so you can merge boards in one sheet or database.

| Field | What it holds |
|---|---|
| `jobId` | The board's own job id |
| `title`, `company` | Job title and hiring company (as the board shows them) |
| `companyUrl`, `companyLogoUrl` | Company page and logo on the board, when given |
| `location`, `city`, `region`, `postalCode`, `country` | Location as shown, and its parts; `country` is an ISO code (FR, DE, US...) |
| `remote`, `workplaceType` | `true`/`false` and `remote`, `hybrid` or `onsite`, only when the board says so |
| `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod`, `salaryText` | Salary range as numbers, ISO currency, `HOUR`/`DAY`/`WEEK`/`MONTH`/`YEAR`; empty when the board gives none (never guessed) |
| `employmentType`, `employmentTypeText` | `FULL_TIME`, `PART_TIME`, `TEMPORARY`, `INTERN`, `APPRENTICE`, `CONTRACTOR`, `FREELANCE`..., and the board's own wording |
| `experienceLevel`, `category`, `skills` | When the board gives them |
| `datePosted`, `validThrough` | ISO 8601 dates |
| `descriptionText`, `descriptionHtml` | Full description as plain text and as HTML |
| `applyUrl`, `jobUrl` | Where to apply, and the job's page on the board |
| `sourceBoard`, `searchLabel`, `scrapedAt` | Which board, which of your searches found it, when |
| `duplicateKey` | The same key for the same ad posted on several boards (or reposted): title without (m/w/d) or H/F tags, company without legal form, city, country. Use it to merge results from several of our board Actors |
| `extra` | A few fields only this board has |

Contact email addresses and phone numbers inside descriptions are removed: this Actor never collects recruiters'
personal contact details.

### Job alerts: only new jobs, sent where you work

1. Switch on **Only new jobs since the last run** and schedule the Actor (daily, hourly). It remembers the jobs it
   has already delivered for the same searches and filters, in a key-value store on your own account (named job-boards-seen-<board>), and saves only
   new ones. The first run delivers everything and remembers it. **Memory name** shares one memory between schedules,
   or starts fresh.
2. Paste a **Slack or Discord webhook** (or a Zapier or Make webhook, which can email you) into **Send new jobs to**.
   After each run that found new jobs you get one message with the count and up to 10 jobs with their links.
   Free: the message is never billed.

Apify's own integrations (Google Sheets, email, webhooks) work too.

### Pricing

Pay per job saved: **USD 0.75 per 1,000 jobs** (USD 0.00075 a job), plus USD 0.002 per run start. No
monthly rental, no charge for jobs skipped as duplicates, already seen or filtered out. Set a maximum cost per run in
Apify and the Actor stops just before it, keeping everything saved so far.

### Use it through the API

```bash
curl -X POST "https://api.apify.com/v2/acts/usefulapi~xing-jobs-scraper/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keywords":["Pflegefachkraft"],"locations":["Berlin"],"maxJobs":20}'
```

Python: `ApifyClient("YOUR_API_TOKEN").actor("usefulapi/xing-jobs-scraper").call(run_input={...})`, then read the dataset items.

### Good to know

- **Polite by design:** one request at a time per site with a pause between requests, and the site's robots.txt is
  followed. Runs read public job pages only: no login, no candidate profiles or CVs.
- **What a run summary tells you:** the `OUTPUT` record has jobs saved per search, jobs skipped (duplicates, seen
  before, too old) and why a run stopped early, if it did.
- **Is it legal?** The Actor reads job ads that the board publishes openly, the same pages a job seeker sees. You are
  responsible for how you use the data (for example, the board's terms and data protection rules in your country).
- **Found a problem?** Open an issue on the Issues tab: we answer quickly.

# Actor input Schema

## `keywords` (type: `array`):

One search per line, as a job title (for example Pflegefachkraft, Softwareentwickler, Buchhalter). XING only shows readable jobs on city pages, so each keyword is searched in every city below.

## `locations` (type: `array`):

Cities in Germany, Austria or Switzerland (Berlin, Hamburg, Wien, Zürich). Each keyword is searched in each city, 20 results per page. Leave empty to search nine big cities (Berlin, Hamburg, München, Köln, Frankfurt am Main, Stuttgart, Düsseldorf, Wien, Zürich).

## `employmentType` (type: `string`):

Only jobs of this type (read from the result list).

## `workplace` (type: `string`):

Only jobs with this work place option (read from each job page, so job pages must be on).

## `includeSalaryEstimates` (type: `boolean`):

Most jobs in the result list show a salary range that XING estimates itself (the job page does not show it). Off: only salaries given by the employer are filled in, estimates go to extra.salaryEstimate. On: estimates fill salaryMin and salaryMax too (extra.salaryKind says estimate).

## `startUrls` (type: `array`):

Paste XING job list pages such as https://www.xing.com/jobs/pflegefachkraft-jobs-in-berlin. When given, the fields above are ignored. The XING search page (/jobs/search) cannot be used.

## `maxJobs` (type: `integer`):

Stop after saving this many jobs (across all searches). You pay only for jobs saved.

## `postedWithinDays` (type: `integer`):

Only jobs published in the last N days. 0 = any date.

## `onlyNewJobs` (type: `boolean`):

Remembers the jobs already delivered for these searches (in a key-value store on your account) and saves only jobs not seen before. Ideal for daily or hourly schedules and job alerts. The first run delivers everything and remembers it.

## `stateKey` (type: `string`):

Use the same name on several schedules to share one memory, or a new name to start fresh. Letters, digits, - and \_. Empty = one memory per set of searches.

## `includeDetails` (type: `boolean`):

Reads each job's own page for the full description and extra fields. Turn off for faster runs with list fields only (same price per job).

## `notifyUrl` (type: `string`):

Paste a Slack or Discord webhook link, or a Zapier or Make webhook (which can email you). After each run that saved jobs you get one message with the count and up to 10 jobs with their links. With 'Only new jobs' on and a schedule, this is a free job alert. Not billed.

## `descriptionFormat` (type: `string`):

Plain text, HTML, both, or none (smaller datasets).

## `maxJobsPerSearch` (type: `integer`):

Cap for each search line, so one broad search does not use up the whole run. 0 = no cap.

## `proxyConfiguration` (type: `object`):

Not needed for XING in our tests. Apify datacenter proxy or your own proxies only; residential proxy is not supported.

## Actor input object example

```json
{
  "keywords": [
    "Pflegefachkraft"
  ],
  "locations": [
    "Berlin"
  ],
  "includeSalaryEstimates": false,
  "maxJobs": 20,
  "postedWithinDays": 0,
  "onlyNewJobs": false,
  "includeDetails": true,
  "descriptionFormat": "both",
  "maxJobsPerSearch": 0,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

One row per job, same columns on every board of this family. Download as CSV, Excel or JSON.

## `summary` (type: `string`):

Jobs saved per search, jobs skipped (duplicates, seen before, too old), pages read and why the run stopped early (if it did).

# 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 = {
    "keywords": [
        "Pflegefachkraft"
    ],
    "locations": [
        "Berlin"
    ],
    "maxJobs": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("usefulapi/xing-jobs-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 = {
    "keywords": ["Pflegefachkraft"],
    "locations": ["Berlin"],
    "maxJobs": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("usefulapi/xing-jobs-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 '{
  "keywords": [
    "Pflegefachkraft"
  ],
  "locations": [
    "Berlin"
  ],
  "maxJobs": 20
}' |
apify call usefulapi/xing-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,usefulapi/xing-jobs-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/iwxBSdrzhTAuahvZe/builds/eFON1ChjYIpJZFvHn/openapi.json