XING Jobs (DACH) Scraper

XING is the largest business network and job board across Germany, Austria and Switzerland. This Actor walks XING's own public job sitemap and visits each job's own page to return one row per posting — title, company, location, employment type, posted date, industry and (optionally) the full description. No login, no browser, no search query.

What you get

• Live jobs straight from XING's own sitemap, not a stale export — every run reads the current freshest batch of listed jobs.
• Full job detail, not a search-result teaser. Since XING's job search itself needs a browser session, this Actor reads each job's own public page directly — the same structured data XING publishes for search engines.
• Optional keyword filter. Keep only jobs whose title contains your term — applied after fetching, since there is no server-side search available here.
• Honest churn handling. A meaningful share of freshly-listed postings are already withdrawn by the time this Actor visits them (temp-staffing boards rotate fast) — those are skipped for free, never billed, never treated as a failure.
• Runs on Apify: schedule it, monitor it, call it from the API or the MCP server, export to JSON, CSV or Excel, or push results straight into your own pipeline.

How to run it

1. Click Try for free — no card needed on the free plan.
2. Set Max jobs to return (or leave the default).
3. Optionally add a Keyword filter to only keep matching titles.
4. Press Start. Results appear in the dataset — read them in the UI, pull them from the API, or have a webhook push them onward.

Pricing

Pay-per-event: $0.005 per run start + $0.003 per job found. No monthly seat, no minimum. 100 jobs cost about $0.31; 1,000 jobs about $3.01.

A withdrawn posting (HTTP 410 — routine on this board), a keyword that matched nothing, or a sitemap that failed to load is still logged with found: false and the reason where one exists — and it is not charged for. You pay for jobs actually delivered, not for attempts.

Input

Field	Required	What it does
max_items	no	Target number of job rows to deliver (default 20, max 200). This is a target, not a guarantee — see the note on withdrawn postings above.
freshness_days	no	Skip sitemap entries older than this many days (default 14). XING's own sitemap batches are typically only minutes to hours old, so this rarely filters anything in practice.
keyword_filter	no	Case-insensitive substring match against each job's title, applied on this Actor's side. Leave empty to keep every job found.
fetch_full_description	no	Include the full description text in the output row (default true). The job's own page is fetched either way — this only controls whether the text is kept.
sitemap_override_url	no	Advanced/diagnostic: override the sitemap URL this Actor walks. Leave empty for normal use.

{
    "max_items": 3
}

Output

One dataset row per job found. This is a real row from a real run (31.07.2026):

{
    "found": true,
    "url": "https://www.xing.com/jobs/minfeld-steuerfachkraft-minfeld-mindestens-52-000-100-remote-156829244",
    "job_id": "156829244",
    "title": "Steuerfachkraft (m/w/d) in Minfeld mindestens 52.000€ - 100% Remote möglich",
    "company": "Taxtalente.de",
    "company_url": "https://www.xing.com/pages/taxtalente",
    "location": "Minfeld, Rheinland-Pfalz",
    "country": "DE",
    "employment_type": "Vollzeit",
    "posted_date": null,
    "salary_raw": null,
    "description": "TaxTalente ist eine junge Job-Matching Plattform für Jobsuchende und Unternehmen in der Steuerberatung. Unser Anspruch ist es, Bewerbern in der Steuerberatung das Leben zu vereinfachen und ihnen zu ihrem Traumjob zu verhelfen. Auf Basis deiner Wünsche können wir dir deinen passenden Job, aus der Vielzahl von Top-Kanzleien in unserem deutschlandweiten Netzwerk vorschlagen und dir vollumfänglich mit unserer Expertise beratend zur Seite stehen. Derzeit suchen wir nach einer Steuerfachkraft (Steuerfachangestellter, Steuerfachwirt oder Bilanzbuchhalter) für eine unserer Partner-Kanzleien in Minfeld",
    "description_is_teaser": false,
    "source_board": "xing-jobs",
    "scraped_at": "2026-07-31T14:21:25.480Z",
    "industry": "Personaldienstleistungen und -beratung",
    "valid_through": "2027-07-30T06:03:10.000Z",
    "direct_apply": true,
    "listed_at": "2026-07-30T06:03:08.000Z"
}

