XING Jobs Scraper - Jobs in Germany, Austria and Switzerland
Pricing
from $0.50 / 1,000 job returneds
XING Jobs Scraper - Jobs in Germany, Austria and Switzerland
Scrape XING job listings by keyword and location, or paste XING job search URLs. Title, company, location, employment type and salary as clean JSON. Optional description, posting date and industry. From $0.50 per 1,000 jobs, no login, no cookies.
Pricing
from $0.50 / 1,000 job returneds
Rating
0.0
(0)
Developer
DataSignals Lab
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
18 hours ago
Last modified
Categories
Share
XING Jobs Scraper: job listings from Germany, Austria and Switzerland
Get the job listings behind any XING job search as clean JSON: title, company, location, employment type and the salary range when XING shows it. Tick one box to add the job description, posting date, closing date, industry and address. Built for recruiters, sales teams and researchers who need the German-speaking market, where many employers post on XING and not on the international boards.
Search by keyword and location, or set your filters on XING in the browser and paste the URL of the result page. No login, no cookies, no API key, no proxy setup. It reads the public job pages XING shows to visitors who are not signed in.
Run it with the default input to see it work. It returns the newest Python jobs in Berlin.
What you get
One row per job:
| field | meaning |
|---|---|
job_id | XING's id for the job, stable across runs |
title | Job title |
company | Hiring company |
location | Location as shown on the result card |
employment_type | For example Full-time or Part-time, when the card shows it |
salary | Salary range, when XING shows it on the card. Often an estimate by XING |
badge | Labels XING puts on the card, for example Urgently hiring or Last chance |
company_logo | URL of the company logo |
url | Link to the job on XING |
search_url | The XING search this job came from |
description | Job description as plain text, up to 5,000 characters. Only with includeDescription |
date_posted | Posting date, ISO 8601. Only with includeDescription |
valid_through | Closing date of the posting. Only with includeDescription |
industry | Industry of the employer. Only with includeDescription |
company_url | The employer's XING page. Only with includeDescription |
city | City from the posting. Only with includeDescription |
region | State or region. Only with includeDescription |
country | Two-letter country code. Only with includeDescription |
Example row:
{"job_id": "156675213","title": "Python Developer Financial Services (all genders)","company": "Exxeta","location": "Berlin","employment_type": "Full-time","salary": "EUR 59,000 to 86,000","badge": "Urgently hiring","company_logo": null,"url": "https://www.xing.com/jobs/berlin-python-developer-financial-services-all-genders-156675213","search_url": "https://www.xing.com/jobs/search?keywords=python&location=Berlin&sort=date","description": "We are looking for a Python developer who...","date_posted": "2026-09-17T05:36:36Z","valid_through": "2027-01-22T21:35:50Z","industry": "Consulting","company_url": "https://www.xing.com/pages/exxetaag","city": "Berlin","region": "Land Berlin","country": "DE"}
How to scrape XING jobs with this Actor
- Open the Actor in the Apify Console and click Try for free. The form is prefilled with one search term and one location.
- Type your search terms, one per line, and the cities or regions as you would type them on XING. Or paste XING job search URLs with your filters into
startUrls. - Tick
includeDescriptionif you need the job text, the posting date and the detail fields. Leave it off for a cheap list. - Set
maxJobsas your budget cap and click Start. Export the dataset as JSON, CSV or Excel from the Storage tab. - From code, call
POST /v2/acts/datasignalslab~xing-jobs-scraper/run-sync-get-dataset-itemson the Apify API with the same input JSON as body.
Input
| field | what it does |
|---|---|
queries | search terms, one per line |
locations | optional, a city or region per line. Each term is searched in each location |
startUrls | optional, XING job search URLs copied from the browser, with your filters |
sort | date (default, newest first) or relevance |
maxJobsPerSearch | cap per search, default 100, max 1,000 |
maxJobs | hard stop across the run, also your budget cap |
includeDescription | adds the description, dates, industry and address, charged per description |
Minimal input:
{ "queries": ["python"], "locations": ["Berlin"] }
Several roles in three cities, with descriptions:
{ "queries": ["data engineer", "softwareentwickler"], "locations": ["Berlin", "Wien", "Zuerich"], "includeDescription": true }
A pasted search URL with your own filters, newest first, capped at 300 jobs:
{ "startUrls": ["https://www.xing.com/jobs/search?keywords=sap%20consultant&location=Muenchen&employmentType=FULL_TIME"], "sort": "date", "maxJobs": 300 }
Pricing
Pay per result, two events:
- $0.50 per 1,000 jobs for every job row in the dataset.
- $0.50 per 1,000 descriptions on top, only with
includeDescriptionand only for rows where the description was actually retrieved.
A job with its description costs $0.001. No start fee, no charge for compute or proxies. Searches that fail cost nothing, and a description that could not be retrieved is not charged. Apify's free monthly credit covers thousands of jobs, so you can evaluate without paying.
Example: 5 search terms in 3 cities, 200 jobs each, is 3,000 jobs. Without descriptions that run costs $1.50, with descriptions $3.00. A daily schedule with sort set to date and a small maxJobsPerSearch returns far fewer rows, only the newest postings.
More from DataSignals Lab
This Actor is one of the pay-per-result data Actors of DataSignals Lab: job listings per ATS platform and job board, app and company reviews, YouTube comments and transcripts, website contacts and tech stacks. Every Actor returns the same clean JSON style and charges only for rows that land in the dataset, so you can combine feeds without remapping fields. All Actors and prices are listed on datasignalslab.com.
Use cases
- Recruiters and staffing agencies: a daily list of new openings for a role in Berlin, Vienna or Zurich, with employment type and the salary range when shown.
- Sales teams: fresh job posts as a buying signal. A company hiring five SAP consultants has a project.
- Labour market researchers: a count per role, region and employment type per day, across the three countries.
- Job boards and aggregators covering the German-speaking market: new listings with the full description, de-duplicated on
job_id. - AI agents: answer "who is hiring data engineers in Munich this week" from live data.
Other boards: LinkedIn Jobs Scraper, Stepstone Jobs Scraper, Indeed Jobs Scraper. Company career sites: Job Search API.
XING jobs API alternative: how it compares
- XING has no public jobs API. This Actor reads the public search and job pages with plain HTTP requests, no browser and no login, which keeps the price at $0.50 per 1,000.
- You pay per row, not per compute unit, and
maxJobscaps the spend. A scheduled run cannot cost more than the cap you set. - The description is a choice with its own price. Pay for the list, add the text only for the rows where you want it.
- Pasted search URLs keep the filters you set on XING, such as employment type, career level, discipline, industry, remote option and salary, so you do not have to rebuild them in the input.
Limits
- XING shows 20 jobs per result page and the Actor stops at 1,000 jobs per search. For more, split the search by location, discipline or employment type.
- The result card has no posting date. The date, the closing date, the industry and the address come with
includeDescription. - XING cuts the description it publishes for search engines at 5,000 characters. Longer postings are returned up to that point.
- The salary on a card is often an estimate by XING, not a figure from the employer.
locationis the first location on the card. Postings with several locations show only the first.- Company profiles, people and posts are out of scope. This Actor returns jobs only.
FAQ
Is it legal to scrape XING jobs?
The Actor reads the job pages XING publishes to visitors who are not signed in, the same pages search engines index. It does not log in and does not collect profiles. Whether you may use the data depends on your jurisdiction and your use.
Do I need a XING account, API key or proxy?
No. There is no login and no cookie to paste. Apify's proxies are built in and included in the price.
How often does the XING Jobs Scraper update?
Every run reads XING live. Set sort to date to get the newest postings first, and keep maxJobsPerSearch small on a schedule so you pay only for the new ones.
Can I schedule it?
Yes. Create a schedule in the Apify Console, for example every morning at 07:00, with sort set to date. De-duplicate on job_id, because a reposted job keeps its id.
Can an AI agent or MCP client call the XING Jobs Scraper?
Yes. Through the Apify MCP server any MCP client, for example Claude Desktop or Cursor, can call this Actor as a tool and read the dataset. The input is the same JSON.
How much do 10,000 XING jobs cost?
$5.00 for the rows, $10.00 with descriptions. No start fee, no charge for failed searches.
What happens when XING blocks a request?
The request is retried up to three times, first through two fresh datacenter proxy sessions and then through a German residential proxy. If a search still fails it is skipped and the run continues. If every search in a run is refused, the run ends with a clear status message and nothing is charged.
Which countries does it cover?
Germany, Austria and Switzerland, the markets XING serves. Type the location as you would on XING, for example Berlin, Wien or Zuerich, or pass a search URL with the country filter set.
Integrations
Works with the Apify API and SDKs, schedules, webhooks and the Apify MCP server, so Claude, ChatGPT and other agents can call it as a tool. Push the dataset into Google Sheets, or connect it through Make, Zapier or n8n to your CRM or Slack. Export to JSON, CSV or Excel.
Support
Issues tab on this page, or support@datasignalslab.com. Response within one working day. Built and maintained by DataSignals Lab.
Changelog
- 2026-10: README restructured with guide, cost example, comparison, limits and FAQ. Prices unchanged.
- 2026-10-04: First release. Search by terms and locations or by pasted URL, optional description with detail fields.