Find Email

Use case

Discover professional or personal email addresses for leads for sales outreach, CRM enrichment, or lead qualification.

Endpoint

POST https://api.sixtyfour.ai/find-email

API Reference

See the full request/response schema and parameters in the API Reference.

Pricing

See Credits & Pricing Guide for credit costs.

Errors

For error responses (400, 403, 422, etc.), see Handling Errors.

Email modes

The mode parameter controls which type of email the API returns. Defaults to PROFESSIONAL if omitted.

Mode	Description	Returned in
`PROFESSIONAL` (default)	Discovers company emails tied to the lead’s employer domain.	`email` and `other_emails` fields
`PERSONAL`	Discovers personal emails (e.g., Gmail, Yahoo). The `email` field still returns the company email when found.	`personal_email` and `personal_other_emails` fields

If the input lead already includes an email field, the API returns it unchanged with appropriate status and type. In PERSONAL mode, if the existing email is a personal email, the API returns immediately without additional processing or cost.

Response format

The email and personal_email fields contain a list of tuples. Each tuple consists of:

Email address (string)
Validation status (string, always uppercase):
- OK — The email address has been validated and is likely deliverable.
- RISKY — The address may work but could bounce, typically because the domain accepts every address (catch-all).
- UNKNOWN — Validation was inconclusive.
- NOT_FOUND — No email could be discovered for this lead.
Email type (string, always uppercase):
- COMPANY — Tied to the company domain.
- PERSONAL — A personal email address (e.g., Gmail, Yahoo).

Other emails

A lead can have more than one address. With verify_emails on (the default), we check every address a provider returns and put the first deliverable one in email (or personal_email). If none is deliverable, you get the first one that did not fail validation, so always read its status. The rest are listed in other_emails (or personal_other_emails) with their own status, so you can fall back to them:

{
  "personal_email": [["sarah.chen@gmail.com", "OK", "PERSONAL"]],
  "personal_other_emails": [
    { "email": "sarahchen@yahoo.com", "status": "RISKY" }
  ]
}

With verify_emails: false nothing is checked: you get the provider’s first address, and the other-emails list is empty.

Addresses that fail validation are left out.
In PERSONAL mode, addresses at the lead’s employer are never listed.
The field is an empty list when there are no other addresses.

Sync usage

curl -X POST "https://api.sixtyfour.ai/find-email" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "lead": {
      "name": "Sarah Chen",
      "company": "Pacific View Studios",
      "title": "Creative Director & Lead Photographer",
      "linkedin": "https://www.linkedin.com/in/sarah-chen-photography"
    },
    "mode": "PERSONAL"
  }'

import requests

response = requests.post(
    "https://api.sixtyfour.ai/find-email",
    headers={
        "x-api-key": "YOUR_API_KEY",
        "Content-Type": "application/json"
    },
    json={
        "lead": {
            "name": "Sarah Chen",
            "company": "Pacific View Studios",
            "title": "Creative Director & Lead Photographer",
            "phone": "+16195551234",
            "linkedin": "https://www.linkedin.com/in/sarah-chen-photography"
        },
        "mode": "PERSONAL"
    }
)

response.raise_for_status()
results = response.json()

const response = await fetch("https://api.sixtyfour.ai/find-email", {
  method: "POST",
  headers: {
    "x-api-key": "YOUR_API_KEY",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    lead: {
      name: "Sarah Chen",
      company: "Pacific View Studios",
      title: "Creative Director & Lead Photographer",
      phone: "+16195551234",
      linkedin: "https://www.linkedin.com/in/sarah-chen-photography"
    },
    mode: "PERSONAL"
  })
});

const results = await response.json();
console.log(results);

Async pattern

For production workflows, use /find-email-async to submit a job and poll for results. This avoids long-lived HTTP connections and lets you parallelize many lookups without blocking your client. The flow is:

Submit — POST /find-email-async with the same body as the sync endpoint. Response includes a task_id.
Poll — GET /job-status/{task_id} until status is completed, failed, cancelled, terminated, or timed_out.
Read result — When completed, the discovered emails are in the result field, in the same shape as the sync response.

The async start endpoint returns uppercase RUNNING. Subsequent /job-status/{task_id} calls return lowercase statuses. charge_amount is returned in cents, not credits.

Polling example

import requests
import time

response = requests.post(
    "https://api.sixtyfour.ai/find-email-async",
    headers={"x-api-key": "YOUR_API_KEY", "Content-Type": "application/json"},
    json={
        "lead": {
            "name": "Sarah Chen",
            "company": "Pacific View Studios",
            "linkedin": "https://www.linkedin.com/in/sarah-chen-photography"
        },
        "mode": "PROFESSIONAL"
    }
)
response.raise_for_status()
task_id = response.json()["task_id"]

while True:
    status = requests.get(
        f"https://api.sixtyfour.ai/job-status/{task_id}",
        headers={"x-api-key": "YOUR_API_KEY"}
    ).json()

    if status["status"] == "completed":
        results = status["result"]
        break
    if status["status"] in ("failed", "cancelled", "terminated", "timed_out"):
        raise RuntimeError(f"Job {status['status']}: {status.get('error', 'Unknown error')}")

    time.sleep(5)

