PeopleSearchLinkedinResponse
LinkedIn by link is a SOURCE OF THE NAME (and the place) the round is then searched by: the
client writes fullname into the name and the place into fields (where the user gave
none), then runs the round. With status: index the profile is also the search's origin:
every round of the report pins the accounts the identity graph ties to it on top of the
panels. Where LinkedIn is also searched (User.peopleSearchLinkedinPanel), the
round has a LinkedIn panel of its own, ranked from the name like the others; the origin is
not a pick of it, and neither is ever a report subject. No photo is
sent to face search on this route.
Where the name came from. index — our LinkedIn database holds the profile: the name and
the profile's own place are its ("name from our database"), and the profile becomes the
search's origin (origin, PeopleSearchState.linkedin_origin). slug — the name is what
the link's slug spells (john-doe-1a2b3c → "john doe"): our database does not hold the
profile (nothing is read from LinkedIn then), or LinkedIn did not answer. profile — the
profile was read directly: only when the lookup could not be made (switched off for
LinkedIn, or failing).
Possible values: [profile, slug, index]
The name to search by — clipped to the name's cap; empty when neither the profile nor the slug gives one (ask the user for it).
index only: the profile's own city, as our database holds it.
The profile's own state (with index as our database writes it, a code such as TX).
index only: the profile's own country.
origin object
index only: the profile, now the search's origin (PeopleSearchState.linkedin_origin).
The name as our database holds it (may be empty — the search then runs by fullname of the answer).
https://www.linkedin.com/in/<slug>.
{
"ok": true,
"status": "profile",
"slug": "string",
"fullname": "string",
"location": "string",
"state": "string",
"country": "string",
"origin": {
"slug": "string",
"fullname": "string",
"link": "string"
},
"took_ms": 0
}