Enrich a person

People Enrich takes what you already know about a person, such as a work email, a profile URL, or a name and employer, and returns the best available candidate with an identity-match score from 0 to 100. It is a beta API available on all plans, including Free. To find people you don’t know yet, use People Search.

Use a work email as the identity clue. See the Quickstart for authentication and SDK setup.

import ContextDev from "context.dev";

const client = new ContextDev({ apiKey: process.env.CONTEXT_DEV_API_KEY });
const result = await client.people.enrich({ email: "[email protected]" });

console.log(result.match);

import os
from context.dev import ContextDev

client = ContextDev(api_key=os.environ["CONTEXT_DEV_API_KEY"])
result = client.people.enrich(email="[email protected]")

print(result.match)

require "cgi/core"
require "context_dev"

client = ContextDev::Client.new(api_key: ENV.fetch("CONTEXT_DEV_API_KEY"))
result = client.people.enrich(email: "[email protected]")

pp result.match

package main

import (
    "context"
    "fmt"
    "os"

    contextdev "github.com/context-dot-dev/context-go-sdk/v2"
    "github.com/context-dot-dev/context-go-sdk/v2/option"
)

func main() {
    client := contextdev.NewClient(option.WithAPIKey(os.Getenv("CONTEXT_DEV_API_KEY")))
    result, err := client.People.Enrich(context.Background(), contextdev.PersonEnrichParams{
        Email: contextdev.String("[email protected]"),
    })
    if err != nil {
        panic(err)
    }

    fmt.Printf("%+v\n", result.Match)
}

<?php

require __DIR__.'/vendor/autoload.php';

use ContextDev\Client;

$client = new Client(apiKey: getenv('CONTEXT_DEV_API_KEY'));
$result = $client->people->enrich(email: '[email protected]');

print_r($result->match);

curl https://api.context.dev/v1/people/enrich \
  -H "Authorization: Bearer $CONTEXT_DEV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "[email protected]"}'

Choose identity clues

Input	Minimum required
Work email	`email`.
Profile URL	`social_urls`.
Name	First and last name, plus company, education, or location.

Clues are additive: supply reliable additional context to improve matching.

Enrich by work email

Send a work email and any reliable company context to POST /people/enrich.

{
  "email": "[email protected]",
  "company": {
    "domain": "example.com"
  }
}

Email inputs can be up to 320 characters. Free and disposable email providers return 422. Preserve the original input and handle rejection without a retry loop. For signup enrichment, show suggestions after checking the match score, and keep the user’s corrections. Use Brand by email if you only need company information.

Enrich by profile URL

Provide one or more person-profile URLs in social_urls. Additional company or location clues can help resolve ambiguous profiles.

{
  "social_urls": [
    "https://www.linkedin.com/in/jane-example/"
  ],
  "company": {
    "domain": "example.com"
  }
}

Send 1–20 valid URLs. Use person-profile pages, not company pages. Keep the profile URL as an external identifier when merging contacts, and review the returned score before treating two records as the same person. To enrich a People Search result, send the URL from its profiles list as social_urls.

Enrich by name

Names alone are ambiguous. Send both first and last name with at least one company, education, or location clue.

{
  "name": {
    "first": "Jane",
    "last": "Example"
  },
  "company": {
    "domain": "example.com"
  },
  "location": {
    "country": "United States",
    "city": "San Francisco"
  }
}

Names accept 1–100 characters per part. Company clues can include a name or domain. Education accepts 1–10 entries with institution details, degree, field of study, or graduation year; valid years range from 1900 to 2200. For attendee lists, send only the context supplied by the source. Do not invent a company or location to satisfy validation. Check the match score and retain an unresolved state for ambiguous people.

Read the result

match.status: "candidate" includes a score and person. Weak candidates can be returned, so choose a score threshold for your workflow and preserve uncertain matches for review. match.status: "not_found" has score: null and person: null. person.current_role_status is present, none, or unknown. When it is unknown, a missing role is unverified, not evidence that the person has no job. Profiles can include experience, education, skills, social links, and timestamps.

Availability and errors

Insufficient clues return 400; free or disposable email inputs return 422. Handle 408 and transient server errors separately from not_found. ZDR omits hosted avatar URLs; see zero data retention. The reference describes all fields, and the lead enrichment recipe shows how to use the profile.

Get started

Web data

Entity Enrichment

Automation

Account and billing

Production

Enrich a person

Enrich a person

Choose identity clues

Enrich by work email

Enrich by profile URL

Enrich by name

Read the result

Availability and errors

​Enrich a person

​Choose identity clues

​Enrich by work email

​Enrich by profile URL

​Enrich by name

​Read the result

​Availability and errors

Enrich a person

Choose identity clues

Enrich by work email

Enrich by profile URL

Enrich by name

Read the result

Availability and errors