Enrich Email or Domain

curl --request POST \
  --url https://api.example.com/v1/email/enrich \
  --header 'Content-Type: application/json' \
  --data '
{
  "email": "<string>",
  "domain": "<string>",
  "include": [
    {}
  ]
}
'

{
  "data": {
    "person": {},
    "company": {},
    "social": {},
    "source": "<string>",
    "confidence": 123,
    "credits_remaining": 123
  }
}

POST

enrich

curl --request POST \
  --url https://api.example.com/v1/email/enrich \
  --header 'Content-Type: application/json' \
  --data '
{
  "email": "<string>",
  "domain": "<string>",
  "include": [
    {}
  ]
}
'

{
  "data": {
    "person": {},
    "company": {},
    "social": {},
    "source": "<string>",
    "confidence": 123,
    "credits_remaining": 123
  }
}

This endpoint consumes enrichment credits from your workspace balance. Each successful lookup costs 1 credit. If the workspace is out of credits, the API returns 402 insufficient_credits.

Request

Headers

Authorization: Bearer wbk_your_api_key_here
Content-Type: application/json

Idempotency-Key

string

Optional UUID to deduplicate retries within 24 hours. The credit is only charged on the first successful call.

Body Parameters

string

Email address to resolve. Either email or domain is required.

domain

string

Domain name to resolve (e.g. acme.com). Either email or domain is required.

include

array

Optional subset of sections to return: person, company, social. Defaults to all.

Response

data

object

Show properties

person

object

Personal details when email is provided: full_name, first_name, last_name, job_title, seniority, location, linkedin_url.

company

object

Organizational details: name, domain, industry, size, founded_year, description, linkedin_url, hq_location.

Social handles, where available.

source

string

Origin of the data (vendor_a, vendor_b, cached).

confidence

number

Confidence score from 0.0 to 1.0.

credits_remaining

integer

Workspace credit balance after this call.

Responses include X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and X-Request-ID.

curl -X POST \
  https://data.leadlex.com/functions/v1/api-gateway/v1/email/enrich \
  -H "Authorization: Bearer wbk_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{"email": "jane@acme.com"}'

Example Response

{
  "data": {
    "person": {
      "full_name": "Jane Doe",
      "first_name": "Jane",
      "last_name": "Doe",
      "job_title": "General Counsel",
      "seniority": "executive",
      "location": "New York, NY, US",
      "linkedin_url": "https://linkedin.com/in/janedoe"
    },
    "company": {
      "name": "Acme Corp",
      "domain": "acme.com",
      "industry": "Legal Services",
      "size": "201-500",
      "founded_year": 1998,
      "hq_location": "New York, NY, US"
    },
    "source": "vendor_a",
    "confidence": 0.92,
    "credits_remaining": 4872
  }
}

Errors

Status	Code	Description
400	`validation_error`	Neither `email` nor `domain` was provided
401	`invalid_key`	Invalid or expired API key
402	`insufficient_credits`	Workspace credit balance is exhausted
403	`insufficient_permissions`	Missing `write:enrich` permission
404	`no_match`	Upstream providers returned no data for the input
429	`rate_limited`	Rate limit exceeded

Trigger Email Sync List Top Correspondents

​Request

​Headers

​Body Parameters

​Response

​Example Response

​Errors

Request

Headers

Body Parameters

Response

Example Response

Errors