LinkedIn Lookup API

Send a public profile URL

Use POST /api/linkedin/lookup when you already have public LinkedIn profile URLs. Pass your API key from a server application. The sample uses a fictional profile and requests available work emails.

curl https://dievio.com/api/linkedin/lookup \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{
    "linkedinUrls": ["https://www.linkedin.com/in/example-profile/"],
    "includeWorkEmails": true,
    "includePersonalEmails": false,
    "includePhones": false,
    "onlyWithEmails": false,
    "_page": 1,
    "_per_page": 1
  }'

Read a match, a missing field or no match

This abbreviated example shows a matched profile with a missing work email. With onlyWithEmails set to false, a profile can match even when its email field is empty. An empty data array means the request returned no matching records for that page.

{
  "success": true,
  "count": 1,
  "data": [{
    "linkedin_url": "https://www.linkedin.com/in/example-profile/",
    "work_email": null
  }],
  "processed_count": 1,
  "total_input_count": 1,
  "has_more": false,
  "next_page": null
}

To request available phone details, set includePhones to true. If phone enrichment is unavailable, inspect the response’s warnings before deciding what to do with the returned records.

Set page size and check your API balance

Send up to 100,000 input URLs and start with a small _per_page. Reuse the same input array when sending the next_page value as _page. The balance must be able to cover the number of URLs on the requested page before lookup starts.

One API credit is charged per record returned on a successful lookup page. A page with no matches uses zero credits. HTTP 402 means the API balance cannot cover the request. Reduce the page size or add credits before retrying.

LinkedIn Lookup API questions