Field	What it means
found	Whether this row is a real job (true) or a notice/error row (false)
url	Direct link to the job posting — the unique key for this row
job_id	XING's own numeric job id (read from its own URL — XING's structured data carries no separate identifier field)
title	Job title
company	Hiring company name
company_url	Link to the company's XING page, when the posting has one — null otherwise
location	City and region as XING shows it
country	Country code (DE, AT or CH)
employment_type	XING's own label, e.g. "Vollzeit" (not translated)
industry	XING's own industry label for the posting (not translated)
posted_date	The date the posting's OWN text states, in the exact German phrasing this Actor looks for ("ausgeschrieben am DD.MM.YYYY") — null whenever that phrase isn't in the description (common on direct-employer/corporate-template postings, roughly a quarter of samples), never a guess.
listed_at	XING's own raw datePosted from the posting's structured data — this is a relisting/refresh timestamp the source itself can carry for months without it reflecting when the job was really first posted, which is exactly why posted_date above is extracted from the text instead of taken from this field.
valid_through	ISO 8601 timestamp — when the posting expires, per XING
direct_apply	Whether XING flags this posting for its own one-click "quick apply"
salary_raw	Always null on this board — XING's DACH postings do not publish a salary field at all; this Actor never estimates or invents one
description	Full job description (HTML tags stripped), up to 600 characters, or null when fetch_full_description is off
description_is_teaser	Always false when description is present — every row comes from the job's own full page, never a search-result snippet
source_board	Always "xing-jobs"
scraped_at	When this Actor fetched the row

A run whose keyword filter matched nothing (or whose entire candidate batch turned out withdrawn/filtered) pushes:

{ "found": false, "error": "", "source_board": "xing-jobs", "scraped_at": "..." }

A run whose sitemap failed to load pushes an error row with a non-empty error (e.g. "http 404") — never the same shape as "no matches".

API

Start a run with a bearer token and explicit JSON input:

curl -sS -X POST 'https://api.apify.com/v2/acts/zinin~xing-jobs/runs?waitForFinish=60' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"max_items":3}'

Read Dataset rows using the returned defaultDatasetId:

curl -sS "https://api.apify.com/v2/datasets/$DEFAULT_DATASET_ID/items?clean=true&format=json" \
  -H "Authorization: Bearer $APIFY_TOKEN"

MCP

For an Apify MCP client exposing the standard call-actor tool, send this exact payload:

{
  "name": "call-actor",
  "arguments": {
    "actor": "zinin/xing-jobs",
    "input": {
      "max_items": 3
    }
  }
}

Other tools we built

Need the rest of the picture?

These run on the same account, take the same shape of input and bill the same way, so they slot into an existing pipeline without new plumbing.

Actor	Use it when
jobs.ch Swiss Jobs Scraper	You want the same DACH region's Swiss board covered too, not just Germany/Austria via XING.
Company Hiring Radar	You already know the company and want every open role straight from its own ATS (Greenhouse/Lever/Ashby), not a board listing.
Job Postings Aggregator	You need one normalized feed pulled across several companies' own ATS pages, beyond a single board.
Layoff Tracker	You want a labor-market signal (recent layoffs) on a company that's also posting XING jobs.

FAQ

Does it need an API key / login? No — it reads XING's public sitemap and public job pages, no session required.

Why do I sometimes get fewer jobs than max_items? A meaningful share of freshly-listed jobs on this board are withdrawn (HTTP 410) within hours of being listed — this Actor automatically tries extra candidates to compensate, but on a small max_items value it can still occasionally return less than asked if the board's live churn that moment is unusually high.

Why is salary_raw always null? Because XING's DACH job postings do not publish a salary field at all. This Actor never estimates or guesses a number.

Can I filter by keyword? Yes, via keyword_filter — a case-insensitive match against the job title, applied after this Actor fetches each candidate page (XING's own job search needs a browser session and is not used here).

How fresh is the data? Live at run time — XING regenerates its job sitemap on the order of every few tens of minutes.

Can I call it from an AI agent? Yes — standard Apify Actor, callable from the Apify API, the SDK, or the Apify MCP server.

What this is NOT. It does not apply to jobs on your behalf, does not cover job boards outside xing.com, and does not invent a salary figure when the source has none.

Found a wrong result, or need a check we don't run? Open an issue on this Actor's page.

---

Built by zinin. Questions? Telegram @timzinin.