Skip to content
Company & B2B

LinkedIn Profile Lookup

Headline, role history, education and skills from a public LinkedIn profile URL.

POST/v1/linkedin-profile-lookup
10 creditsBulk supportedNewGlobal, public profiles
Request
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"}'
Response
{
  "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>required

Your 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>required

LinkedIn profile URL. Example: https://www.linkedin.com/in/jordan-avery-example

freshboolean

Skip the 7-day cache and run a new lookup. Charged as a normal lookup.

referencestring

Your 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.

successboolean

true when the lookup ran.

data.full_namestring

The name shown on the public profile.

data.headlinestring

The line under the name, usually the person's title and employer in their own words.

data.locationstring

The city and country the person lists.

data.current_role.titlestring

The title held today, with company and start date in the same object.

data.experiencearray

Past and present positions in order, each with title, company and dates.

data.educationarray

Schools attended, with degree and years where shown.

data.skillsarray

The skills listed on the profile.

data.follower_countnumber

How many people follow the profile.

meta.credits_usednumber

Credits charged for this call.

meta.credits_remainingnumber

Your balance after the call.

meta.cachedboolean

true when the result came from the 7-day cache.

meta.request_idstring

Quote 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.

HTTPCodeMeaning
401unauthorizedThe key is missing, malformed or revoked.
402insufficient_creditsYour credits are used up and pay as you go is off or at its limit.
422invalid_inputA field is missing or malformed. The field property names it.
429rate_limitedToo many requests for this key. Wait for the Retry-After interval.
500internal_errorSomething failed on our side. Safe to retry.
503source_unavailableAn 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