Fiber AI email-to-person endpoint example

Fiber’s email-to-person endpoint turns any email address—work or personal—into a full, verified B2B identity you can use in outbound, recruiting, or AI agent workflows. Instead of guessing who “unknown@gmail.com” is, you get a structured profile that can be searched, enriched, and activated programmatically.

The Quick Overview

• What It Is: An API endpoint that takes an email and returns a rich person profile (name, role, company, LinkedIn context) with bounce-checked contact data.
• Who It Is For: Growth, outbound, and recruiting teams, plus AI agents, that need to resolve anonymous signups, enrich old CRM records, or de-anonymize high-intent traffic.
• Core Problem Solved: You no longer lose pipeline or waste spend because you can’t map emails to real people or you blast unverified addresses that tank deliverability.

How It Works

The email-to-person endpoint is Fiber AI’s “identity backbone.” You send an email (work or personal) to a single endpoint. Fiber runs it through 100+ live and static sources, applies waterfall validation and four layers of bounce detection, and returns a clean, normalized profile you can plug into your workflows.

1. Submit the email:
   Your system (or AI agent) calls email-to-person/single with an email like john@company.com or jane.doe@gmail.com.

2. Identity + enrichment:
   Fiber resolves the person behind that email and enriches them with core attributes—name, headline, location, current company, role, and more—plus verified contact paths.

3. Validation + response:
   Before you ever send an email, Fiber runs waterfall validation and bounce checks. You only pay credits when data is actually found, and you get a JSON response ready to drop into your CRM, MAP, or agent.

Basic curl example

curl https://api.fiber.ai/v1/email-to-person/single \
  --request POST \
  --header 'Content-Type: application/json' \
  --data '{
    "apiKey": "YOUR_API_KEY",
    "email": "john@company.com"
  }'

Example JSON response (simplified)

{
  "data": [
    {
      "first_name": "John",
      "last_name": "Smith",
      "name": "John Smith",
      "headline": "Software Engineer at Tech Corp",
      "locality": "San Francisco, CA",
      "profile_pic": "https://media.example.com/john.jpg",
      "current_company": {
        "name": "Tech Corp",
        "domain": "techcorp.com",
        "linkedin_url": "https://www.linkedin.com/company/techcorp"
      },
      "linkedin_url": "https://www.linkedin.com/in/john-smith-se/",
      "emails": [
        {
          "email": "john@techcorp.com",
          "type": "work",
          "validated": true,
          "bounce_risk": "low"
        },
        {
          "email": "johnsmith@gmail.com",
          "type": "personal",
          "validated": true,
          "bounce_risk": "low"
        }
      ],
      "phones": [
        {
          "number": "+1-415-555-0123",
          "type": "mobile",
          "validated": true
        }
      ]
    }
  ]
}

You can expect additional fields (work history, education, social URLs, etc.) depending on the profile.

Features & Benefits Breakdown

Core Feature	What It Does	Primary Benefit
Email-to-person resolution	Turns any email (work or personal) into a structured person profile.	De-anonymize signups and contacts instantly.
Waterfall validation + bounces	Runs each email through layered verification and bounce detection.	Protects sender reputation with <1% bounce rates and 0% guarantee.
Programmatic enrichment	Returns machine-readable JSON for agents, CRMs, and workflows.	Drop directly into outbound, scoring, or routing logic.

Ideal Use Cases

• Best for inbound signup resolution: Because it maps “personal” emails (e.g., jane.doe@gmail.com) to a real person and likely employer, so your SDRs don’t ignore high-intent signups that look non-corporate.
• Best for reviving old CRM data: Because it can take a stale email list, re-verify addresses, attach updated work history and company info, and let you safely re-activate dormant contacts.

Example: De-anonymizing a personal email signup

You see a signup from michael.lee@gmail.com with no company field. Call Fiber:

curl https://api.fiber.ai/v1/email-to-person/single \
  --request POST \
  --header 'Content-Type: application/json' \
  --data '{
    "apiKey": "YOUR_API_KEY",
    "email": "michael.lee@gmail.com"
  }'

You might get:

{
  "data": [
    {
      "name": "Michael Lee",
      "headline": "Director of RevOps at FintechCo",
      "locality": "New York, NY",
      "current_company": {
        "name": "FintechCo",
        "domain": "fintechco.com",
        "employee_count": 230
      },
      "emails": [
        {
          "email": "michael.lee@fintechco.com",
          "type": "work",
          "validated": true,
          "bounce_risk": "low"
        }
      ]
    }
  ]
}

Now you know this is a Director-level RevOps lead at a 200–300 person fintech in NYC—not a random Gmail user.

Example: Cleaning a legacy email list

You have 50k emails in your CRM, but no idea which ones are still valid or where people work today. You run them through a batched version of email-to-person (or orchestrate multiple single calls) to:

• Re-verify email deliverability.
• Attach current title and employer.
• Drop contacts with high bounce risk from your sequences.

This is how teams hit <1% bounce rates and keep sender reputation intact.

Limitations & Considerations

• Not every email resolves perfectly: Some addresses (very new, obscure, or privacy-conscious users) may return partial or no profiles. Fiber’s pricing model helps here—you only pay for successful data found.
• You still need good workflows: Email-to-person is the identity layer. You’ll get the most value when it’s wired into lead scoring, routing, suppression logic, and your AI agents’ decision-making.

Pricing & Plans

Fiber AI uses a credit-based model where you only pay for successful calls (data found). That’s aligned with the email-to-person use case: if we can’t resolve or enrich the email, you’re not burning budget.

Typical packaging looks like:

• Growth API Plan: Best for GTM and recruiting teams needing a few hundred to a few thousand email-to-person calls per day wired into CRMs, warehouses, or no-code tools.
• Enterprise / Custom Plan: Best for teams running millions of lookups, AI agents that call Fiber in real time, or those needing custom endpoints, higher rate limits, and a dedicated Slack channel.

For exact pricing, volume discounts, and bundle options (email-to-person plus people search, company search, LinkedIn live fetch), we usually scope this on a call.

Frequently Asked Questions

Can I use email-to-person on personal emails like Gmail or Outlook?

Short Answer: Yes, Fiber can often resolve personal emails to a work identity and profile.

Details:
Many of your highest-intent signups will never use their @company.com address. With email-to-person, you still get:

• Name and headline (e.g., “VP Engineering at XYZ”).
• Likely current company and role.
• Verified work email when available.

That’s how teams stop under-valuing personal email signups and start routing them as real opportunities.

---

How does Fiber’s email-to-person endpoint protect my deliverability?

Short Answer: Every email goes through waterfall validation and multiple bounce checks before you send.

Details:
Fiber doesn’t just “find an email and ship it.” For each contact, email-to-person is backed by:

• Waterfall validation: Multiple verification providers in sequence, plus Fiber’s own checks.
• Four layers of bounce detection: To filter out risky addresses before they hit your sequences.
• 0% Bounce Guarantee language: Fiber is built to keep bounces near zero on the data we return.

Practically, this means your outbound or lifecycle emails are hitting verified inboxes, not burning your domain reputation.

Summary

Fiber AI’s email-to-person endpoint is the fastest path from “mystery email” to “qualified, verified buyer persona.” It resolves both work and personal emails into structured profiles, validates each contact through waterfalls and bounce detection, and returns machine-readable data your GTM stack and AI agents can act on immediately. Teams use it to de-anonymize inbound, revive old CRMs, and protect deliverability while scaling outbound.

Next Step

Get Started