Skip to main content
POST
Enrich people
Request an enrichment of emails and/or phones for up to 500 people. folk searches the requested fields with external data providers, and saves the data found on each person. To learn more, read the Person enrichments guide.

Asynchronous processing

The enrichment runs asynchronously: the request returns a 202 response with the enrichment in the pending status, before any person is enriched. If no ID matches a person you can enrich, the enrichment is already completed in the response, with every item skipped. To know when the enrichment is over, either:
  • Poll the Get an enrichment of people endpoint with the returned id until the status of the enrichment is completed or failed.
  • Subscribe a webhook to the person_enrichment.finished event, then get the enrichment from the url of the event.
Once completed, the enrichment contains the result for each person in items, and the counts per result in summary. You can also find the enrichment later with List enrichments of people.

Credits

Enrichments consume the enrichment credits of the workspace. Read how credits are consumed to learn more.
  • Check the credits left in the workspace with Get credits.
  • The request is rejected with a 402 error if the workspace doesn’t have enough credits for the maximum possible cost of the enrichment. Nothing is performed or charged: send a smaller request, or add credits to the workspace.

People to enrich

Enriching a person needs the contributor role or above in at least one of its groups.
  • Duplicate IDs are enriched once.
  • IDs of people already merged into another one are resolved to the resulting person.
  • IDs that don’t match a person you can enrich (unknown, deleted, not accessible to you, or you aren’t a contributor in any of the person’s groups) don’t reject the request: they are reported with the skipped status in the result of the enrichment.
  • People deleted or merged after the request, including while being enriched, no longer appear in the result of the enrichment, nor in its summary.
The more a person has data, the better the results. Names, a company, a company website and a LinkedIn URL help the providers find the requested fields. For people that aren’t fully enriched, missingInputs lists the data that was missing: read Improving the results to learn more.

Authorizations

Authorization
string
header
required

API key for authentication

Headers

Idempotency-Key
string

A unique key, such as a UUID, that makes retrying this request safe: a retry with the same key and body returns the original response without running the operation again. Keys are kept for 24 hours after the request completes.

Maximum string length: 255
Example:

"8e03978e-40d5-43e8-bc93-6894a57f9324"

Body

application/json
fields
enum<string>[]
required

The fields to enrich on each person. Each field can only be requested once.

Required array length: 1 - 2 elements

A person field to enrich. One of: emails, phones.

Available options:
emails,
phones
Example:
ids
string[]
required

The IDs of the people to enrich, up to 500. Duplicate IDs are enriched once. IDs that don't match a person you can enrich don't reject the request: they are reported as items with the skipped status.

Required array length: 1 - 500 elements
Required string length: 40
Example:

Response

The enrichment that has been requested.

data
object
required

An enrichment of emails and/or phones for a list of people, run asynchronously.

Example:
deprecations
string[]
Example: