# Xing Jobs Scraper (`fetch_cat/xing-jobs-scraper`) Actor Scrape public XING job listings by keyword, location, or direct URL. Export job titles, companies, locations, salaries, descriptions, and URLs. - **URL**: https://apify.com/fetch_cat/xing-jobs-scraper.md - **Developed by:** [Fetch Cat](https://apify.com/fetch_cat) (community) - **Categories:** Jobs, Lead generation, Automation - **Features:** Limited permissions - **Stats:** 3 total users, 1 monthly users, 97.2% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.31 / 1,000 job saveds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README Export public XING job listings from keyword and location searches or known search and job URLs. Retain job identity, company and location context, exposed salary and employment labels, optional public descriptions and source provenance for separate recruiting or labor-market research. The Actor does not log in, apply to roles or access private XING data. ### Quick start Start with the existing Berlin software-engineer query, a small saved-job cap and a low page cap: ```json { "keywords": ["software engineer"], "location": "Berlin", "maxItems": 10, "maxPages": 2, "includeDetails": true } ``` Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same. https://youtu.be/1OW8gOqlZbY?t=25 ### What you get One saved public job row with its ID and source URL, title, exposed company and location fields, optional detail content and collection time. Salary is source text rather than a normalized or verified pay offer. Remote or hybrid hints and optional links can be absent when the source does not expose them. ### Who is it for? - **DACH recruiting researchers** reviewing role and city samples. - **Labor-market analysts** retaining source salary and employment text with its context. - **Hiring-intelligence teams** observing public company postings over time. - **Job-data developers** building source-linked records for separate review and reporting tools. ### How you can use the data - **Inspect Berlin engineering roles.** Use the existing small keyword/location recipe and keep title, jobId, location and sourceSearchUrl. The observed sample is not an exhaustive count of open roles or proof of applicant eligibility. - **Compare two Munich role queries.** Use the existing marketing manager and sales manager recipe with a smaller shared job cap. Preserve source links and search context rather than assuming equally sized or representative role samples. - **Review a known Hamburg search or direct posting.** Use the existing search URL or your known public job link, retaining sourceType and jobUrl. A direct accessible posting is different from broad keyword discovery, and missing public fields stay unknown. - **Keep your own source-salary observations.** Retain salaryText, employmentType, postedAt or postedText and collection time before grouping results. Do not infer annual pay, currency conversion or a guaranteed offer from text, and build repeated comparisons or alerts in your own destination. ### Input settings | Setting | JSON key | Use it for | Example | | --- | --- | --- | --- | | Keywords | `keywords` | Job titles, skills, or hiring terms to search. | `["software engineer"]` | | Location | `location` | City, region, or country for keyword searches. | `"Berlin"` | | Start URLs | `startUrls` | XING search URLs or direct XING job URLs. | `https://www.xing.com/jobs/search?keywords=...` | | Maximum jobs | `maxItems` | Cap saved rows and control spend. | `10` | | Maximum pages | `maxPages` | Limit paginated search pages per query. | `5` | | Fetch job detail pages | `includeDetails` | Enrich search results. Direct job URLs are always fetched. | `true` | | Proxy configuration | `proxyConfiguration` | Connection settings. See field help for default access and usage costs. | `{ "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "countryCode": "DE" }` | #### Existing Munich market-scan input ```json { "keywords": ["marketing manager", "sales manager"], "location": "Munich", "maxItems": 100, "maxPages": 10, "includeDetails": true } ``` #### Existing direct-search and job URL input ```json { "startUrls": [ { "url": "https://www.xing.com/jobs/search?keywords=data%20analyst&location=Hamburg" }, { "url": "https://www.xing.com/jobs/berlin-senior-software-engineer-155853218" } ], "maxItems": 50, "includeDetails": true } ``` ### Output data The existing illustrative row contains historical values rather than a current role or salary measurement: ```json { "jobId": "155853218", "jobUrl": "https://www.xing.com/jobs/berlin-senior-software-engineer-155853218", "title": "Senior Software Engineer", "companyName": "Nulegal GmbH", "companyUrl": null, "location": "Berlin, DE", "remoteOrHybrid": null, "postedAt": "2026-07-08", "postedText": null, "employmentType": "Full-time", "salaryText": "EUR 61,000 - 81,500", "descriptionText": "Bureaucracy and legal friction are holding Europe back...", "skills": ["Urgently hiring", "Full-time"], "applyUrl": "https://www.xing.com/jobs/berlin-senior-software-engineer-155853218", "sourceSearchUrl": "https://www.xing.com/jobs/search?keywords=software+engineer&location=Berlin", "sourceType": "search", "scrapedAt": "2026-07-09T18:45:00.000Z" } ``` | Field | Description | | --- | --- | | `jobId` | XING job identifier parsed from the job URL. | | `jobUrl` | Canonical public XING job URL. | | `title` | Job title. | | `companyName` | Hiring company name. | | `companyUrl` | Public company URL when XING exposes one. | | `location` | Job location text. | | `remoteOrHybrid` | Remote, hybrid, or on-site hint when visible. | | `postedAt` | Structured posting date when available. | | `postedText` | Human-readable posting freshness text when visible. | | `employmentType` | Employment type such as full-time or part-time. | | `salaryText` | Salary text when shown publicly. | | `descriptionText` | Plain-text public job description from the detail page. | | `skills` | Tags, labels, or skills visible on the listing/detail page. | | `applyUrl` | Application URL when exposed publicly. | | `sourceSearchUrl` | Search page where the listing was found. | | `sourceType` | `search` or `detail`. | | `scrapedAt` | Timestamp when the record was saved. | #### Download your results Open your run's dataset, choose **Export** and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet. See [Apify's download and export guide](https://docs.apify.com/storage/dataset#apify-console) for the available formats and field options. ### Pricing The `start` event is charged when extraction starts, even if no jobs are found. Each job saved to the dataset is charged as an `item` event. Runs stop collecting when the remaining result budget is exhausted. Keep both job and page caps modest when checking a query, and request search-result details only when useful. See the [live Pricing tab](https://apify.com/fetch_cat/xing-jobs-scraper/pricing) for current event rates and tier discounts. Platform and proxy usage can also apply. ### Tips for best results - **Begin with a focused city and role.** Berlin, Munich and Hamburg are existing examples rather than universal location matches. - **Use German and English terms deliberately.** Source text and job titles can differ across DACH postings. - **Keep detail collection optional.** Turn it off when listing-level context is sufficient. - **Preserve source salary strings.** Missing or ambiguous pay text should not become an inferred numeric salary. - **Retain dates and source URLs.** Repeated snapshots need your own comparison and deduplication logic. ### Limits and caveats - XING can change public markup or throttle very large/frequent runs. - Some jobs do not expose salary, remote status, apply URL, or company URL publicly. - Search results can change between pages while new jobs are posted or removed. - This Actor reads public job pages only. It does not log in, apply to jobs, or access private XING data. The saved cap and page cap limit the observed search sample. New, removed or changed postings can shift results between pages. Source remote hints, dates, application links and salary text are not verified eligibility or employment guarantees. The existing German residential proxy default concerns public-source access rather than changing the requested job location. It does not establish where a job is based or guarantee that a source can always be reached. No private account session or application action is provided. Unavailable pages and completed searches with no usable matching listings are recorded in the run summary without invented records. Excluding unrelated recommendations does not establish that XING has no matching jobs. Blocking, unrecognized pages and failed requested details fail the run while preserving any useful rows already collected. Check the run summary before treating a dataset as a complete extraction. A saved search-only row does not prove its requested details were retrieved. Abnormally large pages fail as incomplete extraction, not empty results: decompressed HTML is limited to 2 MiB per response, with 20,000 markup delimiters and 30,000 DOM construction operations per parse. Exact attempted-job deduplication uses at most 8 MiB of temporary hashed state. Exhausting it also fails explicitly. These are resource safeguards, not a limit on the number of requested seeds. Useful mixed-batch rows remain available. `RUN_SUMMARY` contains at most 50 samples each for warnings and input outcomes, with strings limited to 4,096 characters. Its diagnostic totals and omitted counts disclose additional outcomes. Omitted failures still fail the run. On a processing deadline, `PENDING_INPUT_CURSOR` identifies the unprocessed phase/index/page in the original `INPUT`, instead of duplicating the remaining URL list. ### Automation and integrations #### Save your settings for next time Once you have an input that works for you, [save it as an Apify task](https://docs.apify.com/actors/running/tasks). This keeps your settings together so you can use them again without filling in the form from scratch. #### Run on a schedule Need fresh results regularly? You can [schedule the Actor or a saved task](https://docs.apify.com/actors/running/schedules) to run at a time that suits you. Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow. #### Send results to your other tools Use **n8n, Make or Zapier** to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the [Apify integration guides](https://docs.apify.com/integrations) for your chosen tool. For a custom connection, an [Apify webhook](https://docs.apify.com/integrations/webhooks) can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure. ### API usage Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results. The existing Node.js and Python examples wait for completion and print the dataset ID. Read its saved rows using the Dataset API or client, with pagination for larger exports. The cURL example starts a run and returns its details. Wait for completion before reading its dataset. For setup instructions, see Apify's [JavaScript client guide](https://docs.apify.com/api/client/js), [Python client guide](https://docs.apify.com/api/client/python) and [Actor runs API reference](https://docs.apify.com/api/v2/acts-runs-post). #### cURL ```bash curl -X POST "https://api.apify.com/v2/acts/fetch_cat~xing-jobs-scraper/runs?token=YOUR_APIFY_TOKEN" \ -H "Content-Type: application/json" \ -d '{"keywords":["software engineer"],"location":"Berlin","maxItems":10,"includeDetails":true}' ``` #### Node.js ```js import { ApifyClient } from "apify-client"; const client = new ApifyClient({ token: process.env.APIFY_TOKEN }); const run = await client.actor("fetch_cat/xing-jobs-scraper").call({ keywords: ["software engineer"], location: "Berlin", maxItems: 10, includeDetails: true }); console.log(run.defaultDatasetId); ``` #### Python ```python from apify_client import ApifyClient client = ApifyClient("YOUR_APIFY_TOKEN") run = client.actor("fetch_cat/xing-jobs-scraper").call(run_input={ "keywords": ["software engineer"], "location": "Berlin", "maxItems": 10, "includeDetails": True, }) print(run["defaultDatasetId"]) ``` ### MCP and AI agents You can ask your AI assistant to collect data with **Xing Jobs Scraper** and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes. Connect your assistant through the [Apify MCP server](https://mcp.apify.com/). MCP gives your assistant a way to find this scraper, run it and read the results. Follow the [official setup and sign-in guide](https://docs.apify.com/mcp) for your app. #### Easier setup with an Apify plugin If you use a supported coding assistant, the [official Apify plugin](https://docs.apify.com/agents/plugins) can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app. #### Use Apify AI in Console Prefer to keep everything in Apify? Open [Apify AI in Console](https://docs.apify.com/account/apify-ai) and ask it to find Fetch Cat's **Xing Jobs Scraper**. You can describe the data you want and ask questions about the results. Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply. #### Choose your assistant - **Claude and Claude Code (Anthropic):** [Apify setup guide](https://docs.apify.com/integrations/claude). - **ChatGPT and Codex (OpenAI):** [Apify setup guides](https://docs.apify.com/integrations/openai). - **Grok Bot (xAI):** [Apify plugin guide](https://docs.apify.com/integrations/grok-bot). - **Gemini CLI (Google):** [MCP server setup guide](https://geminicli.com/docs/tools/mcp-server/). Use the server URL below with the HTTP configuration supported by Gemini CLI. #### Connect just this scraper To keep your setup focused on this scraper, add this server configuration to a compatible MCP client: ```json { "mcpServers": { "apify": { "url": "https://mcp.apify.com?tools=fetch_cat/xing-jobs-scraper" } } } ``` Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format. #### Use Apify's general server Already connected to the general Apify MCP server at `https://mcp.apify.com`? You can use it to find this scraper without adding another server. Ask your assistant to use **Xing Jobs Scraper** by Fetch Cat, or give it the identifier `fetch_cat/xing-jobs-scraper`. Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service. #### Example requests - “Use Fetch Cat’s Xing Jobs Scraper to collect up to 5 software engineer jobs in Berlin with a two-page cap and details enabled. Keep source links and salary text without inferring a guaranteed annual offer.” - “Collect up to 5 public jobs across marketing manager and sales manager queries in Munich with a two-page cap and details off. Keep source provenance without assuming equal samples or private applicant access.” - “Retrieve up to 5 jobs from https://www.xing.com/jobs/search?keywords=data%20analyst\&location=Hamburg with details enabled and a two-page cap. Preserve missing optional fields and public source context without applying to jobs.” Normal Apify charges apply. Check the [live Pricing tab](https://apify.com/fetch_cat/xing-jobs-scraper/pricing) before asking your assistant to run a larger batch. ### Pay with x402 If your AI agent has a funded wallet, it can pay for Apify usage through [x402](https://docs.apify.com/integrations/x402). This experimental option lets an agent use Apify without a conventional account. [Apify AGI](https://agi.apify.com/) provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection. Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability. Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration. #### Other ways for agents to pay Apify also supports **MPP** for prepaid access through AGI and **Skyfire** for eligible Actors. If your agent already uses one of these, see the [agentic payment guide](https://docs.apify.com/agents/payments) to choose the right setup. ### FAQ #### Can I export results? Yes. Apify datasets support JSON, CSV, Excel, XML, RSS, and API access. #### Why are some fields empty? XING does not expose every field on every public listing. The Actor leaves unavailable fields empty instead of guessing. #### Can I scrape direct job URLs? Yes. Add direct `https://www.xing.com/jobs/...` URLs to `startUrls`. Each direct job URL produces one dataset row when accessible publicly. #### Does this need a proxy? The default uses Apify Residential proxy in Germany. You can provide your own connection settings. See the input field help for choices and costs. No connection guarantees access. ### Related Actors - [ATS Jobs Scraper](https://apify.com/fetch_cat/ats-jobs-scraper) — Collect public job-board openings and available job details from supported applicant-tracking systems. - [Lever Jobs Scraper](https://apify.com/fetch_cat/lever-jobs-scraper) — Collect public Lever job-board openings and available job details. - [Remote.com Jobs Scraper](https://apify.com/fetch_cat/remote-dot-com-jobs-scraper) — Collect public Remote.com job listings with available company, hiring-location and application details. - [Greenhouse Jobs Scraper](https://apify.com/fetch_cat/greenhouse-jobs-scraper) — Collect public Greenhouse job-board openings and available job details. - [Workable Jobs Scraper](https://apify.com/fetch_cat/workable-jobs-scraper) — Collect public Workable job-board openings and available job details. ### Support and feedback For custom additions or integrations, email . Found an error or have a feature request? [Open an issue](https://apify.com/fetch_cat/xing-jobs-scraper/issues) with the run URL, a non-sensitive input example and what you expected. Need help sharing it? See [Apify’s guide to sharing a run when reporting an issue](https://docs.apify.com/account/collaboration/general-resource-access#automatically-sharing-runs-via-actor-issues). Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead. Tried this scraper? We'd love to hear how it worked for you. [Leave a review](https://apify.com/fetch_cat/xing-jobs-scraper/reviews) to help others choose the right tool and help us improve it. Your feedback means a lot to us. Made with care for curious people, AI agents and the possibilities in data. ♥ # Changelog This Actor's version history is a separate document: https://apify.com/fetch_cat/xing-jobs-scraper/changelog.md # Actor input Schema ## `keywords` (type: `array`): Job titles, skills, or hiring keywords to search on XING. Leave empty when using only Start URLs. ## `location` (type: `string`): City, region, or country for keyword searches, such as Berlin, Munich, Hamburg, or Germany. ## `startUrls` (type: `array`): Optional XING job search URLs or direct XING job detail URLs to scrape. ## `maxItems` (type: `integer`): Maximum number of job listings to save across all searches and start URLs. ## `maxPages` (type: `integer`): Safety limit for paginated search result pages. XING usually returns around 10-20 jobs per page. ## `includeDetails` (type: `boolean`): Enrich search results with public descriptions, dates, salary and available links. Direct job URLs always require a page fetch, even when this setting is off. ## `proxyConfiguration` (type: `object`): Connections start with Apify Residential proxy in Germany by default, which can incur proxy usage costs. Explicit saved/API settings are used unchanged: managed groups and country, custom proxy URLs, or useApifyProxy:false for direct access. Direct access has no paid fallback. Access is not guaranteed. Choose either managed or custom proxies, not both. ## Actor input object example ```json { "keywords": [ "software engineer" ], "location": "Berlin", "startUrls": [ { "url": "https://www.xing.com/jobs/search?keywords=software%20engineer&location=Berlin" } ], "maxItems": 10, "maxPages": 5, "includeDetails": true, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ], "countryCode": "DE" } } ``` # Actor output Schema ## `overview` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "keywords": [ "software engineer" ], "location": "Berlin", "startUrls": [ { "url": "https://www.xing.com/jobs/search?keywords=software%20engineer&location=Berlin" } ] }; // Run the Actor and wait for it to finish const run = await client.actor("fetch_cat/xing-jobs-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "keywords": ["software engineer"], "location": "Berlin", "startUrls": [{ "url": "https://www.xing.com/jobs/search?keywords=software%20engineer&location=Berlin" }], } # Run the Actor and wait for it to finish run = client.actor("fetch_cat/xing-jobs-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "keywords": [ "software engineer" ], "location": "Berlin", "startUrls": [ { "url": "https://www.xing.com/jobs/search?keywords=software%20engineer&location=Berlin" } ] }' | apify call fetch_cat/xing-jobs-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,fetch_cat/xing-jobs-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/zMJbU5y6jhHUN8TaK/builds/VjaFhqK0jSpB4FrP9/openapi.json