/xing/companies

POST /api/xing/companies

Price: 10 credits

Get XING company (employer page) profile by alias or page URL

How to use it

Get the full XING (xing.com) employer page profile of a DACH company by alias (the /pages/{alias} URL segment, e.g. 'sap') or page URL. Returns the company name, slogan, logo and cover image, industry, employee-count band and total, page follower count, founding year, website, imprint, the 'about us' summary and full text, office locations with address, geo coordinates and contact details (email, phone, fax, website), and related companies. Resolve the alias first via /xing/companies/search if you only have the company name.

Parameters

• access-token string required

Request body

• timeout 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)
• lang string — Content language (default: "de"; one of: "de", "en")

Response

• @type string (default: "XingCompany")
• id string nullable
• entity_page_id string nullable
• global_id string nullable
• alias string required
• name string required
• url string required
• slogan string nullable
• image string nullable
• cover string nullable
• industry string nullable
• focus_type string nullable
• contract_type string nullable
• employee_count_min integer nullable
• employee_count_max integer nullable
• employee_total integer nullable
• follower_count integer nullable
• founding_year integer nullable
• website string nullable
• imprint string nullable
• about_summary string nullable
• about_text string nullable
• location_count integer nullable
• main_location object nullable
  • @type string (default: "XingCompanyLocation")
  • id string nullable
  • label string nullable
  • city string nullable
  • address string nullable
  • address_suffix string nullable
  • postcode string nullable
  • country_code string nullable
  • country string nullable
  • lat number nullable
  • lng number nullable
  • email string nullable
  • phone string nullable
  • fax string nullable
  • website string nullable
  • is_highlighted boolean nullable
• locations array (default: [])
  • @type string (default: "XingCompanyLocation")
  • id string nullable
  • label string nullable
  • city string nullable
  • address string nullable
  • address_suffix string nullable
  • postcode string nullable
  • country_code string nullable
  • country string nullable
  • lat number nullable
  • lng number nullable
  • email string nullable
  • phone string nullable
  • fax string nullable
  • website string nullable
  • is_highlighted boolean nullable
• related_companies array (default: [])
  • @type string (default: "XingCompanyCard")
  • id string nullable
  • alias string nullable
  • name string required
  • url string nullable
  • image string nullable
  • industry string nullable
  • city string nullable
  • job_count integer nullable
  • contract_type string 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 — 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.

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.