# Xing Jobs Scraper (DACH) (`axery/xing-jobs-scraper`) Actor

Scrape Xing job listings across Germany, Austria and Switzerland with company, location and posting date - no login, no browser.

- **URL**: https://apify.com/axery/xing-jobs-scraper.md
- **Developed by:** [Axery](https://apify.com/axery) (community)
- **Categories:** Jobs, News, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.67 / 1,000 results

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?

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 (DACH)

Scrapes job listings from **xing.com**, the leading professional network in Germany, Austria and Switzerland, over plain HTTP — no browser, no login, no cookies.

### How it gets through

Xing's main jobs search (`/jobs/search`) is a client-side microfrontend that only hydrates via GraphQL after JavaScript runs — there is no job data at all in the initial HTML, only a config script naming the GraphQL endpoint. Reverse-engineering that query would require a signed/hashed persisted query this Actor cannot recover from static HTML.

Xing keeps a separate, fully server-rendered SEO path instead: `/jobs/{keyword}` returns plain HTML with real job links, no JavaScript required. This Actor reads that path exclusively. Each linked job page carries a full schema.org `JobPosting` block, the same well-defined vocabulary the Bayt Actor in this suite reads.

### Input

| Field | Type | Notes |
|---|---|---|
| `keyword` | string | A single keyword, e.g. `python`, `projektmanager`. Multi-word phrases work as a hyphenated slug. |
| `maxItems` | integer | Pages automatically until this limit or the reachable depth. |
| `incremental` | boolean | Only listings not seen in previous runs. |
| `proxyConfiguration` | object | Datacenter is sufficient — no IP-reputation gate was observed. |

### Known limits

- **No salary field.** Xing does not publish `baseSalary` via this path in this market — `salary` is present in every row for schema consistency with the other job-board Actors in this suite, but its fields are always null here, not a parsing failure.
- **Modest per-page volume.** The SEO path returns a handful of listings per page rather than dozens — narrower than Xing's full catalogue, but still real, current listings with no login required.
- **Employment type is normalized from German labels** (Vollzeit, Teilzeit, Selbstständig, ...) into the shared FULL\_TIME/PART\_TIME/CONTRACT/INTERNSHIP vocabulary; the original German label is kept in `work_types`.

### Local development

```bash
pip install -r requirements.txt
python test_local.py python --max 20 --out sample_output.json
python test_local.py projektmanager --max 10
```

`sample_output.json` in this folder is real output from a live run, kept so the schema can be reviewed without running anything.

# Actor input Schema

## `keyword` (type: `string`):

A single keyword, e.g. `python`, `projektmanager`, `data-engineer`. Multi-word phrases work as a hyphenated slug.

## `maxItems` (type: `integer`):

Maximum listings to return. The Actor pages automatically (a handful of listings per page on this path) until this limit or the reachable depth.

## `incremental` (type: `boolean`):

Remember job ids between runs and return only listings not seen before. You are charged only for the new rows. Ids are stored in this Actor's key-value store under `seen_job_ids`.

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

Apify Proxy settings. Defaults to Residential - built in the same batch as sibling DACH-market sites that needed TLS-fingerprint rotation to get past their WAF.

## Actor input object example

```json
{
  "keyword": "python",
  "maxItems": 50,
  "incremental": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

One row per listing: title, company with Xing profile link, structured DACH location, employment type, industry and posting/expiry dates.

# 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 = {
    "keyword": "python",
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("axery/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 = {
    "keyword": "python",
    "maxItems": 50,
}

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

```

## MCP server setup

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