POST
/
enrich
/
database
/
lead
curl --request POST \
  --url https://api.generect.com/api/v1/enrich/database/lead/ \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "id": "lead_abc123xyz"
}
'
{
  "data": {
    "id": "lead_abc123xyz",
    "first_name": "John",
    "last_name": "Doe",
    "title": "CEO",
    "headline": "CEO at Acme",
    "linkedin_url": "https://linkedin.com/in/johndoe",
    "location": "San Francisco, CA",
    "seniority": "CXO",
    "company": {
      "id": "comp_def456",
      "name": "Acme Technologies",
      "domain": "acmetech.com",
      "linkedin_url": "https://linkedin.com/company/acme",
      "industry": "Software",
      "headcount": 150
    },
    "work_history": [],
    "education": [],
    "skills": []
  },
  "meta": {
    "amount_charged": 0.02
  }
}

Use Case:

Retrieve a full lead profile from cached data by Generect ID, LinkedIn URL, or email (reverse lookup).

Pricing

This is a billable endpoint — you are charged only when a lead is found and returned. If nothing is found, the request is free.
Your price decreases automatically as your lifetime spend grows. Check your current tier and pricing →

Authorizations

Authorization
string
header
required

Use the required Token prefix. Example: Authorization: Token xxxxxxxxx

Body

application/json
id
string
required

Internal Generect lead identifier returned by Search or Preview.

Example:

"lead_abc123xyz"

Response

Full lead profile. If no data is found, the request is free.

data
object

Full lead profile — see the example for the field set.

meta
object

Operation metadata returned in every data/meta response.