LinkedIn Profile Lookup
Headline, role history, education and skills from a public LinkedIn profile URL.
curl -X POST https://api.1lookup.dev/v1/linkedin-profile-lookup \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"linkedin_url":"https://www.linkedin.com/in/jordan-avery-example"}'{
"success": true,
"data": {
"linkedin_url": "https://www.linkedin.com/in/jordan-avery-example",
"full_name": "Jordan Avery",
"headline": "Director of Revenue Operations at Northwind Logistics",
"location": "Austin, Texas, United States",
"about": "Revenue operations lead focused on forecasting, territory design and CRM data quality.",
"current_role": {
"title": "Director of Revenue Operations",
"company": "Northwind Logistics",
"company_url": "https://www.linkedin.com/company/northwind-example",
"started": "2023-04"
},
"experience": [
{
"title": "Director of Revenue Operations",
"company": "Northwind Logistics",
"started": "2023-04",
"ended": null
},
{
"title": "Senior Sales Operations Manager",
"company": "Contoso Roasters",
"started": "2019-08",
"ended": "2023-03"
}
],
"education": [
{
"school": "Example State University",
"degree": "BBA, Finance",
"start_year": 2011,
"end_year": 2015
}
],
"skills": [
"Sales forecasting",
"CRM administration",
"Territory planning"
],
"follower_count": 2840
},
"meta": {
"credits_used": 10,
"credits_remaining": 999,
"cached": false,
"request_id": "req_8f3a2c1e9b7d"
}
}Authorization
Authorizationstring<bearer>requiredYour API key as a Bearer token. Live keys start with 1lk_live_. Test keys start with 1lk_test_ and return this endpoint's sample response without spending credits. See authentication.
Body
Send the fields as a JSON object with Content-Type: application/json.
linkedin_urlstring<uri>requiredLinkedIn profile URL. Example: https://www.linkedin.com/in/jordan-avery-example
freshbooleanSkip the 7-day cache and run a new lookup. Charged as a normal lookup.
referencestringYour own identifier, echoed back in meta and shown in lookup history.
Response
A 200 response carries the result in data and the cost of the call in meta. These are the fields most integrations read.
successbooleantrue when the lookup ran.
data.full_namestringThe name shown on the public profile.
data.headlinestringThe line under the name, usually the person's title and employer in their own words.
data.locationstringThe city and country the person lists.
data.current_role.titlestringThe title held today, with company and start date in the same object.
data.experiencearrayPast and present positions in order, each with title, company and dates.
data.educationarraySchools attended, with degree and years where shown.
data.skillsarrayThe skills listed on the profile.
data.follower_countnumberHow many people follow the profile.
meta.credits_usednumberCredits charged for this call.
meta.credits_remainingnumberYour balance after the call.
meta.cachedbooleantrue when the result came from the 7-day cache.
meta.request_idstringQuote this when you contact support.
Errors
A failed request returns success: false with an error object, and is never charged. The full list is on the errors page.
| HTTP | Code | Meaning |
|---|---|---|
| 401 | unauthorized | The key is missing, malformed or revoked. |
| 402 | insufficient_credits | Your credits are used up and pay as you go is off or at its limit. |
| 422 | invalid_input | A field is missing or malformed. The field property names it. |
| 429 | rate_limited | Too many requests for this key. Wait for the Retry-After interval. |
| 500 | internal_error | Something failed on our side. Safe to retry. |
| 503 | source_unavailable | An upstream source did not answer in time. Safe to retry. |
Billing
10 credits. Charged when the lookup runs and returns a result. Errors are never charged, and repeating the same input within 7 days is served from cache at no charge.
Product overview and use cases