XING Jobs Scraper

Collect public XING job listings for DACH hiring research. Each dataset record contains the job title, employer, location, employment type, salary estimate when XING displays one, XING job URL, public apply URL, XING refresh time, and collection time.

Use this actor for public vacancy discovery, compensation benchmarking, recruiting intelligence, and labour-market analysis. Its focused scope is public XING job listings; profile and private-account workflows belong in purpose-built tools with the appropriate permissions.

A practical recruiting workflow

Start with a narrow role and location such as data analyst in Berlin. The actor returns normalized job rows that can be grouped by employer, city, employment type, and annual salary range. Keep jobUrl and refreshedAt for later monitoring; use applyUrl only as the public destination supplied by XING.

Input modes

Input	Use it when
searchQuery + location	You want the actor to generate a public XING Jobs search.
startUrls	You already have public XING job or job-search URLs, including advanced filters created on XING.
maxResults	You need a hard cap of 1–100 validated job rows.

{
  "searchQuery": "software engineer",
  "location": "Berlin",
  "maxResults": 20
}

Output data

{
  "jobId": "153735338",
  "title": "Software Engineer (m/w/d)",
  "companyName": "Example GmbH",
  "location": "Berlin",
  "employmentType": "Vollzeit",
  "salaryMin": 60000,
  "salaryMax": 80000,
  "salaryCurrency": "EUR",
  "jobUrl": "https://www.xing.com/jobs/berlin-software-engineer-153735338",
  "applyUrl": "https://careers.example.com/jobs/123",
  "refreshedAt": "ISO-8601 timestamp when supplied by XING",
  "sourceUrl": "https://www.xing.com/jobs/t-software-engineer?keywords=software+engineer",
  "scrapedAt": "ISO-8601 collection timestamp"
}

Records only include public fields that XING exposes on the page. Salary and application fields are null when XING does not show them.

Field	Meaning
title, companyName, location	Core vacancy identity and employer context.
salaryMin, salaryMax, salaryCurrency	XING’s displayed salary estimate, with null for an unavailable estimate.
jobUrl, applyUrl	The public XING source and its public application destination.
refreshedAt, sourceUrl, scrapedAt	Freshness and provenance fields for follow-up monitoring.

Pricing

This actor uses Pay per event with platform usage passed through. A job-found event is charged only after a validated job record is written to the default dataset. An apify-actor-start event covers actor setup. See the live Pricing tab for the effective prices and platform-usage component.

API and agent use

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~xing-jobs-scraper/runs" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchQuery":"software engineer","location":"Berlin","maxResults":20}'

AI agent / MCP prompt:

Find up to 20 public XING software-engineer jobs in Berlin. Return title, employer, location, salary range, job URL, and apply URL. Report missing salary fields as null, then read OUTPUT and RUN_SUMMARY before using the dataset.

The default dataset is paginated by the Apify API; request a small page first and increase the offset for later rows. Every result carries sourceUrl and scrapedAt so an agent can preserve its provenance and freshness context. OUTPUT and RUN_SUMMARY use COMPLETE, PARTIAL, VALID_EMPTY, INVALID_INPUT, or UPSTREAM_FAILED to state the terminal result clearly.

Best results and limits

• Use a precise role query and a practical result cap.
• Use a public XING search URL when you need XING-specific filters beyond role and location.
• Preserve jobUrl, sourceUrl, and scrapedAt for provenance.
• XING pages can evolve and optional fields can be absent. Check RUN_SUMMARY for guidance and use OUTPUT.outcome to distinguish complete, partial, valid-empty, and upstream-status runs.

Builder's note

I designed the actor around the structured state that XING renders with its public job pages instead of guessing from visual card markup. That keeps the record contract compact, preserves the public source and refresh timestamps, and allows missing salary or apply fields to remain explicit null values rather than misleading placeholders.

Focused standalone workflow

This actor is designed as a focused standalone workflow for public XING vacancy collection. Pair its normalized output with your ATS, spreadsheet, BI, or market-analysis workflow after inspecting the run outcome and source timestamps.

Responsible use

This actor collects public job-listing information. Use it for legitimate research in accordance with applicable law, XING’s terms, and your organisation’s data-governance requirements. Keep workflows focused on public listings, authorised access, and human-reviewed employment decisions.