XING Jobs Scraper

💰 $2.70 / 1 000 results  ·  pay only for results  ·  no credit card to try

We run the gauntlet. 😈

Scrape job listings from XING, the DACH region's leading professional network, keyed by keyword and an optional location. Get clean, deduplicated rows — title, company, location(s), employment type, salary range, key responsibilities, and posting/expiry dates — ready for a recruiter pipeline or a hiring-intent feed.

🎯 What this scrapes

XING lists thousands of German, Austrian, and Swiss job postings, 20 to a page, with no bulk export. This Actor searches by keyword and optional location, walks the result pages, and returns one row per job: title, company (with logo), city and full location list, employment type, salary range (when published), key responsibilities, and posted/expiry timestamps.

🔥 Features

• 🛡️ We rotate browser fingerprints (curl-cffi impersonation — Chrome and Firefox) so XING sees a real browser's TLS handshake, not a Python script.
• 🔁 We retry with exponential backoff on rate limits and server errors, honouring Retry-After.
• 🌐 We rotate residential proxies through Apify Proxy, pinned to Germany, on every run.
• 🧊 Run-wide deduplication. The same job id never appears twice in your dataset, even across pages or across multiple keywords in one run.
• 🧾 Multi-keyword batching in one run — search several terms at once and every row is tagged with the keyword (and location) that found it.
• 💰 You pay only for results that land. No data → no charge (only the small actor-start warm-up fee).

💡 Use cases

• Recruiters and staffing agencies — pull every open role matching a skill or title across DACH employers.
• Job boards and aggregators — backfill DACH-region postings your existing sources miss.
• Sales / BD teams — new job openings are a public hiring-intent signal; a company opening five engineering roles just funded a team.
• Market research — track which titles, locations, and salaries a sector is hiring for over time.

⚙️ How to use it

1. Set one or more keywords — the search terms to run.
2. Optionally set location — applied to every keyword in the run.
3. Set maxResults and maxPagesPerKeyword to bound how much you pull per run.
4. Run it, then export to JSON, CSV, or Excel — or pull the dataset straight from the Apify API.

📥 Input

Field	Type	Required	Default	Notes
keywords	array<string>	yes	—	Search terms; one search runs per keyword.
location	string | null	no	null	Applied to every keyword in the run.
maxResults	integer	no	100	Hard cap on total rows emitted across all keywords (1-2000).
maxPagesPerKeyword	integer	no	10	Safety cap on pages fetched per keyword, 20 rows/page (1-50).
proxyConfiguration	object	no	Residential, DE	Apify Proxy configuration.

Example input

{
  "keywords": ["developer", "marketing"],
  "location": "Berlin",
  "maxResults": 50,
  "maxPagesPerKeyword": 2
}

📤 Output

One row per deduplicated job matching your search.

Field	Type	Notes
id	string	Stable job id, dedupe key.
slug	string	XING's URL slug for this job.
title	string	Job title.
url	string	Absolute job URL.
companyName	string	Hiring company's display name.
companyLogoUrl	string | null	96px company logo, if published.
locationCity	string | null	Primary listed city.
locations	array<string>	All listed cities; may be multi-city.
employmentType	string | null	e.g. "Full-time".
salaryMin / salaryMax	integer | null	~20% of postings don't publish salary at all.
salaryMedian	integer | null	Sparser than min/max by design. XING serves two salary shapes: its own SalaryEstimate (carries a median) and an employer-stated SalaryRange (min/max only, no median). Measured on a live page: 44 estimates vs 28 ranges, so expect a median on roughly two-thirds of the postings that publish salary at all.
salaryCurrency	string | null	e.g. "EUR".
keyResponsibilities	array<string>	Bullet list; may be empty.
refreshedAt	string	ISO-8601 last-refreshed timestamp.
activeUntil	string | null	ISO-8601 expiry timestamp, if published.
paid	boolean	Paid/sponsored listing flag.
topJob	boolean	Top-job placement flag.
sourceKeyword	string	Input keyword that produced this row.
sourceLocation	string | null	Input location that produced this row.

💰 Pricing

Pay-Per-Event — you pay only when these events fire:

Event	USD	What it is
actor-start	$0.20	One-off warm-up charge per run
result-emitted	$0.0025	Per deduplicated job posting written to the dataset

Example: 1 000 job postings = $2.70 per run ($0.20 start + 1000 x $0.0025). No subscription, no minimum, no card required to try it.

🚧 Limitations

• List-page fields only. This returns the fields XING's search result page publishes; full job-description text isn't fetched — use the returned url for a follow-up detail-page job.
• Semantic search. XING ranks results by relevance, not just keyword match — a niche keyword can surface adjacent roles rather than an empty page.
• A narrow search can legitimately return zero rows. That's a successful run, not a failure — widen your keyword or drop the location filter.

❓ FAQ

Do I need a XING account or API key? No. This reads XING's public search result pages.

Why did my run return fewer rows than maxResults? Either the search genuinely has fewer matching jobs than your cap, or maxPagesPerKeyword stopped the run first — the status message tells you which.

Can I search multiple keywords in one run? Yes — pass an array to keywords; every row is tagged with the keyword that found it via sourceKeyword.

Can I run this on a schedule? Yes — use Apify Schedules to re-run your keyword set on a cadence and catch newly posted jobs.

💬 Your feedback

Found a bug, or need a field we don't return yet? Open an issue on the Actor's Issues tab — we read every one.