/linkedin/user/endorsers

POST /api/linkedin/user/endorsers

Price: 5 credits

Linkedin Get User Endorsers

How to use it

Returns the people who endorsed this person's skills, deduplicated, so someone who backed several skills appears once. `count` bounds endorsers, not skills, and a small `count` still finds them on a profile whose endorsed skills sit far down the list. The scan is bounded, so a very large `count` is served short rather than rejected, and a list shorter than `count` means either the profile had no more endorsers or the scan reached that bound — the length is not an endorsement total. An empty list means no endorsement was found. Which skill each endorsement was for is not returned; /linkedin/user/skills carries the skill list.

Call these first: /linkedin/user

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• urn object required — User fsd_profile URN from /linkedin/user response. Format: fsd_profile:ACoAAA... Only URN accepted, alias or URL will fail. (examples: "urn:li:fsd_profile:ACoAACmguogBIdbijM6YpcIganWLJ67yKyV5kd4")
  • type string required (one of: "fsd_profile")
  • value string required
• count integer required — Max result count (>: 0)

Response

• @type string (default: "LinkedinUserEndorser")
• urn object required
  • type string required (one of: "fsd_company", "fsd_group", "fsd_profile", "fsd_skill", "activity", "comment", "company", "group", "geo", "pulse", "member", "person", "industry", "ugcPost", "job", "message", "conversation", "media", "share", "linkedInArticle")
  • value string required
• name string required
• photo string nullable
• alias string required
• url string required
• headline 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 — The entity was not found, or a precondition failed 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.