Kitchen sink person lookup
Search for a person using a variety of parameters such as LinkedIn slug, LinkedIn URL, or their current company information. Returns profile data for the person if found.
Dynamic pricing
(body.numProfiles ? body.numProfiles * 0.04 : 0.04) + (body.liveFetch ? 0.08 : 0)
Example code
// Using @orth/sdk - The simplest way to call APIs
// Install: npm install @orth/sdk
import Orthogonal from "@orth/sdk";
const orthogonal = new Orthogonal({
apiKey: process.env.ORTHOGONAL_API_KEY,
});
const output = await orthogonal.run({
api: "fiber",
path: "/v1/kitchen-sink/person"
});
console.log(output);Body parameters
Object identifying the profile — NOT a bare string. Shape: { "identifier": <id type>, "value": <the id> }, e.g. {"identifier":"linkedinUrl","value":"https://www.linkedin.com/in/jdoe"}. If provided and correct, no other fields are needed. If you are unsure of the identifier type, omit this and instead pass emailAddress, or personName together with companyName / companyDomain.
The email address of the person to search for
The company the profile is currently working at. If provided the accuracy of the lookup increases. You do not need to pass in any other company parameters if you pass this.
The maximum number of profiles you want to fetch. Profiles are sorted by best match first.
Whether to fetch the freshest copy of the found profiles's LinkedIn data (costs extra). If omitted or set to false, we'll give the cached data present in our database. The boolean flag is deprecated and will be removed in future. Please use the object instead.
Whether to strictly match the company. If true, we will strictly lookup prospects which belong to given company details.
Whether to use fuzzy search on names, job titles and other parameters. This is good if you are not sure about the exact name or job title.
Whether to include deep details about each educational item, like the school's LinkedIn URL, website, location, etc. That'll be put in the detailedEducation array. This slows down the API call, so only enable this if you need it.
Whether to include deep details about each work experience item, like the company's LinkedIn URL, website, location, etc. That'll be put in the detailedWorkExperience array. This slows down the API call, so only enable this if you need it.
Response