Skip to main content
POST
/
v2
/
enrichments
/
bulk
curl --request POST \
  --url https://api.lemlist.com/api/v2/enrichments/bulk \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Content-Type: application/json' \
  --data null
[
  {
    "id": "enr_7y2vszPS5F6C9qLEg",
    "metadata": {
      "id": "some_id"
    }
  },
  {
    "id": "enr_4e1vEfOA3F7D9dJHd",
    "metadata": "some_id"
  },
  {
    "error": "MISSING_INPUTS",
    "metadata": "some_id"
  }
]
This endpoint allows you to send a batch of enrichment requests for multiple entities, processing up to 500 enrichments in a single API call.
Unlike other endpoints, this one starts with /v2/enrichments.

​
How to use the endpoint

The bulk enrichment API is ideal for:
  • Processing large lists of prospects efficiently
  • Enriching CRM data in batches
  • Finding and verifying multiple contacts simultaneously
  • Automating data enrichment workflows at scale

​
Enrichment Types

TypeRequired InputDescription
find_emaillinkedinUrl OR (firstName + lastName + companyName + companyDomain)Find and verify email addresses
find_phonelinkedinUrlFind phone numbers
verifyemailVerify email deliverability
linkedin_enrichmentlinkedinUrl OR email OR (firstName + lastName + (companyName OR companyDomain))Enrich with LinkedIn profile data

​
Metadata

The metadata field can be a string or an object. This data will be returned in both the API response and webhook notifications, allowing you to track and correlate enrichment requests.

​
Response

The API returns an array where each element corresponds to a request in the input array. Successful requests return an enrichment ID, while failed requests return an error code. 
{
  "id": "enr_cawQhM9N3pWkqw2Yt",
  "metadata": {
    "some_id": "some_id"
  }
}

​
Getting Results

Check Enrich Data for details on the enrichment result structure.
Since enrichment is asynchronous, you can retrieve results in two ways:
  1. Polling: Use the Get Enrichment Result endpoint with the returned enrichment ID
  2. Webhooks: Provide a webhookUrl query parameter to receive notifications when enrichments complete
Learn more about webhooks in the Enrich object definition.

​
Error Codes

Error CodeDescription
WRONG_INPUT_FORMATThe input must be an object containing at least one valid field
WRONG_METADATA_FORMATThe metadata field must be a string or an object
NO_WORKFLOW_REQUESTEDAt least one enrichment type must be specified
WRONG_ENRICHMENT_REQUEST_FORMATThe enrichmentRequests field must be an array
UNAUTHORIZED_WORKFLOW_REQUESTEDInvalid enrichment type specified
TOO_MANY_ENRICHMENTS_REQUESTEDMaximum 500 enrichments per request
NO_ENRICHMENTS_REQUESTEDThe body must contain at least one enrichment
WRONG_BODY_FORMATThe body must be a valid JSON array
MISSING_INPUTSRequired input fields are missing for the requested enrichment type
MISSING_EMAILEmail is required for verify enrichment
MISSING_LINKEDIN_URLLinkedIn URL is required for this enrichment type

​
Limits

  • Maximum requests per call: 500 enrichments
  • Rate limits: Standard API rate limits apply (20 requests per 2 seconds)
  • Credits: Each enrichment type consumes credits from your team’s balance
See Credits for more information about credit consumption.

Authorizations

​
Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Query Parameters

​
webhookUrl
string

Webhook URL for enrichment events

Body

application/json · object[]
​
enrichmentRequests
enum<string>[]
required

Array of enrichment types to perform. Must contain at least one of: find_email, find_phone, verify, linkedin_enrichment

Example:
["find_email", "verify"]
​
input
object

Input data for enrichment. Required fields depend on enrichmentRequests.

​
metadata

Custom data to be returned in the response and webhook. Can be a string or an object

Example:
{ "id": "some_id" }

Response

Success - Returns enrichment IDs and metadata for each request

  • Option 1
  • Option 2
​
id
string

Enrichment ID

Example:

"enr_cawQhM9N3pWkqw2Yt"

​
metadata

The metadata provided in the request