Skip to main content
POST
/
contact
/
enrich
/
bulk
Enrich Contacts In Bulk
curl --request POST \
  --url https://app.fullenrich.com/api/v2/contact/enrich/bulk \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "Sales Operations in London",
  "webhook_url": "https://example.com/webhook",
  "webhook_events": {
    "contact_finished": "https://example.com/webhook/contact"
  },
  "data": [
    {
      "first_name": "John",
      "last_name": "Snow",
      "domain": "example.com",
      "company_name": "Example Inc",
      "linkedin_url": "https://www.linkedin.com/in/demoge/",
      "enrich_fields": [
        "contact.work_emails",
        "contact.personal_emails",
        "contact.phones"
      ],
      "custom": {
        "user_id": "12584"
      }
    }
  ]
}
'
{
  "enrichment_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}

Documentation Index

Fetch the complete documentation index at: https://docs.fullenrich.com/llms.txt

Use this file to discover all available pages before exploring further.

First time? Set up Authentication

Learn how to authenticate your API requests with your API key.
Use this endpoint to find the contact information of any B2B person:
  • Work email (1 credit)
  • Mobile phone number (10 credits)
  • Personal Email (3 credits)

​
Input needed

To enrich a contact, you must provide either:
  1. first_name + last_name & company (domain or company_name)
  2. linkedin_url
For the best results, provide as much information as possible. Including a LinkedIn URL can improve enrichment rates by +5–20% for emails and +10–60% for mobile phone numbers. If you pass a linkedin_url, we will also return a full contact and company profile (job title, location, headcount, etc.).

​
Practical tips

You can enrich up to 100 contacts in bulk. If you want to enrich only 1 contact, you can pass only 1 contact in the list. All enrichments started on the API are visible on your FullEnrich dashboard. It is good practice to use a readable ‘name’ for each enrichment. This way, you can easily search through them. For instance, if you are enriching just one contact, you might name your enrichment ‘Firstname Lastname’. To pass specific properties, utilize the ‘custom’ field by passing an object. For example, if you are enriching a contact from your CRM, include the CRM ‘contact_id’ in the custom object. This allows you to reference the contact_id when you receive the result on your webhook. The custom value should be a cast as a string (number will return an error) To retrieve the results of your enrichment, you can either provide a webhook URL [recommended] or call the GET /bulk/enrichment_id endpoint [not recommended].

How Do Webhooks Work? [Recommended Read]

Learn how to receive results in real-time, set up per-contact webhooks, and track requests with custom fields.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
​
name
string
required

A readable name for this enrichment (visible in your dashboard)

​
data
object[]
required
​
webhook_url
string

URL that will receive a POST request when the entire enrichment is finished (all contacts processed).

​
webhook_events
object

Optional webhook URLs for specific events during enrichment

Response

OK

​
enrichment_id
string<uuid>
Example:

"2db5ea61-1752-42cf-8ea1-ab1da060cd0a"