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

# Get Prospect Person

> Retrieves a person associated with a prospect by their unique identifier, including their associated company

Retrieves detailed information about a specific person from the global person database. This endpoint returns the person record along with their associated company data if available.

Persons are shared across all organizations and contain enriched data aggregated from multiple lead providers.

## Authentication

This endpoint does not require authentication. Person data is publicly accessible within the Lance platform.

## Request

<ParamField path="id" type="string" required>
  The unique identifier (UUID) of the person to retrieve.
</ParamField>

## Response

Returns a person object with all available fields, including an embedded company object if the person has an associated company.

### Person Fields

<ResponseField name="id" type="string" required>
  Unique identifier (UUID) for the person.
</ResponseField>

<ResponseField name="firstName" type="string" required>
  The person's first name.
</ResponseField>

<ResponseField name="lastName" type="string" required>
  The person's last name.
</ResponseField>

<ResponseField name="jobTitle" type="string | null">
  Current job title.
</ResponseField>

<ResponseField name="city" type="string | null">
  Person's city of residence or work.
</ResponseField>

<ResponseField name="postalCode" type="string | null">
  Person's postal code.
</ResponseField>

<ResponseField name="country" type="string | null">
  Person's country.
</ResponseField>

<ResponseField name="linkedinUrl" type="string | null">
  LinkedIn profile URL.
</ResponseField>

<ResponseField name="phones" type="array">
  Array of phone numbers for the person.
</ResponseField>

<ResponseField name="emails" type="array">
  Array of email addresses for the person.
</ResponseField>

<ResponseField name="companyId" type="string | null">
  UUID of the associated company.
</ResponseField>

<ResponseField name="birthDate" type="string | null">
  Date of birth in ISO 8601 format.
</ResponseField>

<ResponseField name="departments" type="array">
  Array of department names the person belongs to.
</ResponseField>

<ResponseField name="subDepartments" type="array">
  Array of sub-department names.
</ResponseField>

<ResponseField name="functions" type="array">
  Array of job functions.
</ResponseField>

<ResponseField name="seniority" type="string | null">
  Seniority level (e.g., "Director", "Manager", "VP").
</ResponseField>

<ResponseField name="languages" type="array">
  Array of language objects.

  <Expandable title="Language object properties">
    <ResponseField name="language" type="string | null">
      Language name.
    </ResponseField>

    <ResponseField name="level" type="string | null">
      Proficiency level.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="industry" type="string | null">
  Industry the person works in.
</ResponseField>

<ResponseField name="educations" type="array">
  Array of education records.

  <Expandable title="Education object properties">
    <ResponseField name="institution" type="object">
      Institution details with `id`, `name`, `logoUrl`, and `linkedinUrl` properties.
    </ResponseField>

    <ResponseField name="degreeName" type="string | null">
      Name of the degree.
    </ResponseField>

    <ResponseField name="fieldOfStudy" type="string | null">
      Field of study.
    </ResponseField>

    <ResponseField name="grade" type="string | null">
      Grade or GPA.
    </ResponseField>

    <ResponseField name="dates" type="object | null">
      Start and end dates with `start` and `end` properties.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="workExperiences" type="array">
  Array of work experience records.

  <Expandable title="Work experience object properties">
    <ResponseField name="company" type="object | null">
      Company details with `id`, `name`, `logoUrl`, `linkedinUrl`, and `employees` properties.
    </ResponseField>

    <ResponseField name="dates" type="object | null">
      Overall employment dates with `start` and `end` properties.
    </ResponseField>

    <ResponseField name="profilePositions" type="array | null">
      Array of positions held at this company, each with `company`, `description`, `title`, `employmentType`, `location`, and `dates` properties.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="skills" type="array">
  Array of skill strings.
</ResponseField>

<ResponseField name="certificates" type="array">
  Array of certificate records.

  <Expandable title="Certificate object properties">
    <ResponseField name="name" type="string | null">
      Certificate name.
    </ResponseField>

    <ResponseField name="authority" type="string | null">
      Issuing authority.
    </ResponseField>

    <ResponseField name="url" type="string | null">
      URL to certificate.
    </ResponseField>

    <ResponseField name="license_number" type="string | null">
      License or certificate number.
    </ResponseField>

    <ResponseField name="display_source" type="string | null">
      Display source.
    </ResponseField>

    <ResponseField name="date" type="object | null">
      Issue dates with `start` and `end` properties.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="linkedinProfile" type="object | null">
  LinkedIn profile information.

  <Expandable title="LinkedIn profile properties">
    <ResponseField name="headline" type="string | null">
      LinkedIn headline.
    </ResponseField>

    <ResponseField name="summary" type="string | null">
      LinkedIn summary/about section.
    </ResponseField>

    <ResponseField name="pictureUrl" type="string | null">
      Profile picture URL.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="leadOwnerId" type="string | null">
  UUID of the lead owner user.
</ResponseField>

<ResponseField name="consentStatus" type="string">
  GDPR consent status. One of: `UNKNOWN`, `OPTOUT`.
</ResponseField>

<ResponseField name="consentSource" type="string | null">
  Source of consent information.
</ResponseField>

<ResponseField name="consentUpdatedAt" type="string | null">
  ISO 8601 timestamp of when consent was last updated.
</ResponseField>

### External Identifiers

<ResponseField name="baseProviderId" type="string | null">
  Internal provider identifier for this person.
</ResponseField>

<ResponseField name="bullhornId" type="number | null">
  Bullhorn CRM identifier for this person.
