Email finder API for verified B2B emails

Enrich contacts with valid professional emails, verified through catch-all validation and real-world signals to improve outbound deliverability.

Trusted by the best GTM teams

Enrichment

Find verified emails you can actually use

Enrich any professional contact with valid B2B emails powered by real signals and catch-all validation. Build cleaner lists, reduce risk, and improve outbound deliverability.

Deep catch-all validation before delivery

Ready for outbound, CRM, and automation

EnrichmentLIVE
200 OKAPPLICATION/JSON

From contact data to verified emails

Find emails

Discover professional email addresses. Find B2B emails attached to a contact using identity signals, company context, domain logic, and real-world data points.

01Find emailsBLITZ API · V2
200 OKAPPLICATION/JSON

Validate quality

Verify before you send. Every email is checked with our catch-all validation layer to reduce risky addresses, protect deliverability, and improve campaign quality.

02Validate qualityBLITZ API · V2
200 OKAPPLICATION/JSON

Activate workflows

Move from emails to action. Use verified emails to power outbound campaigns, enrich CRM records, complete prospect lists, and trigger automated workflows.

03Activate workflowsBLITZ API · V2
200 OKAPPLICATION/JSON

Built for high-quality email enrichment

Find better emails, verify them before activation, and improve the quality of every outbound workflow.

Find better

Use real signals and company context to find professional emails that are more likely to match the right contact.

Send cleaner

Emails are verified with catch-all validation to reduce risk, improve deliverability, and protect outbound performance.

Scale outbound

Enrich contacts at scale for prospecting, CRM completion, outbound sequences, and automated data workflows.

The endpoint

A LinkedIn URL in, a verified work email out

The email finder API takes a LinkedIn profile URL and returns the person's verified work email, with every work address found for the jobs on the profile in all_emails. An address that cannot be proven is not returned: found comes back false instead of a guess.

POST/v2/enrichment/email
curl -X POST https://api.blitz-api.ai/v2/enrichment/email \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"person_linkedin_url":"https://www.linkedin.com/in/example-person"}'
from blitz_api import BlitzAPI

client = BlitzAPI()  # reads BLITZ_API_KEY

email = client.enrichment.email(person_linkedin_url="https://www.linkedin.com/in/example-person")
if email.found:
    print(email.email)
import { BlitzAPI } from "blitz-api-js";

const client = new BlitzAPI(); // reads BLITZ_API_KEY

const email = await client.enrichment.email({ person_linkedin_url: "https://www.linkedin.com/in/example-person" });
if (email.found) console.log(email.email);
200 OKfoundemailall_emails[]

ENRICHMENT

Every enrichment endpoint returns the same structured record, whatever you send in.

API Docs
Maya ChenRAWRESOLVED

Frequently asked questions

How does BlitzAPI find emails?

Emails are discovered from identity signals, company context, domain logic, and real-world data points attached to the contact. They are never guessed from name patterns: an address we cannot prove comes back Not Found.

Are the emails verified before I get them?

Yes. Every address goes through the catch-all validation layer, which works out whether an address on a permissive domain can actually be proven. Only proven addresses are delivered; anything we cannot prove comes back Not Found instead of a maybe.

Can I use it at outbound scale?

The API is built for high-volume enrichment: complete prospect lists, CRM records, and automated sequences without per-record manual checks.

How can I test it on my own contacts?

Sign up on app.blitz-api.ai and get 1,000 free records to enrich a sample of your contacts.

How do I find a work email from a LinkedIn profile?

Send the profile URL to POST /v2/enrichment/email as person_linkedin_url. The response returns the verified work email in email, and every work address found for the jobs on the profile in all_emails. No name or company matching is needed on your side.

Data shouldn't be
the problem

Grab. Connect. Build.