/xing/users

POST /api/xing/users

Price: 10 credits

Get XING member profile by page name or profile URL

How to use it

Get the public XING (xing.com) member profile by page name (the /profile/{pageName} URL segment, e.g. 'Ricardo_Azenha') or profile URL. Returns the name, gender, academic title, photo, membership flag, profile quality index, city and country, spoken languages, the self-declared skill list, the full career history (job title, company name, company page alias and logo, dates and duration) and the education history (school, degree, subject, notes and dates).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — XING profile page name (the /profile/{pageName} URL segment) or a full profile URL (examples: "Ricardo_Azenha", "https://www.xing.com/profile/Ricardo_Azenha"; minLength: 1)
• lang string — Content language (default: "de"; one of: "de", "en")

Response

• @type string (default: "XingUser")
• id string nullable
• alias string required
• first_name string nullable
• last_name string nullable
• display_name string nullable
• academic_title string nullable
• gender string nullable
• url string required
• image string nullable
• display_flag string nullable
• quality_index number nullable
• headline string nullable
• job_title string nullable
• occupation_summary string nullable
• current_company string nullable
• city string nullable
• country string nullable
• country_code string nullable
• display_location string nullable
• work_experience array (default: [])
  • @type string (default: "XingWorkExperience")
  • job_title string nullable
  • company_name string nullable
  • company_alias string nullable
  • company_url string nullable
  • company_image string nullable
  • company_notes string nullable
  • is_current boolean nullable
  • begin_date string nullable
  • end_date string nullable
  • duration string nullable
• education array (default: [])
  • @type string (default: "XingEducation")
  • subject string nullable
  • degree string nullable
  • school_name string nullable
  • school_notes string nullable
  • begin_date string nullable
  • end_date string nullable
  • duration string nullable
  • is_primary boolean nullable
• skills array (default: [])
• languages array (default: [])
  • @type string (default: "XingLanguageSkill")
  • language string nullable
  • display_language 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 — Profile 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.