---
title: "Enrich Profile V1 Endpoint"
method: POST
path: "/enrich/profile/v1"
tags: ["enrichment"]
---

# Enrich Profile V1 Endpoint

`POST /enrich/profile/v1`

## Request

- Base URL: `https://api.dataforb2b.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.dataforb2b.ai/enrich/profile/v1`
- Auth: none declared

Profile enrichment endpoint — V1.

Now backed by the DECO engine (Voyager REST FullProfileWithEntities — clip-safe,
all company data inline). Same response format as before and as `/enrich/profile`,
so existing v1 integrations keep working unchanged — no version bump needed. The
token-clipping GraphQL engine is NO LONGER used by this endpoint.

Enriches a LinkedIn profile with the requested data types.
All enrichment types are optional - at least one must be requested.

**Supported profile_identifier formats:**
- Full URL: `https://www.linkedin.com/in/john-doe-123456/`
- Short URL: `linkedin.com/in/john-doe`
- Public ID only: `john-doe`
- Member identity: `ACoAABxxxxxx`
- URN: `urn:li:fsd_profile:ACoAABxxxxxx`
- Encoded profile ID: `prof_PVXj1LZJg54zXKcnKNBusu8LgvJX5SYm5QYj`

**Available enrichments:**
- **enrich_profile**: Full profile details (same format as /search/people response)
- **enrich_work_email**: Professional/work email address
- **enrich_personal_email**: Personal email address
- **enrich_phone**: Phone number

**Example request:**
```json
{
    "profile_identifier": "prof_PVXj1LZJg54zXKcnKNBusu8LgvJX5SYm5QYj",
    "enrich_profile": true,
    "enrich_work_email": true
}
```

**Example response:**
```json
{
    "profile": {
        "id": "prof_xxxxx",
        "first_name": "John",
        "last_name": "Doe",
        "headline": "Software Engineer",
        ...
    },
    "work_email": "john.doe@company.com"
}
```

## Headers

- `api-key` string, nullable

## Request body

- EnrichRequest: Unified enrichment request - all fields optional except profile_identifier. At least one enrich_* field must be True. Supports batch enrichment with comma-separated identifiers.
  - `profile_identifier` string, required: LinkedIn profile identifier(s). Single or comma-separated for batch. Supports: https://linkedin.com/in/john-doe, john-doe, ACoAABxxxxxx, prof_xxx Batch example: 'prof_xxx1,prof_xxx2,prof_xxx3'
  - `enrich_profile` boolean: Enrich full profile details (same format as search/people response)
  - `enrich_work_email` boolean: Enrich professional/work email address
  - `enrich_personal_email` boolean: Enrich personal email address
  - `enrich_phone` boolean: Enrich phone number
  - `enrich_github` boolean: Find GitHub profile URL via Google search

## Response `200`

Successful Response

- EnrichResponse: Unified enrichment response - only includes requested fields. For batch requests, returns a list of results.
  - `profile` object, nullable: Full profile data (single request)
  - `work_email` string, nullable: Professional/work email address (single request)
  - `personal_email` string, nullable: Personal email address (single request)
  - `phone` string, nullable: Phone number (single request)
  - `git_profile` object, nullable: GitHub profile data (username, bio, repos, followers, pinned_repos, etc.)
  - `results` object[], nullable: Batch results (only present for batch requests)
  - `credits_used` number: Credits charged for this request

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/dataforb2b/apis/dataforb2b-api.md) · [All operations](https://skmtc.dev/dataforb2b/apis/dataforb2b-api/llms.txt) · [OpenAPI document](https://skmtc.dev/dataforb2b/apis/dataforb2b-api/revisions/24ea79caa1a1?raw)