Enrich people (bulk)
Enrich up to 50 people in one request — the bulk counterpart to Enrich person. Each lookup object carries one LinkedIn identifier you already hold (URL, vanity ID, numeric ID, or URN) and comes back as a full person record. No Specter ID is involved: use Get person by ID when you already have one.
queued rows aren’t charged. What you need
A JSON array of 1–50 lookup objects, each identifying one person by LinkedIn URL, vanity ID, numeric ID, or URN.
Behaviour
- Provide exactly one identifier per lookup object.
- Results are returned in input order, so each row maps back to its lookup.
- Each row carries a
status:found(resolved, with thepersonpayload) orqueued(not found; an enrichment was started, poll later).
What you do next
- Reach out. The profile doesn’t include a contactable address; get one with Get person email.
Authorizations
Body
1 - 50 elementsThe person's LinkedIn profile URL. Accepts http/https, with or without www.
"https://www.linkedin.com/in/janedoe"
The person's LinkedIn vanity ID, the slug at the end of their profile URL (e.g. john-doe-123abc in linkedin.com/in/john-doe-123abc).
"janedoe"
The person's LinkedIn numeric member ID.
123456789
The person's LinkedIn URN, a stable, non-changing reference found in many datasets.
"ACoAAAxxxxxxxx"
Response
One row per lookup, in input order. found rows carry the resolved person; queued rows carry the enrichment request context.