Reverse Email Lookup
Turn an email address (or phone number) into the person behind it — LinkedIn profile, name, and full enriched identity.
Reverse Email Lookup
Normal enrichment goes person → contact info. Reverse lookup runs the other way: give Fiber an email address and get back the person's LinkedIn profile and personal details — name, headline, current company, location, and the full enriched profile shape.
There's also a reverse phone lookup: given a phone number, find the person (or company) it belongs to. Mobile and home phones typically resolve to people, while front-desk or business lines may resolve to companies.
How it works
Reverse Email Lookup stands on years of enrichment at scale: one of the largest verified email↔identity maps in the industry, paired with proprietary matching that resolves emails to real people inside Fiber's own data. That combination is what delivers the numbers below.
Performance you can expect:
- 70%+ hit rate on work emails — a large majority of work emails resolve to a profile.
- High throughput — optimized for bulk jobs at up to ~3,000 requests/minute for high-volume customers.
Variants
| Variant | Operation | When to use |
|---|---|---|
| Single | reverseEmailLookup | One email, full personal details |
| Bulk | reverseEmailLookupBulk | A list of emails in one async job |
| Lite (high-volume) | liteReverseEmailLookup | Maximum throughput at lower cost; returns the essential profile match |
| Reverse phone (single) | reversePhoneLookup | A phone number → person or company |
Why teams use it
- Signup-list enrichment. Turn product signups (you already have their emails) into full profiles with firmographics and titles for segmentation.
- CRM backfill. Resolve the half of your CRM that only has an email into LinkedIn URLs and enriched records.
- Lead routing & scoring. Resolve inbound emails to profiles in real time so routing rules and scoring models can use company size, industry, seniority.
Using it effectively
Have more than just an email? If you also know the person's name, company, or anything else, use the Kitchen Sink profile resolver instead — it accepts all available signals and produces better matches. Same logic applies to phone numbers: with extra context, prefer Kitchen Sink.
- Pick lite for scale, single for depth. Lite trades a little match depth for speed and cost — ideal when processing tens of thousands of emails and a slightly lower hit rate is acceptable. Use the standard variant when every match matters more than marginal cost.
- Pace your requests evenly. To avoid HTTP 429s, space requests out (e.g., run at roughly 1/60th of the per-minute limit per second) instead of bursting everything at once.
- Work emails beat personal emails. Coverage is strongest for professional addresses; expect more misses on disposable or very old personal domains.
- Charge model. Lookups only charge when they find something — misses don't cost credits — so it's cheap to push through a whole backlog and keep whatever resolves.