Skip to content

Xing Scraper API

Xing is a professional network with a strong German-speaking user base.

OUTPUT FORMATSHTMLJSONMarkdown

Teams often want its profile, job and endorsement data for recruiting research, market mapping or brand analysis. This page explains what a managed scraping API does for Xing, how requests are billed in credits, and which checks to run before you collect anything.

What a Xing scraping API handles for you

A managed API sits between your code and Xing. You send a target URL plus options; the service handles browser rendering, proxy rotation and page delivery, then returns rendered HTML or extracted data for your parser. The useful output types for Xing are:

  • Profile pages: names, titles, companies and positions.
  • Job listings: structured role data for market and competitor tracking.
  • Company insights: organisation-level context for research.
  • Profile bios: professional background text for collaboration or talent sourcing.
  • Endorsements: skill endorsements for brand and positioning analysis.

A common pattern is to read Xing's XHR/API endpoints rather than the full HTML page, because the JSON payload is easier to parse than a rendered profile. Both routes are supported by the same request model; the choice depends on which endpoint actually returns the fields you need.

How a request flows

  1. Create an account and get an API key.
  2. Send a request to the API with the Xing URL and any options you need (JavaScript rendering, premium proxies, extraction rules, screenshots).
  3. Receive rendered HTML or structured output.
  4. Parse the fields you need and store them in your own pipeline.

The service handles proxies and headless browsers, so your code does not need to manage a browser fleet. Advanced options cover dynamic pages, screenshots and CSS/XPath extraction rules.

Credit costs and plan limits

Requests are billed in API credits. The base cost is 1 credit per request. Enabling JavaScript rendering costs 5 credits per successful request. Enabling premium proxies costs 10 credits without JS rendering, or 25 credits with it — the 25-credit premium rate already includes JS rendering, so it is not 5 plus 25. Credits are valid for one month and do not roll over. Concurrent requests are the number of requests you can send at the same time.

The plan table below shows the published monthly prices, credit allowances and concurrency for each tier. Prices are exclusive of VAT. The plan table is a reference snapshot; confirm current pricing and terms before you commit.

Decision checklist before you scrape Xing

  • Confirm your legal basis: Xing's terms of service, privacy law and intellectual property rules all apply. Get legal advice if you are unsure.
  • Decide whether you need rendered HTML or XHR/API JSON. JSON is usually easier to parse when the endpoint exposes the fields you need.
  • Estimate credits: multiply your monthly request volume by the per-request credit cost for the options you need (1 base, 5 with JS rendering only, 10 with premium proxies only, 25 with premium proxies plus JS rendering).
  • Check concurrency: pick a plan whose concurrent-request limit matches your batch size.
  • Plan for blocking: Xing actively blocks scraping, so premium proxies and headless rendering reduce the risk but do not guarantee access.
  • Keep personal data minimal: collect only what your use case requires and follow GDPR/CCPA obligations.

Worked example: estimating credits

Suppose you need 2,000 Xing profile requests per month and each request needs JavaScript rendering plus premium proxies. The combined premium-plus-JS rate is 25 credits per request (the 25-credit premium rate already includes JS rendering), so 2,000 × 25 = 50,000 credits. The Hobby plan includes 75,000 credits and 25 concurrent requests, so it covers this volume with headroom.

For comparison, the other cases are separate: JS rendering only costs 5 credits per request (2,000 × 5 = 10,000 credits), and premium proxies without JS rendering cost 10 credits per request (2,000 × 10 = 20,000 credits). Do not add the 5-credit JS rate on top of the 25-credit premium-plus-JS rate. Use this arithmetic against the plan table to pick a tier before you sign up.

Telling failures apart

Not every empty result means the same thing. Separate these cases before you change your code:

  • Blocked request: Xing returns a challenge or block page. Try premium proxies or headless rendering, and slow the request rate.
  • Empty selector: the page loaded but your CSS/XPath rule matched nothing. Inspect the rendered HTML and update the selector.
  • Missing field: the endpoint you chose does not expose that field. Switch to the XHR/API endpoint that does.
  • Legal stop: the data you want is out of scope under Xing's terms or privacy law. Stop and get advice rather than engineering around it.

Field map: what to collect and where

Data typeTypical sourceNotes
Name, title, company, positionProfile page or XHR/API JSONJSON is easier to parse when available
Job listingsJob search pages or XHR/API JSONStructured role data for market tracking
Company insightsCompany pagesOrganisation-level context
Profile biosProfile pageBackground text for talent sourcing
EndorsementsProfile pageSkill endorsements for brand analysis

Use CSS/XPath extraction rules when you want structured output directly from rendered HTML. Use XHR/API endpoints when the JSON payload already contains the fields you need.

Published Xing Scraper API plan snapshot
PlanPrice /moAPI CreditsConcurrent requestsJS renderingRotating & Premium ProxiesGeotargetingScreenshots & Extraction RulesPriority Email SupportDedicated Account ManagerTeam Management
Hobby$1975,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$991,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$2493,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$5998,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$99914,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,59924,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,39941,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,59969,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

Prices are exclusive of VAT. Credits are valid for one month and do not roll over. Requests start at 1 credit each; JS rendering costs 5 credits per successful request; premium proxies cost 10 or 25 credits depending on whether JS rendering is enabled.

Frequently asked questions

What is Xing?

Xing is a professional networking platform similar to LinkedIn, primarily used in German-speaking countries. Users connect with peers, search for jobs and join industry groups. Scraping Xing can support job market research, competitor analysis and professional trend tracking.

What does a Xing scraper do?

It extracts data from Xing using web scraping techniques. It automates collection from web pages and interacts with the web API, returning structured data such as profiles, jobs and posts without manual work.

Is scraping Xing legal?

Legality depends on compliance with Xing's terms of service and applicable laws, including privacy and intellectual property rules. Get legal advice for your specific use case before you collect data.

What information can I get from Xing?

You can collect profile information such as first and last names, titles, companies and positions by reading XHR/API endpoints or rendered pages. Follow legal and ethical guidelines for any platform you scrape.

Does Xing block scraping?

Yes, Xing actively blocks scraping. Premium proxies and headless rendering can reduce the risk by providing anonymity and mimicking real browser behaviour, but they do not guarantee access.