POST /v2/person to enrich multiple contacts in a single request. Submit a list of up to 100 contact objects and Lusha returns enriched data for each one, including emails, phone numbers, job details, and company information.
Endpoint
api_key request header.
Request requirements
Each contact object in thecontacts array must include a contactId (your own sequential identifier used to match results back to inputs) and at least one of the following:
emaillinkedinUrlpersonId- the most direct identifier; uniquely identifies a record in Lusha’s databasefullNameand a company object withnameordomain
Request body fields
contacts array (required)
string
required
Your own unique sequential ID for this contact. Used to match each result in the response back to your input. Example:
"1234"string
The Lusha person identifier. The most direct lookup method. Example:
"4183886134"string
The full name of the person. Example:
"Dustin Moskovitz"string
The email address of the person. Example:
"dustin@lusha.com"string
The LinkedIn profile URL of the person. Example:
"https://www.linkedin.com/in/dustin/"string
The raw location of the person. Example:
"Chicago" or "Singapore,Chicago"array
Details of the company where the contact is currently (or previously) employed. Each entry includes:
name(string) - company name; required ifdomainis not provided.domain(string) - company domain; required ifnameis not provided.isCurrent(boolean, required) - whether this is the person’s current employer.jobTitle(string) - the person’s job title at this company.fqdn(string) - fully qualified domain name.companySocialId(string) - social ID for the company.
metadata object
boolean
Set to
true to replace outdated job details with the most current information. Example: truestring
Return only contacts that have a specific contact detail. Allowed values:
emailAddresses, phoneNumbersboolean
Set to
true to retrieve only email addresses. Requires the Unified Credits plan.boolean
Set to
true to retrieve only phone numbers. Requires the Unified Credits plan.array
Signal types to retrieve for each contact. Allowed values:
allSignals, promotion, companyChangestring
Start date for signal retrieval in
YYYY-MM-DD format. Defaults to 6 months ago. Example: "2025-03-01"boolean
Set to
true to accept simplified contact profiles when a full match is unavailable. Example: trueResponse fields
A successful200 response includes: