> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/xing/jobs-jobid>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/xing/jobs-jobid.mdx>

---

# XING Job API

One XING job listing with its full description.

`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`.

## Request

- **Endpoint:** `GET /v1/xing/jobs/{jobId}`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by job slug or URL
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/xing/jobs/jobid/get)
- **Platform page:** [/platforms/xing](https://www.socialfetch.dev/platforms/xing)

## 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.
