XING hub

XING Job API

One XING job listing with its full description.

GET /v1/xing/jobs/{jobId}

1 credit Failed requests are free

About this endpoint

GET /v1/xing/jobs/{jobId} takes the job's slug, for example berlin-senior-solution-engineer-159150774 (search returns it as slug), or the full job URL.

On found, data.job carries everything a search row has plus description (plain text), sections (title and text, when the employer used XING's template), careerLevel, discipline, industry, remoteOptions, keywords, language and jobCode. A wrong or ended slug returns HTTP 200 with lookupStatus: "not_found" and job: null.

Price

From $1.35 per 1,000 requests

1 credit per request. Failed requests are free.

Scale pack
$1.64 / 1,000
Growth pack
$2.36 / 1,000

The lowest rate is on annual plans; packs are pay as you go.

Example request

Send your API key in the x-api-key header. New accounts get 100 free credits, no card needed.

Request
cURL

Example response

A 200 response. Live responses have the same shape with current data.

Request
JSON

XING Job API FAQ

Why is the number alone not enough?

XING answers a job page only at its exact slug; any other path, even with the right number, is the same answer as an ended listing. Use the slug from search or the job URL.

What are sections?

When the employer used XING's template, the description is split into about the company, tasks, profile, what they offer and contact. Each section has a title and text. description always holds the whole text.

How does an ended listing look?

HTTP 200 with data.lookupStatus not_found and data.job null.

How many credits does a job lookup cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.