LinkedIn Profile Lookup API: a profile URL in, the whole person out
Turn a public LinkedIn profile URL into name, headline, location, current role, full job history, education and skills in about a second. 10 credits, and only charged when we find a profile.
10
Credits per match
about $0.035 on Growth
0
Credits on a miss
private or gone, no charge
~1s
Typical lookup
instant repeats for 7 days
2
Independent sources
automatic fallback
What LinkedIn Profile Lookup gives you
The whole profile, not just a job title
Most enrichment gives you a current title and stops. This returns the dated career history, education and skills as well, so you can see the arc rather than a single row.
- Name, headline and location
- Current title and employer
- Full role history with tenure
- Education and skills
Dated roles with tenure calculated
Every role carries its date range, how long it lasted, location and employment type, and the current role is flagged. Tenure is computed for you, so 'in seat 3 months' or 'in seat 6 years' is a field, not a parsing exercise.
- Start and end dates
- Tenure like '3 yrs 6 mos'
- Current-role flag
- Employment type and location
About a second, not a minute
The primary source answers in around a second. When it cannot see a profile we fall back automatically to a slower deep fetch that reads the same fields, so a single source having a bad day does not become your failed lookup.
- ~1s typical response
- Automatic second source
- Repeats instant for 7 days
- No queue, no polling
Only charged on a match
Private profiles, deleted vanity URLs and upstream failures all cost you nothing. Vendors that bill on every attempt make list quality your problem; we do not.
- Zero credits on a no-match
- Applies to bulk jobs too
- Predictable cost on messy lists
- No minimum commitment
One canonical URL per person
Locale subdomains, trailing slashes, tracking parameters and bare usernames all collapse to the same canonical profile URL before anything is cached or billed. Paste it five ways, pay once.
- de.linkedin.com accepted
- Tracking params stripped
- Bare username accepted
- One cache key per person
Same credits, same API
One balance covers profile lookups, company profiles, contact append, phone, email and everything else. No separate contract, no separate key, no unused seat.
- Universal credits
- Credits roll over
- One API key
- Bulk CSV supported
Profile URL in, person out
Send a public profile URL
POST the profile link you already have on the record. Any spelling works: locale subdomains, trailing slashes, tracking parameters, or just the bare vanity username.
$ POST /v1/linkedin-profile-lookup
"profile_url": ".../in/williamhgates"
> bare username accepted too
> canonicalized before caching
We read the public profile
The fast source answers in about a second. If it cannot see the profile we fall back to a deep fetch automatically. Public, logged-out data only, and repeats within 7 days come straight from cache.
Profile URL canonicalized
Fast source queried (~1s)
Fallback source on miss
Public data only
Get the whole profile back
Identity, headline, location, reach, current role, dated job history, education and skills land in one JSON payload. A match bills 10 credits; a miss bills nothing.
nameAvery Chen
titleVP of Revenue Operations
10 yrs across 3 roles
One endpoint. A public LinkedIn profile URL in, structured data out.
Same authentication, same credit balance, and the same response envelope as every other 1Lookup product. If you have already integrated one endpoint, this one is a URL change.
curl -X POST https://app.1lookup.io/api/v1/linkedin-profile-lookup \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{ "profile_url": "https://www.linkedin.com/in/williamhgates" }'{
"classification": {
"matched": true,
"name": "Avery Chen",
"headline": "VP of Revenue Operations at Acme Analytics",
"current_title": "VP of Revenue Operations",
"current_company": "Acme Analytics",
"location": "San Francisco, California, United States",
"connections": 3100,
"followers": 8420
},
"insights": {
"linkedin_profile_lookup_result": {
"profile_url": "https://www.linkedin.com/in/avery-chen",
"years_of_experience": 10,
"experience": [
{
"title": "VP of Revenue Operations",
"company": "Acme Analytics",
"range": "Mar 2023 - Present",
"duration": "3 yrs 6 mos",
"is_current": true
}
],
"education": [
{ "school": "University of Washington", "degree": "BS, Economics" }
],
"skills": ["Revenue Operations", "Salesforce", "Forecasting"]
}
},
"metadata": { "credits_used": 10, "cache_hit": false }
}What a matched profile looks like
One call turns a profile link into a record you can score, route and personalize against: who they are and what they do on top, the dated career history underneath, next to the raw JSON your code receives.
- NameAvery Chen
- HeadlineVP of Revenue Operations at Acme Analytics
- Current titleVP of Revenue Operations
- Current companyAcme Analytics
- LocationSan Francisco, California, United States
- Followers8,420
- Connections3,100
- Years experience10
- Roles listed3
- EducationUniversity of Washington
- Skills returned5
{
"classification": {
"matched": true,
"name": "Avery Chen",
"current_title": "VP of Revenue Operations",
"current_company": "Acme Analytics",
"location": "San Francisco, California, United States",
"followers": 8420
},
"insights": {
"linkedin_profile_lookup_result": {
"years_of_experience": 10,
"experience": [
{
"title": "VP of Revenue Operations",
"company": "Acme Analytics",
"range": "Mar 2023 - Present",
"duration": "3 yrs 6 mos",
"is_current": true
}
],
"skills": ["Revenue Operations", "Salesforce"]
}
},
"metadata": { "credits_used": 10 }
}Every field you get back
No hidden tiers. Every field below is returned on a successful lookup at the price shown above.
Identity
- name
- first_name
- last_name
- headline
- location
- profile_url
- vanity_id
Profile
- about
- picture_url
- banner_url
Reach
- followers
- connections
Employment
- current_title
- current_company
- years_of_experience
- experience[].title
- experience[].company
- experience[].range
- experience[].duration
- experience[].is_current
Background
- education[].school
- education[].degree
- education[].range
- skills[]
Who uses LinkedIn Profile Lookup
Sales teams personalizing outbound
A generic opener gets deleted. Pull the prospect's dated history and you can reference the move they made eight months ago or the six years they spent at a competitor, which is the difference between a reply and a delete.
Recruiters screening a shortlist
Paste a list of profile URLs, get back tenure at every employer, education and skills in one bulk job. Filter for the candidates who have actually held the seat before instead of opening fifty tabs.
RevOps enriching CRM contact records
Contacts age badly. Refresh the current title and employer on the records that matter, and the routing rules and territory logic stop firing on job titles from two roles ago.
Trust and safety vetting signups
A high-value trial signs up claiming a senior title. One lookup shows whether the public profile supports the claim, how long the account has existed and how much reach it has, before you extend credit or access.
Frequently asked questions
What does LinkedIn Profile Lookup do?
You send a public LinkedIn profile URL and it returns that person's profile: name, headline, location, about text, profile photo, follower and connection counts, their current title and employer, their full role history with dates and tenure, education, and skills. Public, logged-out data only.
How much does it cost?
10 credits per matched profile. That is about $0.035 per person on the Growth plan and about $0.05 on Starter. A profile we cannot read costs nothing.
Am I charged when no profile is found?
No. LinkedIn Profile Lookup is success-billed. A private profile, a deleted vanity URL, or an upstream failure all return no match and deduct zero credits. That applies to the API, the dashboard and bulk CSV jobs alike.
How fast is a lookup?
About a second for a typical profile. If our primary source cannot see the profile we automatically fall back to a slower deep fetch, which takes longer but reads the same fields. Results are cached for 7 days, so repeat lookups on the same person return instantly.
What can I send as input?
A public profile URL such as https://www.linkedin.com/in/williamhgates. Locale subdomains, trailing slashes and tracking parameters are all accepted and stripped. You can also send the bare vanity username. Every spelling collapses to one canonical URL before caching, so you are never billed twice for the same person because a teammate pasted a different link.
Does every profile come back with skills?
No, and we will not pad it. Skills are only returned when the person actually publishes a skills section. In live testing one profile returned 47 skills while two others returned none, because those two do not list any. The about text and banner image are profile-dependent in the same way. You get whatever the person made public, and you are charged the same 10 credits either way.
Is the connection count a measure of reach?
No, and it is worth being precise about. Connections are mutual connections, which LinkedIn caps and which large accounts often show as a small number. Bill Gates returns 8 connections against 40.5 million followers. If you are scoring audience size, use the follower count.
Where does the data come from, and is this allowed?
Public, logged-out profile data only. There is no authenticated scraping and no private profile access. We hold results in a 7-day cache rather than a long-lived profile database, and we honour erasure and opt-out requests. You are responsible for using the data lawfully in your jurisdiction, including under GDPR and CCPA where they apply to you.