POST /api/xing/companies/jobs
Price: 5 credits
List open job postings of a XING company by alias or page URL
List the open job postings of a XING (xing.com) company by alias (the /pages/{alias} URL segment, e.g. 'sap') or page URL. Each result carries the job id, slug, title, work city, salary estimate and employment type. Use /xing/jobs to fetch the full posting for a result.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)company string required — XING company page alias (the /pages/{alias} URL segment) or a full company page URL (examples: "sap", "https://www.xing.com/pages/sap"; minLength: 1)count integer required — Max number of jobs to return (min: 1)lang string — Content language (default: "de"; one of: "de", "en")@type string (default: "XingJob")id string requiredglobal_id string nullableslug string nullableurl string nullablecompany_name string nullablecompany_id string nullableemployment_type string nullablecareer_level string nullablediscipline string nullableindustry string nullablelanguage string nullablekeywords array (default: [])remote_options array (default: [])salary object nullable@type string (default: "XingJobSalary")currency string nullableminimum number nullablemaximum number nullablemedian number nullablelocation object nullable@type string (default: "XingJobLocation")city string nullablecity_id integer nullableregion string nullablestreet string nullablezip_code string nullablecountry_code string nullablecountry string nullabledescription string nullabledescription_text string nullablewebsite string nullableapply_url string nullableis_paid boolean nullableis_top_job boolean nullableis_prioritized boolean nullableredirects_to_third_party boolean nullableactivated_at integer nullablerefreshed_at integer nullableexpires_at integer nullable422 — 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 — Company 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.