Start bulk email find

curl --request POST \
  --url https://api.generect.com/api/v1/email/find/bulk/ \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "leads": [
    {
      "lead_id": "lead_abc123xyz"
    },
    {
      "first_name": "Jane",
      "last_name": "Smith",
      "domain": "corp.io"
    }
  ]
}
'

{
  "data": null,
  "meta": {
    "job_id": "job_123",
    "status": "pending",
    "total": 2,
    "processed": 0,
    "amount_charged": 0,
    "error": null
  }
}

POST

find

bulk

Start bulk email find

curl --request POST \
  --url https://api.generect.com/api/v1/email/find/bulk/ \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "leads": [
    {
      "lead_id": "lead_abc123xyz"
    },
    {
      "first_name": "Jane",
      "last_name": "Smith",
      "domain": "corp.io"
    }
  ]
}
'

{
  "data": null,
  "meta": {
    "job_id": "job_123",
    "status": "pending",
    "total": 2,
    "processed": 0,
    "amount_charged": 0,
    "error": null
  }
}

Use Case:

Start an asynchronous bulk job to find verified work emails for many leads.

Pricing

This is a billable endpoint — you are charged only for each valid email found. If no email 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

leads

(By Lead ID · object | By LinkedIn URL · object | By Name and Domain · object)[]

required

Leads to find emails for. Each entry is one of: {lead_id}, {linkedin_url}, or {first_name, last_name, domain}.

By Lead ID
By LinkedIn URL
By Name and Domain

Show child attributes

Response

Bulk job accepted

data

object

Always null — results arrive via the bulk status endpoint.

​Use Case:

​Pricing

Authorizations

Body

Response

Use Case:

Pricing