</ResponseField>

<ResponseField name="crmId" type="string | null">
  Generic CRM identifier for this person.
</ResponseField>

### Timestamps

<ResponseField name="createdAt" type="string | null">
  ISO 8601 timestamp of when the person record was created.
</ResponseField>

<ResponseField name="updatedAt" type="string | null">
  ISO 8601 timestamp of when the person record was last updated.
</ResponseField>

<ResponseField name="deletedAt" type="string | null">
  ISO 8601 timestamp of when the person was soft-deleted, if applicable.
</ResponseField>

### Embedded Company

<ResponseField name="company" type="object | null">
  The associated company record, included when the person has a `companyId`.
  Contains all company fields as documented in the [Get Prospect
  Company](/api-reference/entities/prospects-company-get) endpoint.
</ResponseField>

## Response Examples

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "firstName": "John",
    "lastName": "Smith",
    "jobTitle": "VP of Engineering",
    "city": "San Francisco",
    "postalCode": "94105",
    "country": "United States",
    "linkedinUrl": "https://www.linkedin.com/in/johnsmith",
    "phones": ["+1-555-123-4567"],
    "emails": ["john.smith@acme.com", "jsmith@gmail.com"],
    "companyId": "660e8400-e29b-41d4-a716-446655440001",
    "birthDate": null,
    "departments": ["Engineering"],
    "subDepartments": ["Platform"],
    "functions": ["Engineering Management"],
    "seniority": "VP",
    "languages": [
      {
        "language": "English",
        "level": "Native"
      },
      {
        "language": "Spanish",
        "level": "Intermediate"
      }
    ],
    "industry": "Computer Software",
    "educations": [
      {
        "institution": {
          "id": null,
          "name": "Stanford University",
          "logoUrl": "https://example.com/stanford.png",
          "linkedinUrl": "https://www.linkedin.com/school/stanford-university"
        },
        "degreeName": "Master's",
        "fieldOfStudy": "Computer Science",
        "grade": null,
        "dates": {
          "start": "2008",
          "end": "2010"
        }
      }
    ],
    "workExperiences": [
      {
        "company": {
          "id": null,
          "name": "Acme Corporation",
          "logoUrl": "https://example.com/acme.png",
          "linkedinUrl": "https://www.linkedin.com/company/acme-corp",
          "employees": {
            "start": "1001",
            "end": "5000"
          }
        },
        "dates": {
          "start": "2020-01",
          "end": null
        },
        "profilePositions": [
          {
            "company": "Acme Corporation",
            "description": "Leading the platform engineering team...",
            "title": "VP of Engineering",
            "employmentType": "Full-time",
            "location": "San Francisco, CA",
            "dates": {
              "start": "2022-06",
              "end": null
            }
          }
        ]
      }
    ],
    "skills": ["Python", "Kubernetes", "System Design", "Team Leadership"],
    "certificates": [],
    "linkedinProfile": {
      "headline": "VP of Engineering at Acme Corporation",
      "summary": "Experienced engineering leader with 15+ years...",
      "pictureUrl": "https://media.licdn.com/dms/image/..."
    },
    "baseProviderId": "baseProvider_person_xyz789",
    "bullhornId": 54321,
    "crmId": null,
    "leadOwnerId": null,
    "consentStatus": "UNKNOWN",
    "consentSource": null,
    "consentUpdatedAt": null,
    "createdAt": "2024-01-15T10:30:00.000Z",
    "updatedAt": "2024-01-20T14:22:00.000Z",
    "deletedAt": null,
    "company": {
      "id": "660e8400-e29b-41d4-a716-446655440001",
      "name": "Acme Corporation",
      "description": "Acme Corporation is a global leader in innovative solutions...",
      "summary": "Enterprise software company specializing in sales automation",
      "headcount": "1001-5000",
      "industry": "Computer Software",
      "phones": ["+1-555-987-6543"],
      "linkedinUrl": "https://www.linkedin.com/company/acme-corp",
      "websiteUrl": "https://acme.com",
      "domain": "acme.com",
      "city": "San Francisco",
      "postalCode": "94105",
      "country": "United States",
      "logoUrl": "https://cdn.example.com/logos/acme.png",
      "legalName": "Acme Corporation Inc.",
      "foundedYear": 2010,
      "revenue": "$50M-$100M",
      "location": null,
      "baseProviderId": "baseProvider_company_abc123",
      "bullhornId": 12345,
      "crmId": null,
      "createdAt": "2024-01-10T08:00:00.000Z",
      "updatedAt": "2024-01-18T12:15:00.000Z"
    }
  }
  ```

  ```json 404 theme={null}
  {
    "error": {
      "code": "NOT_FOUND",
      "message": "Person with id 550e8400-e29b-41d4-a716-446655440000 not found"
    }
  }
  ```
</ResponseExample>

## Error Codes

| Status Code | Error Code       | Description                             |
| ----------- | ---------------- | --------------------------------------- |
| 404         | `NOT_FOUND`      | No person exists with the specified ID. |
| 500         | `INTERNAL_ERROR` | An unexpected server error occurred.    |

## Notes

* The `company` field is automatically populated when the person has a valid `companyId`. If the person has no associated company or the `companyId` is null, the `company` field will be `null`.
* This endpoint is provided under the `/prospects/` path for organizational purposes within the prospecting feature context.
* Person data is deduplicated using LinkedIn URL, email addresses, and provider-specific IDs.