> ## Documentation Index
> Fetch the complete documentation index at: https://docs.seamless.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# LinkedIn URL → Profile

> Turn a LinkedIn, Sales Navigator, or Recruiter profile URL into a full contact profile with verified emails, direct dials, and mobile numbers.

> [!NOTE]
>
> **Endpoint** `POST /contacts/research` · **Credits** by default 1 for email, 5 for phone ([details](https://docs.seamless.ai/core-concepts/credits.md#contact-research-costs)) · **Delivery** async (poll or webhook) · **Versions** v1, v2

## Introduction

Send a LinkedIn profile URL and get back the contact details LinkedIn doesn't show: work and personal emails with validation status, direct dials, mobile numbers, company phones, and a normalized location. Accepts public profile URLs, Sales Navigator URLs, and Recruiter URLs.

Use it to enrich LinkedIn exports, Sales Navigator lead lists, and URLs captured by your own tools.

## AI agent prompt

```text theme={null}
Read https://docs.seamless.ai/llms.txt and https://docs.seamless.ai/api-catalog/linkedin-to-profile.
Using my Seamless.AI API key from SEAMLESS_API_KEY, read a CSV of LinkedIn URLs, send them in batches
no larger than the page's per-request limit to POST https://api.seamless.ai/api/client/v1/contacts/research as
{"contacts":[{"liProfileUrl": <url>}]}, poll each requestId until done,
and write email, contactPhone1, jobTitle, and companyName back to the CSV.
```

## Authentication

Send your API key in the `Token` header, or `Authorization: Bearer <token>` with [OAuth](https://docs.seamless.ai/authentication/oauth.md). Create a key under [Settings → Public API](https://docs.seamless.ai/authentication/api-keys.md).

## Example

```bash Research theme={null}
curl -X POST https://api.seamless.ai/api/client/v1/contacts/research \
  -H "Token: $SEAMLESS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "contacts": [
      {"liProfileUrl": "https://www.linkedin.com/in/janedoe"},
      {"liSalesNavUrl": "https://www.linkedin.com/sales/lead/ACwAAA..."}
    ]
  }'
```

```bash Poll theme={null}
curl "https://api.seamless.ai/api/client/v1/contacts/research/poll?requestIds=REQUEST_ID" \
  -H "Token: $SEAMLESS_API_KEY"
```

For Python, JavaScript, and other languages, see [Research contacts](https://docs.seamless.ai/api-reference/v1/contact-research/research-contacts.md) in the API reference.

## Reference

Each item in `contacts` needs one of these URLs.

| Parameter | Type | Required | Description |
| - | - | - | - |
| `contacts` | object\[] | Yes | Contact enrich request. Provide an array of contacts to research by identity. Each item must include one of the following combinations: contactName and companyName (optionally include title when using isJobChange); contactName and domain; email; liProfileUrl; liSalesNavUrl; liRecruiterUrl. Intended as an alternative to searchResultIds; if both are sent, their combined length must not exceed 500. When isJobChange is true, only the contacts array should be used. Each contact is charged the same way as a searchResultId. Up to 500 values. |
| `contacts[].liProfileUrl` | string | No | LinkedIn public profile URL. Can be used as a standalone identifier. |
| `contacts[].liSalesNavUrl` | string | No | LinkedIn Sales Navigator profile URL. Can be used as a standalone identifier. |
| `contacts[].liRecruiterUrl` | string | No | LinkedIn Recruiter profile URL. Can be used as a standalone identifier. |
| `listIds` | integer\[] | No | IDs of the contact lists to add each newly saved contact to. Contacts that were already researched are not saved again, so they are not added to the lists. The lists must already belong to the authenticated user; an unknown ID fails the research request items, which report the error when you poll for them. Up to 50 values. |
| `skipDeduplicationCheck` | boolean | No | When true, research skips both duplicate checks and researches the record again, which charges credits again. By default a request is reported as `duplicate` when the same record was researched in the last few minutes, and as `contact-already-researched` when the contact is already saved in your My Contacts. Within those few minutes, a request for contact data the earlier research didn't get (for example phone after an email-only research) is researched onto that contact instead, and only the new data is charged. Repeated IDs within a single request are always collapsed into one research request. Default `false`. |

## Response

The call returns `202` with `requestIds`. When a poll returns `status: done`, `contact` holds the full record:

| Field | Description |
| - | - |
| `email`, `email1`-`email3`, `email{n}EmailAI` | Work emails with validation status |
| `personalEmail` | Personal email, when available |
| `contactPhone1`, `contactPhone2`, `contactPhone{n}DataType` | Direct dials and mobiles |
| `companyPhone1`-`companyPhone3` | Company phones |
| `fullName`, `jobTitle`, `seniority`, `companyName`, `companyDomain` | Identity and employer |
| `lIProfileUrl`, `lISalesNavUrl`, `lIRecruiterUrl` | All known LinkedIn URLs |

See the [Data dictionary](https://docs.seamless.ai/api-catalog/data-dictionary.md) for every field.

## Errors

| Status | Meaning |
| - | - |
| `401` | Missing or invalid API key |
| `422` | `insufficientCredits` or `missingApiAccess` |
| `429` | Rate limit reached |
| Poll `not found` | No person matched the URL |

## Related

* [Email → Profile](https://docs.seamless.ai/api-catalog/email-to-profile.md)
* [Phone → Profile](https://docs.seamless.ai/api-catalog/phone-to-profile.md)
* [Contact Research API](https://docs.seamless.ai/api-catalog/contact-enrichment.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.