/xing/jobs

POST /api/xing/jobs

Price: 10 credits

Get XING job posting details by slug or URL

How to use it

Get full details of a XING (xing.com) DACH job posting by its slug or full URL. A bare numeric id is not resolvable (XING has no numeric-only job URL). Returns the job title, HTML and plain-text descriptions, employment type, career level, discipline, industry, the salary estimate (min / max / median with currency), the work location (city, region, postal code, country and city id), remote-work options, the hiring company name, publication / refresh / expiry timestamps, the company website and external application URL, and paid / top-job flags.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — XING job slug (the URL segment ending in the numeric id) or a full job URL (examples: "berlin-principal-software-engineer-156804885", "https://www.xing.com/jobs/berlin-principal-software-engineer-156804885"; minLength: 1)
• lang string — Content language (default: "de"; one of: "de", "en")

Response

• @type string (default: "XingJob")
• id string required
• global_id string nullable
• slug string nullable
• url string nullable
• company_name string nullable
• company_id string nullable
• employment_type string nullable
• career_level string nullable
• discipline string nullable
• industry string nullable
• language string nullable
• keywords array (default: [])
• remote_options array (default: [])
• salary object nullable
  • @type string (default: "XingJobSalary")
  • currency string nullable
  • minimum number nullable
  • maximum number nullable
  • median number nullable
• location object nullable
  • @type string (default: "XingJobLocation")
  • city string nullable
  • city_id integer nullable
  • region string nullable
  • street string nullable
  • zip_code string nullable
  • country_code string nullable
  • country string nullable
• description string nullable
• description_text string nullable
• website string nullable
• apply_url string nullable
• is_paid boolean nullable
• is_top_job boolean nullable
• is_prioritized boolean nullable
• redirects_to_third_party boolean nullable
• activated_at integer nullable
• refreshed_at integer nullable
• expires_at integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Job posting not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.