Skip to main content

The id every call takes

Circle, edge and paths name a person by a LinkedIn profile URL, or the public identifier from one — the part after /in/. Both of these name the same person:
A LinkedIn member token (ACoAA…) is not a public identifier, and is answered 404 person_not_found.

Finding the id: resolve

When you hold an email, or a name and a company, /v1/resolve finds the profile. It takes one of three bodies:
  • A name is full_name, or first_name with last_name. A one-word name has no last name: send it in first_name and last_name.
  • A company is any of company, company_domain or company_linkedin_url. It also decides which current position the answer shows.
  • An email that finds no one falls back to a search by name — the name you sent, or one read from the address.
  • on_miss: RESEARCH searches a further profile source and does not reuse an earlier search that found no one. It takes longer, and counts towards the research limit.

Reading the answer

resolution.status is what to branch on: resolution.method says what answered: EMAIL, NAME_COMPANY, PUBLIC_ID or LINKEDIN_URL.

Two ids, one person

Every person in an answer carries a key and a publicId.
  • publicId is the person’s current LinkedIn identifier. It is a valid id in any call.
  • key is the identifier percent-decoded and lower-cased. Two people in answers are the same person when their keys are equal — use it to de-duplicate across calls.
A profile can have been held by more than one person over time. A circle, edge or paths call with such an id is answered 422 ambiguous_person, with the candidates in the error body: call again with the one you mean.