Scrape public job listings from XING — the leading professional network and job board for the DACH market (Germany, Austria, Switzerland). Extracts job titles, companies, locations, salary ranges, employment types, and more. No login required. No external API key needed.

What it does

The actor fetches XING's jobs search page (/jobs/search) and extracts all job data from XING's embedded Apollo/GraphQL cache — the same structured data that powers the XING website. Because it reads the server-side-rendered data directly (not scraped HTML classes), the parser is resilient to frontend redesigns.

• Keyword search with optional location filter
• Pagination — up to 5 pages × 20 jobs = 100 results per keyword (XING's logged-out cap)
• Multi-keyword support — pass multiple keywords; results are deduplicated by job ID
• Salary extraction — normalized as "55,000–70,000 EUR/yr" when XING provides it
• Confidence scoring — each record has a parse_confidence (0.0–1.0) and warnings field so you know how complete the parse was
• PPE pricing — you pay only for records successfully extracted and pushed

How to use

Basic: scrape software jobs in Berlin

{
  "searchKeywords": ["Software Engineer"],
  "location": "Berlin",
  "maxItems": 100
}

Multiple keywords across Germany

{
  "searchKeywords": ["Product Manager", "UX Designer", "DevOps Engineer"],
  "location": "",
  "maxItems": 300,
  "maxPages": 5
}

Full input reference

Field	Type	Default	Description
searchKeywords	string[]	["Software Engineer"]	Job search keywords. Each runs a separate search.
location	string	""	City or region: "Berlin", "München", "Zürich", etc. Empty = all DACH.
maxItems	integer	100	Total job records cap across all keywords.
maxPages	integer	5	Pages per keyword (max 10). Each page = ~20 jobs.
proxyConfiguration	proxy	RESIDENTIAL	Proxy settings. Actor works without proxy in most cases; RESIDENTIAL is fallback for geo-restrictions.

Output schema

Each record contains:

{
  "job_id": "3423872",
  "title": "Senior Backend Engineer (Python)",
  "company": "TechCorp GmbH",
  "company_id": "2239127",
  "location": "Berlin",
  "zip_code": null,
  "region": "Berlin",
  "country_code": null,
  "employment_type": "FULL_TIME",
  "salary": "70,000–90,000 EUR/yr",
  "salary_min": 70000,
  "salary_max": 90000,
  "salary_currency": "EUR",
  "remote_option": "REMOTE",
  "career_level": "SENIOR",
  "posted_date": "2026-06-01T08:00:00",
  "active_until": "2026-07-01T08:00:00",
  "job_url": "https://www.xing.com/jobs/berlin-senior-backend-engineer-3423872",
  "apply_url": null,
  "description_snippet": "We are looking for a Senior Backend Engineer to join our growing team…",
  "source_query": "Software Engineer",
  "source_page": 1,
  "scraped_at": "2026-06-07T12:00:00Z",
  "parse_confidence": 1.0,
  "warnings": []
}

Fields that XING doesn't expose for a given listing will be null — this is normal. Salary and country code are only available when XING includes them in the search result cache.

Pricing

$1.09 per 1,000 job listings — charged per record pushed to the dataset.

Example:

• 100 jobs → $0.11
• 1,500 jobs → $1.64
• XING caps logged-out results at ~100/keyword — to get more, use more keywords.

You supply compute via your Apify account. No external API keys, no subscriptions.

Access & proxy

XING serves job data to logged-out users without aggressive bot protection. The actor accesses XING reliably without proxy in most cases.

RESIDENTIAL proxy is enabled by default as a fallback for geo-restricted requests. Proxy compute is billed to your Apify account at standard Apify rates — no markup.

XING data limits

XING limits logged-out job searches to approximately 100 results per query (5 pages × 20 items). The boundedTotal field on the XING results page reflects this cap. To collect more jobs across different specializations, use multiple keywords.

FAQ

Does it require XING login? No. All data is extracted from the public logged-out job search.

What DACH locations are supported? Any city or region XING recognizes: Berlin, München, Hamburg, Frankfurt am Main, Zürich, Wien, Köln, etc. Leave location empty to search all of DACH.

Why do some jobs have salary: null? XING only shows salary ranges when the employer explicitly provides them. Most job listings on XING do not include salary data.

Can I get full job descriptions? The description_snippet is extracted from the search result page (up to 350 characters). Full descriptions require loading each job detail page — this increases run time and proxy usage significantly and is not enabled by default.

Why does country_code show null? The XING jobs search page Apollo cache does not include country at the listing level — only city/region. Country is available on individual job detail pages.

How often should I run it? XING job listings refresh continuously. For monitoring purposes, daily or weekly runs are typical.

The actor returned fewer than expected results. XING's logged-out search cap is 100 results per keyword. If you need broader coverage, pass more specific or varied keywords (e.g. ["Python Engineer", "Django Developer", "Backend Python"]).

Legal disclaimer

This actor scrapes publicly available job listings from XING's job search — the same data visible to any logged-out visitor. Job listings are not personal data under GDPR (they describe a position, not an individual).

This actor is not affiliated with, endorsed by, or sponsored by XING SE (a New Work SE company). Use of this tool must comply with XING's Terms of Service and applicable law.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Ashby Job Scraper
• Dice Jobs Scraper
• Glassdoor Scraper
• Greenhouse Job Scraper
• Greenhouse, Lever & Ashby Job Scraper
• Jobstreet Jobs Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.