Skip to main content

Queue prospect enrichments

Queue one or more prospects for enrichment. This endpoint starts an asynchronous prospect enrichment batch and returns a batch uuid that you can later check with list prospect enrichments or get prospect enrichment.

Use this flow to enrich prospects that already exist in your account's main prospect database. The endpoint matches submitted records by email and updates matching prospects after enrichment; it does not create new prospects or update records that are not already in that database.

Request

Credit usage

This call can use account credits. Credits are applied only when enrichment finds data. Successfully enriching an existing prospect costs 1.5 credits.

Endpoint

POST https://api.woodpecker.co/rest/v2/lead_finder/prospects/enrichments

Headers

x-api-key: {YOUR_API_KEY}
Content-Type: application/json

For details on how to authenticate your requests, please see the authentication guide.

Body

Provide wide prospect context whenever possible. Enrichment usually needs additional signals, such as linkedin_url or first_name and last_name together with company_website. Each submitted email should belong to an existing prospect in your account's main prospect database.

{
"prospects": [
{
"email": "erlich@bachmanity.com",
"first_name": "Erlich",
"last_name": "Bachman",
"linkedin_url": "https://www.linkedin.com/in/erlich-bachman-404xyz",
"company_name": "Bachmanity",
"company_website": "https://bachmanity.com"
},
{
"email": "jared@piedpiper.com",
"first_name": "Jared",
"last_name": "Dunn",
"company_name": "Pied Piper",
"company_website": "https://piedpiper.com"
}
]
}

Body schema

FieldTypeRequiredDescription
prospectsarray[object]YesNon-empty list of prospects to enrich
  └─ emailstringYesEmail address of an existing prospect in the account's main prospect database. The endpoint uses this value as the enrichment identity
  └─ first_namestringNoProspect's first name
  └─ last_namestringNoProspect's last name
  └─ linkedin_urlstringNoProspect's LinkedIn profile URL
  └─ company_namestringNoProspect's company name
  └─ company_websitestringNoProspect's company website

Request samples

Queue prospects for enrichment

curl --request POST \
--url "https://api.woodpecker.co/rest/v2/lead_finder/prospects/enrichments" \
--header "x-api-key: {YOUR_API_KEY}" \
--header "Content-Type: application/json" \
--data '{
"prospects": [
{
"email": "erlich@bachmanity.com",
"first_name": "Erlich",
"last_name": "Bachman",
"linkedin_url": "https://www.linkedin.com/in/erlich-bachman-404xyz",
"company_name": "Bachmanity",
"company_website": "https://bachmanity.com"
},
{
"email": "jared@piedpiper.com",
"first_name": "Jared",
"last_name": "Dunn",
"company_name": "Pied Piper",
"company_website": "https://piedpiper.com"
}
]
}'

Response

Response examples

Batch accepted for processing. Use list prospect enrichments to check recent statuses. Use get prospect enrichment when you already know the returned uuid.

{
"uuid": "e9e6abc4-799e-4c24-b412-7917b1db919d",
"prospects_count": 2,
"total_prospects_count": 2,
"status": "ENQUEUED"
}

Body schema

FieldTypeDescription
uuidstring/nullEnrichment batch identifier. null when nothing was queued
prospects_countintegerNumber of prospects queued in this response
total_prospects_countintegerNumber of prospects submitted in the request
statusstringQueue status.
  • ENQUEUED - at least one prospect was accepted and all eligible prospects were queued
  • PARTIALLY_ENQUEUED - some prospects were queued. Usually because available credits can cover fewer prospects than requested
  • NOT_ENQUEUED - none of the submitted prospects were queued because they are already pending
  • CREDITS_EXHAUSTED - not enough credits. An account admin can manage credits in the billing section of the app