From inbox to identity

Turn any work email into a full professional profile

Send a verified work email and retrieve the person behind it: current role, company, seniority, location, and LinkedIn URL, in one request.

Trusted by the best GTM teams

Built for instant identification

Every email in your funnel is a person waiting to be identified. Resolve them before your first reply.

Identify instantly

One email in, one full profile out: name, headline, current role, company, seniority, location, and LinkedIn URL.

Qualify signups

Enrich product-led signups the moment they land, so scoring, routing, and personalization run on real data instead of a bare address.

Route inbound

Prioritize demo requests and inbound leads by seniority and company before a rep ever opens the record.

Sync clean records

Write the resolved LinkedIn URL and firmographics back to your CRM to dedupe contacts and keep records complete.

From address to identity

One endpoint, POST /v2/enrichment/email-to-person, resolves an email into the professional behind it.

  1. Send the email

    Pass a single verified work email address. No other fields, no pre-formatting, no matching keys to build.

  2. Match the person

    Get a found flag plus the full person object: current role, company, location, work history, education, and LinkedIn URL.

  3. Activate the profile

    Score, route, and personalize with the resolved identity, or chain the LinkedIn URL into company and phone enrichment.

IDENTITY RESOLUTION

Every identifier resolves against the same graph: one key in, the full record out.

API Docs
ONE API LAYER

Frequently asked questions

What does the lookup return for an email?

A found flag and, when matched, the full person object: name, headline, current role and company, seniority, location, LinkedIn URL, work history, education, and skills.

Which emails work best?

Verified work email addresses give the strongest match rates, since they map directly to a professional identity. It's the ideal companion for product signups, demo requests, and event lists.

What happens when no match is found?

The response returns found: false and you can fall back to other identity keys (domain, name, or LinkedIn URL) using Profile Enrichment or Waterfall ICP.

Data shouldn't be
the problem

Grab. Connect. Build.