Enrich by Email

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

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

POST

enrich

Enrich by Email

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

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

This endpoint consumes 1 enrichment credit per successful call. Requests that find no data return 409 no_match and do not consume credits. If the workspace balance is zero, the API returns 402 insufficient_credits.

Request

Use this endpoint to fetch enrichment data when you do not yet have a contact record - for example, scoring inbound leads before creating them or pre-populating a signup form. Unlike /v1/enrich/contact, this endpoint never writes to your database.

Headers

Authorization: Bearer wbk_your_api_key_here
Content-Type: application/json

Idempotency-Key

string

Optional UUID. Deduplicates retries within 24 hours; the credit is charged only on the first call.

Body Parameters

string

required

Email address to look up. Must be a syntactically valid RFC 5321 address.

include

array

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

verify

boolean

default:"false"

When true, additionally performs SMTP verification and returns deliverable status.

Response

data

object

Show properties

person

object

full_name, first_name, last_name, job_title, seniority, location, linkedin_url

company

object

name, domain, industry, size, founded_year, description, hq_location, linkedin_url

Known social handles

deliverable

string

deliverable, undeliverable, risky, or unknown - only present when verify=true

source

string

Data source identifier

confidence

number

0.0 - 1.0

credits_remaining

integer

Workspace balance after the 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/enrich/email \
  -H "Authorization: Bearer wbk_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{"email": "jane@acme.com", "verify": true}'

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",
      "hq_location": "New York, NY, US"
    },
    "deliverable": "deliverable",
    "source": "vendor_a",
    "confidence": 0.93,
    "credits_remaining": 4869
  }
}

Errors

Status	Code	Description
400	`validation_error`	Malformed or missing email
401	`invalid_key`	Invalid or expired API key
402	`insufficient_credits`	Workspace credit balance is exhausted
403	`insufficient_permissions`	Missing `write:enrich` permission
409	`no_match`	Upstream providers returned no data
429	`rate_limited`	Rate limit exceeded

Enrich Company Scan Business Card

​Request

​Headers

​Body Parameters

​Response

​Example Response

​Errors

Request

Headers

Body Parameters

Response

Example Response

Errors