> For the complete documentation index, see [llms.txt](https://kevins-organization-58.gitbook.io/smtp-ghost-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kevins-organization-58.gitbook.io/smtp-ghost-api/linkedin-email-finder.md).

# LinkedIn Email Finder

Fetches a LinkedIn profile and attempts to discover an email address. \
\
Always returns `status: "success"` if the profile is fetched, even if no email is found.

### Endpoint

**POST** `/api/v1/linkedin_finder`

### Base URL

```
https://smtpghost.com/api/v1/linkedin_finder
```

### Headers

| Header         | Value                         | Required |
| -------------- | ----------------------------- | -------- |
| `Content-Type` | `application/json`            | Yes      |
| `X-KEY`        | `<your-organization-api-key>` | Yes      |

### Request Body

```json
{
  "linkedin_url": "https://www.linkedin.com/in/urrutia/"
}
```

### Success Response (200 OK)

#### Email Found

```json
{
  "status": "success",
  "linkedin_url": "https://www.linkedin.com/in/urrutia/",
  "email_address": "kevin@voymedia.com",
  "email_status": "VALID",
  "account_type": "professional",
  "is_catch_all": false,
  "profile": {
    "linkedin_url": "https://www.linkedin.com/in/urrutia/",
    "input_url": "https://www.linkedin.com/in/urrutia/",
    "name": "Kevin Urrutia",
    "city": "New York, New York, United States",
    "country_code": "US",
    "about": "We’re a performance-based, full-service agency that does more than just sales and…",
    "location": "New York",
    "followers": 10815,
    "connections": 500,
    "avatar": "https://media.licdn.com/…",
    "banner_image": "https://media.licdn.com/…",
    "current_company_id": "voy-media",
    "current_company_name": "Voy Media",
    "current_company_link": "https://www.linkedin.com/company/voy-media?…",
    "company_id": 5,
    "linkedin_num_id": "43092606",
    "educations_details": "State University of New York at Binghamton",
    "default_avatar": false,
    "memorialized_account": false,
    "snapshot_fetched_at": "2025-05-16T12:10:40.302-04:00",
    "education": [ /* array of education objects */ ],
    "activity":  [ /* array of activity objects  */ ],
    "experience": [],
    "bio_links": [],
    "honors_and_awards": [],
    "email": "kevin@voymedia.com",
    "created_at": "2024-09-29T14:44:02.378-04:00",
    "updated_at": "2025-05-16T12:10:46.874-04:00"
  }
}
```

#### No Email Found

```json
{
  "status": "success",
  "linkedin_url": "https://www.linkedin.com/in/urrutia/",
  "message": "No valid or risky email found.",
  "profile": { /* same profile object */ }
}
```

**Note:** Even when no email is found, the endpoint returns `status: "success"` with a `message` field.

### Error Response

#### Internal Server Error (500)

```
{
  "status": "error",
  "error": "An internal error occurred: Connection timed out",
  "profile": { /* partial profile data */ }
}
```

**Note:** On any unhandled exception, credits are refunded and a 500 is returned with `status: "error"`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kevins-organization-58.gitbook.io/smtp-ghost-api/linkedin-email-finder.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.