LinkedIn Profile Finder by Name & Company — $3.20/1k
Pricing
from $3.20 / 1,000 name resolved (summary)s
LinkedIn Profile Finder by Name & Company — $3.20/1k
Find a person’s LinkedIn profile from their full name — anchored to a company site domain for precision, or from the bare name when it is unique. Ambiguous names come back as a free row with the namesake count instead of a wrong guess. $3.20 per 1,000 resolved, 20% under the shelf. Misses are free.
Pricing
from $3.20 / 1,000 name resolved (summary)s
Rating
0.0
(0)
Developer
Sputnik API
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
20 hours ago
Last modified
Categories
Share
LinkedIn Profile Finder by Name & Company
$3.20 per 1,000 resolved names, $8 with the full 164-field document — and a namesake is a free row, never a wrong guess. The shelf's by-name Actor charges a page fee plus a per-profile fee, so one resolved name costs about $6 per 1,000 before you see whether it is even the right person.
Resolve full names to LinkedIn profiles — honestly. A name alone is not an identity: this actor never guesses between namesakes.
Two modes, picked automatically:
- With a company domain (
companyDomain): each name is anchored to one employer, which makes even common names resolvable. "Satya Nadella" +microsoft.comfinds exactly the person you meant. - Bare names: a name resolves only when exactly one profile in the
database carries it. Namesakes come back as a free
ambiguousrow that tells you how many people share the name (_nameMatchCount) — so you know to add a company domain and retry.
This is a database lookup, not a live scrape, over one billion professional profiles, with a freshness stamp on every row.
Input
{"names": ["Satya Nadella", "Jane Doe"],"companyDomain": "microsoft.com","fullOutput": false}
What you get — 60+ fields per resolved name, 164 with fullOutput
| Group | Summary card (default, $0.0032/resolved) | Full document (fullOutput: true, $0.008/resolved) |
|---|---|---|
| Identity | full name, first/last, headline, photo, profile slug | same + background image |
| Current role | job title, employer name + slug (flat columns), position dates, industry | + role descriptions, employment type, job function |
| Career history | current positions | every past position with dates and descriptions |
| Education & certifications | schools, degrees, fields of study, dates; cert names, authorities | + descriptions, grades, license numbers |
| Skills, languages, bio | full skills list, languages, "about" text | same |
| Location & seniority | city/state/country, experience years, tenure, decision-maker flag | same |
| Salary estimate | inferred min–max | same |
| Social links | professional profile URL, GitHub, Twitter/X, Facebook, website | same |
| Contacts | — | email addresses and phone numbers when on record |
| Deep sections | — | publications, patents, awards, projects, articles, related profiles |
| Honesty meta | _status, _freshness, updatedAt; _nameMatchCount in bare-name mode | same + per-section coverage map |
Output
One row per name, _status explaining each (found / ambiguous /
not_found / invalid). Resolved rows carry the profile card,
_freshness, _fullData — a link to the complete document via the direct
API — and flat companyName / companySlug columns when a current
position is on record. In bare-name mode resolved rows also carry
_nameMatchCount, and free ambiguous rows carry it too — the honest
namesake count. A real resolved row:
{"_status": "found","_input": { "name": "Satya Nadella", "domain": "microsoft.com" },"_freshness": "fresh_90d","companyName": "Microsoft","companySlug": "microsoft","_view": "lite-v3","fullName": "Satya Nadella","headline": "Chairman and CEO at Microsoft","jobTitle": "Chairman and CEO","about": "As chairman and CEO of Microsoft, I define my mission and that of my company as empowering every person and every organization on the planet to achieve more.","location": { "city": "Redmond", "state": "WA", "country": "US" },"seniority": { "totalExperienceYears": 12, "currentTenureYears": 12 },"experience": { "work": [ { "title": "Chairman and CEO", "company": "Microsoft", "startDate": "2014-02-01", "endDate": null } ] },"education": [ { "school": "University of Wisconsin-Milwaukee", "degreeName": "Master’s Degree", "fieldOfStudy": "Computer Science" } ]}
(trimmed for display — the card also carries skills, languages,
certifications, inferredSalary, social links and connection counts
whenever the profile has them)
fullOutput: true upgrades every resolved name to the complete document —
164 fields across 37 sections, including full career history with
descriptions and the contact block.
The Output tab shows three views: Overview, Career & education, and Contacts & signals.
Pricing — you only pay for resolved names
| Event | Price | When |
|---|---|---|
| Name resolved (summary) | $0.0032 | exactly one profile matched, 60+ field row |
| Name resolved (full document) | $0.008 | fullOutput: true, 164 fields / 37 sections |
| Ambiguous / unknown / invalid | $0 | always free, with the namesake count |
FAQ
Why did my name come back ambiguous? More than one real person
carries it. The row tells you how many (_nameMatchCount) — add
companyDomain to anchor the name to an employer and rerun.
What exactly does fullOutput add? The complete career history with
role descriptions, education and certification detail, publications,
awards, related profiles — and the contact block. The summary card never
carries contact data.
The family
Same engine, other doors: Reverse Email Lookup (email → person), Profile Lookup (URL → profile), Work Email Finder (name + domain → email), Company Employees Finder (domain → roster), People/Company Database Search, Social Handle Lookup (dev/social handle → person), Bulk People Enrichment (CSV, 50k rows). One data core, one billing promise: misses are free.
Disclaimer
This Actor is an independent product and is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. It does not access, crawl, or scrape LinkedIn at run time — answers come from our own database of publicly available professional data; "LinkedIn" is used only to describe the kind of public profile data the database covers. Removal requests are honored via the Issues tab.