async function runAsync() {
  const start = await fetch("https://api.sixtyfour.ai/find-email-async", {
    method: "POST",
    headers: { "x-api-key": "YOUR_API_KEY", "Content-Type": "application/json" },
    body: JSON.stringify({
      lead: {
        name: "Sarah Chen",
        company: "Pacific View Studios",
        linkedin: "https://www.linkedin.com/in/sarah-chen-photography"
      },
      mode: "PROFESSIONAL"
    })
  });
  if (!start.ok) throw new Error(`Submit failed: ${start.status}`);
  const { task_id } = await start.json();

  while (true) {
    const pollRes = await fetch(
      `https://api.sixtyfour.ai/job-status/${task_id}`,
      { headers: { "x-api-key": "YOUR_API_KEY" } }
    );
    if (!pollRes.ok) throw new Error(`Poll failed: ${pollRes.status}`);
    const status = await pollRes.json();

    if (status.status === "completed") return status.result;
    if (["failed", "cancelled", "terminated", "timed_out"].includes(status.status)) {
      throw new Error(`Job ${status.status}: ${status.error || "Unknown error"}`);
    }
    await new Promise(r => setTimeout(r, 5000));
  }
}

Webhook callback

Pass a webhook_url to receive the result via HTTP POST instead of polling. The signed payload, retry behavior, and verification steps are documented in Outgoing Webhooks.

POST /find-email-async
{
  "lead": {
    "name": "Sarah Chen",
    "company": "Pacific View Studios",
    "linkedin": "https://www.linkedin.com/in/sarah-chen-photography"
  },
  "webhook_url": "https://your-server.com/webhooks/sixtyfour"
}

Bulk processing

Use /find-email-bulk (sync) or /find-email-bulk-async (async) to process up to 100 leads in a single call. Both accept a leads array and the same mode, verify_emails, and webhook_url fields as the single-lead endpoints.

Bulk sync

Returns 200 OK with results once every lead is processed. Best for small batches where you want a single round-trip.

curl -X POST "https://api.sixtyfour.ai/find-email-bulk" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "leads": [
      {
        "name": "Sarah Chen",
        "company": "Pacific View Studios",
        "linkedin": "https://www.linkedin.com/in/sarah-chen-photography"
      },
      {
        "name": "John Doe",
        "company": "Example Corp",
        "linkedin": "https://linkedin.com/in/johndoe"
      }
    ],
    "mode": "PROFESSIONAL"
  }'

import requests

response = requests.post(
    "https://api.sixtyfour.ai/find-email-bulk",
    headers={"x-api-key": "YOUR_API_KEY", "Content-Type": "application/json"},
    json={
        "leads": [
            {
                "name": "Sarah Chen",
                "company": "Pacific View Studios",
                "linkedin": "https://www.linkedin.com/in/sarah-chen-photography"
            },
            {
                "name": "John Doe",
                "company": "Example Corp",
                "linkedin": "https://linkedin.com/in/johndoe"
            }
        ],
        "mode": "PROFESSIONAL"
    }
)
response.raise_for_status()
results = response.json()

Bulk async

Submit a batch, get back a task_id, then poll /job-status/{task_id} (or set webhook_url to receive a callback). Recommended for batches of more than a handful of leads, or when you don’t want to hold a long-lived HTTP connection.

import requests
import time

response = requests.post(
    "https://api.sixtyfour.ai/find-email-bulk-async",
    headers={"x-api-key": "YOUR_API_KEY", "Content-Type": "application/json"},
    json={
        "leads": [
            {
                "name": "Sarah Chen",
                "company": "Pacific View Studios",
                "linkedin": "https://www.linkedin.com/in/sarah-chen-photography"
            },
            {
                "name": "John Doe",
                "company": "Example Corp",
                "linkedin": "https://linkedin.com/in/johndoe"
            }
        ],
        "mode": "PROFESSIONAL"
    }
)
response.raise_for_status()
task_id = response.json()["task_id"]

while True:
    status = requests.get(
        f"https://api.sixtyfour.ai/job-status/{task_id}",
        headers={"x-api-key": "YOUR_API_KEY"}
    ).json()

    if status["status"] == "completed":
        results = status["result"]
        break
    if status["status"] in ("failed", "cancelled", "terminated", "timed_out"):
        raise RuntimeError(f"Job {status['status']}: {status.get('error', 'Unknown error')}")

    time.sleep(10)

Get Started

Intelligence API

Search API

Workflows API

Monitors API

Webhooks

Troubleshooting

Developer Tools

Use case

Endpoint

API Reference

Pricing

Errors

Email modes

Response format

Other emails

Sync usage

Async pattern

Polling example

Webhook callback

Bulk processing

Bulk sync

Bulk async

​Use case

​Endpoint

API Reference

​Pricing

​Errors

​Email modes

​Response format

​Other emails

​Sync usage

​Async pattern

​Polling example

​Webhook callback

​Bulk processing

​Bulk sync

​Bulk async

Use case

Endpoint

Pricing

Errors

Email modes

Response format

Other emails

Sync usage

Async pattern

Polling example

Webhook callback

Bulk processing

Bulk sync

Bulk async