Skip to main content
POST
/
api
/
v1
/
enrich
/
realtime
/
lead
/
curl --request POST \
  --url https://api.generect.com/api/v1/enrich/realtime/lead/ \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "id": "ACwAAAE9bk0BxY7Qf2mN4pR8sT1vW3zA5cE6gH9"
}
'
{
  "data": {
    "id": "ACwAAAE9bk0BxY7Qf2mN4pR8sT1vW3zA5cE6gH9",
    "first_name": "Jordan",
    "last_name": "Ellis",
    "title": "CEO",
    "linkedin_url": "https://www.linkedin.com/in/jordan-ellis",
    "company": {
      "id": 1035,
      "name": "Microsoft",
      "domain": "microsoft.com"
    },
    "work_history": [],
    "education": [],
    "skills": []
  },
  "meta": {
    "amount_charged": 0.04
  }
}

Use Case:

Retrieve a fresh lead profile, including reverse email lookup, by Generect ID, LinkedIn URL, or email.

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:

"ACwAAAE9bk0BxY7Qf2mN4pR8sT1vW3zA5cE6gH9"

Response

Fresh full lead profile

data
object

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

meta
object

Operation metadata returned in every data/meta response.