# XING Jobs Scraper | Salaries, Descriptions & Filters (`cauldo/xing-jobs-scraper`) Actor

Export duplicate-free XING jobs with complete descriptions, salary data, and verified filters. Run multiple queries, locations, search URLs, or direct job URLs. Pay only for unique jobs delivered - no separate enrichment charge.

- **URL**: https://apify.com/cauldo/xing-jobs-scraper.md
- **Developed by:** [Cauldo](https://apify.com/cauldo) (community)
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 job 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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## XING Jobs Scraper

Export structured public job listings from XING Jobs. Search by role and
location, reuse public XING search URLs, or scrape individual job URLs. The
Actor returns analysis-ready records with salary data, complete descriptions,
company information, location details, application links, and search
provenance whenever XING publishes those fields.

The scraper is designed for public job-market research, recruiting workflows,
lead generation, salary analysis, and vacancy monitoring across Germany,
Austria, Switzerland, and other locations available through XING Jobs.

### What you get

- Stable XING job IDs and canonical job URLs.
- Job title, company, company profile, logo, and company size.
- City, street, postal code, region, country, and all published locations.
- Employment type, career level, discipline, industry, and workplace mode.
- Salary minimum, maximum, median, currency, and whether it is an estimate or
  an employer-provided range.
- Full description as HTML, plain text, and Markdown.
- Structured company, responsibility, requirement, benefit, and contact
  sections when the listing uses XING's structured template.
- Application URL, application email, and application type when available.
- Activation, refresh, and expiry timestamps, paid/top-job flags, language,
  keywords, and source-search provenance.
- Automatic deduplication across queries, locations, pages, and start URLs.
- A run summary containing request, result, duplicate, exclusion, and partial
  detail-failure counts.

Missing source data is returned as `null` or an empty array. The Actor does not
invent salary, contact, or company information.

### Input

You can combine up to 20 search queries with up to 20 locations. Every query is
searched in every location. You can also supply up to 100 public XING job or
search URLs in `startUrls`.

```json
{
  "queries": ["software engineer", "data engineer"],
  "locations": ["Berlin", "München"],
  "radiusKm": 50,
  "postedWithin": "LAST_WEEK",
  "workplace": ["FULL_REMOTE", "PARTLY_REMOTE"],
  "employmentTypes": ["FULL_TIME"],
  "careerLevels": ["PROFESSIONAL", "MANAGER"],
  "salaryMin": 60000,
  "language": "de",
  "includeDetails": true,
  "maxJobs": 100,
  "maxPagesPerSearch": 10
}
```

Available filters include posting date, radius, workplace mode, employment
type, career level, XING discipline ID, and annual salary bounds. Multiple
values within a filter are treated as OR; different filter categories are
combined as AND. To preserve correct OR behavior, multi-select filters can
create multiple XING searches. Inputs producing more than 500 search
combinations are rejected with a clear message.

Set `includeDetails` to `false` for a faster, lower-cost card-only export. Full
details are required for workplace filtering because logged-out search cards do
not consistently include workplace metadata.

`maxJobs` is a global limit across the whole run, not a per-query limit.
`maxPagesPerSearch` is a safety cap for each generated search.

### Output

Each job is written to the default dataset as soon as it is ready. You can
download the dataset as JSON, CSV, Excel, XML, RSS, or JSONL, or access it from
the Apify API. The **Jobs** dataset view highlights the fields most useful for
reviewing vacancies.

The Actor's **Output** tab links to both the dataset and the final run summary
stored in the default key-value store. A detail page that disappears or changes
during a run does not discard its valid search-card record: that row is returned with
`descriptionStatus: "detail_failed"` and a diagnostic `detailError`.

### Example JavaScript API call

```js
const run = await apifyClient.actor('cauldo/xing-jobs-scraper').call({
    queries: ['product manager'],
    locations: ['Hamburg'],
    includeDetails: true,
    maxJobs: 50,
});

const { items } = await apifyClient.dataset(run.defaultDatasetId).listItems();
```

### Reliability and cost

Residential Apify Proxy is enabled in the input defaults because XING can
throttle repeated logged-out requests. Proxy transfer and Actor compute are
part of the underlying platform usage unless the Actor's pricing page states
that usage is included. Start with a small `maxJobs` value when estimating a
new workflow.

XING may change its public pages or remove listings without notice. The Actor
records malformed search entries and recoverable detail failures in the run
summary. A source-wide access denial or incompatible page change fails the run
instead of silently returning misleading data.

### Responsible use

Scrape only public data and use the results in compliance with applicable law,
XING's terms, and privacy and data-protection requirements. Do not use the Actor
to collect private profiles, bypass authentication, or send unsolicited bulk
messages.

This independent Actor is not affiliated with or endorsed by XING.

# Actor input Schema

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

Job titles, skills or phrases. Each query is combined with every selected location.

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

Cities, regions or countries, for example Berlin, Wien or Switzerland. Empty runs each query without a location.

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

Optional public xing.com/jobs search or individual job URLs. You can mix these with query searches.

## `radiusKm` (type: `integer`):

Optional radius around text locations.

## `postedWithin` (type: `string`):

Restrict results to recently posted jobs.

## `workplace` (type: `array`):

Optional. Match fully remote, hybrid or on-site jobs. Empty keeps every workplace mode.

## `employmentTypes` (type: `array`):

Optional. Keep jobs matching at least one selected XING employment type.

## `careerLevels` (type: `array`):

Optional. Keep jobs matching at least one selected XING seniority level.

## `disciplines` (type: `array`):

Optional XING discipline labels or entity IDs copied from a XING search URL.

## `salaryMin` (type: `integer`):

Optional lower annual salary bound. Jobs without enough salary data are excluded.

## `salaryMax` (type: `integer`):

Optional upper annual salary bound. Jobs without enough salary data are excluded.

## `language` (type: `string`):

Language requested from XING for localized labels.

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

Fetch each public job page for descriptions, structured sections and richer metadata.

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

Maximum delivered jobs across all queries and URLs.

## `maxPagesPerSearch` (type: `integer`):

Safety limit for each query/location combination or search URL.

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

Optional. Residential proxy is recommended for larger or repeated cloud runs.

## Actor input object example

```json
{
  "queries": [
    "software engineer"
  ],
  "locations": [
    "Berlin"
  ],
  "startUrls": [],
  "postedWithin": "ANY_TIME",
  "workplace": [],
  "employmentTypes": [],
  "careerLevels": [],
  "disciplines": [],
  "language": "de",
  "includeDetails": true,
  "maxJobs": 100,
  "maxPagesPerSearch": 10,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `jobs` (type: `string`):

No description

## `summary` (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("cauldo/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 = {}

# Run the Actor and wait for it to finish
run = client.actor("cauldo/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 '{}' |
apify call cauldo/xing-jobs-scraper --silent --output-dataset

```

## MCP server setup

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