Can a business email return experience, education and skills?

Yes. Enable extended profile context to request the person’s location, professional headline, work experience, education and skills where available. Profile access depends on your account and the underlying record.

What email address can I submit?

Use one business email as the starting identifier. The current API or MCP reference lists the accepted request format.

What can TargetWise return from a business email?

The lookup can return available professional identity, role, employer and company context. Supported fields can vary by email and route.

Does reverse email lookup verify mailbox deliverability?

No. This product resolves professional identity and company context. It is not SMTP verification, deliverability testing or a guarantee that an address is reachable.

What happens when the email cannot be resolved?

TargetWise returns an explicit not_found or unresolved outcome instead of filling the record with a guess. Keep that branch separate from matched and partial results in your application.

Can an AI agent use reverse email lookup?

Yes. Through MCP, an agent can request available identity and company context. The surrounding application controls tool access, call limits and downstream actions.

How is reverse email lookup different from contact enrichment?

Reverse email lookup begins with an email and resolves identity and company context. Contact enrichment begins with a known person and searches for a requested work email, business phone number or both.

Is this a bulk email lookup product?

No. TargetWise is designed for on-demand enrichment of one business email per request, inside a product, CRM workflow, automation or agent tool.

How should my workflow handle a partial match?

Treat each returned field independently and keep missing fields unresolved. Your workflow can continue with the accepted fields, route the record for review or stop the action based on its own rules.

Can I test my own inputs before integrating?

A bounded evaluation is available subject to workspace limits. Reverse-email paid production pricing and access are not currently published, so adding balance does not enable the operation; discuss production requirements with TargetWise before depending on it.

✦ B2B reverse email lookup

Reverse email lookup API for B2B person and company context.

Start with one permitted business email. TargetWise returns available professional identity, role, employer and optional contact context through a normalized REST API or MCP response—not mailbox verification.

Run an evaluation Inspect the API contract

Bounded evaluation; production access is scoped separately.

Reverse email lookup

Example only

Business emailalex@northstar.example

Professional identityAlex ReedMatched to company context

Matched

Role contextAvailable

CompanyNorthstar Systems

Company domainnorthstar.example

ResponseNormalized

Business email inone starting identifier

Person + companyavailable professional context

Explicit outcomematched or unresolved

REST + MCPsoftware and agent delivery

Plan the contract before you call the API

Choose optional data. Inspect matched, partial and unresolved branches.

This browser-only explorer makes no lookup and sends no email address anywhere. Its fictional response states explain the current request contract; they are not TargetWise coverage, accuracy or latency measurements.

Business-email requestOne email is the only required identifier.

Fictional business email

Local preview only. Use an address you are permitted to process in a real evaluation.

Optional response groupsBusiness phoneinclude_phone defaults to true in the API. This preview sends an explicit choice.Extended profileRequest available location, headline, work history, education and skills. Account permission may be required.

POST/api/v1/reverse-email

{
  "email": "alex@northstar.example",
  "include_phone": false,
  "include_profile": false
}

Authentication uses a server-side bearer key. Do not place an API key in browser code or logs.

Result-state walkthroughChoose the branch your workflow needs to handle.

Some requested context is returned and every missing field stays explicitly unresolved.

Field groups in this fictional stateCounts describe only the example shown below.

ReturnedUnresolvedNot requested

Identity2 fields requested

1/2

Company2 fields requested

1/2

Optional phonenot requested

off

Extended profilenot requested

off

Illustrative responsepartial

{
  "status": "partial",
  "request_id": "req_example_01",
  "data": {
    "full_name": "Alex Reed",
    "linkedin_url": null,
    "company_name": "Northstar Systems",
    "company_website": null
  },
  "unresolved_fields": [
    "linkedin_url",
    "company_website"
  ]
}

PurposeIdentity and company context—not mailbox ownership or SMTP verification

InputOne permitted business email per request; no public bulk endpoint

Optional dataMake phone and extended profile choices explicit before processing

OutcomesBranch on matched, partial and not_found; never fill gaps with guesses

PrivacyDefine lawful purpose, field access, retention and deletion before storing results

Commercial fitBounded evaluation is available; paid production access is not currently published

Review the exact API schema Run a bounded evaluation Discuss production requirements

Reverse email lookup, clearly explained

Start with the email. Resolve the business identity behind it.

Reverse email lookup uses an email address as the starting identifier for a professional and company match.

Instead of searching for a work email from a known person, this workflow runs in the opposite direction. TargetWise searches for professional and company context associated with the supplied business email, then returns the available fields.

Keep the purpose narrower than the data available.Choose phone and extended-profile fields only when the workflow needs them. Define the lawful purpose, field access, retention and deletion rules before storing a result.Review the privacy policy

A different starting point

Choose the workflow that matches the identifier you have.

Waterfall Enrichment API

Known person → email and phone

Start with a person or professional profile and request a work email, business phone number or both.

Explore Waterfall Enrichment API

vs.

Reverse email lookup

Known email → person + company

Start with a business email and request the available professional identity and company context.

See the reverse workflow

Available outputs

One response with professional and company context.

Coverage varies by email and source. Missing context stays unresolved instead of being replaced with a guess.

Professional contextIdentityWhere available

Work contextRole or titleWhere available

Company contextName + domainWhere available

Lookup resultStructured outcomeUse the documented response

Person enrichment

Location, experience and professional background.

Build a fuller picture of a known professional. Start with a LinkedIn profile, a name and company, or a business email, and request the available profile alongside the contact details you need.

Explore the person enrichment API

Fields depend on the record and account access. Contact us for production profile access.

Location: The professional’s available city, region and country.
Professional headline: A short description of the person’s role and professional focus.
Work experience: Employers, roles, start and end dates, and current-role status where reported.
Education: Institutions, courses or qualifications, and dates where available.
Skills: Reported professional skills, returned as a list.

How the lookup works

One business email becomes one evidence-aware result.

TargetWise checks the identifier format, retrieves available business context and maps it into a stable response without exposing supplier credentials or supplier-specific fields.

Start with one business email
Retrieve identity and employer context
Keep professional and company fields distinct
Preserve unresolved fields without guessing

Illustrative example — not an API schemaalex@northstar.example

Identifier format acceptedOne business emailReady

Identity contextProfessional fields returned where availableMatched

Missing contextPreserved as unresolvedExplicit

ResponseOne normalized B2B record

Three clear steps

Email in. Dedicated retrieval route. Business context out.

Submit a business email

Send one business email through the REST API or MCP.

Retrieve available context

TargetWise uses the reverse-email route for identity, role, employer and optional phone context.

Use the result

Handle matched data and unresolved fields in separate workflow branches.

Reverse email lookup for AI agents

Let an agent request business context without guessing.

When an agent encounters a business email, MCP can connect the reverse-lookup capability to a supported host. The host controls tool permissions and the workflow controls downstream action.

Host-owned tool permissions
Per-workspace request limits
Explicit unresolved branch

Agent inputWho is behind this business email?

TargetWise toolReverse email lookup

Grounded contextMatched person + company fields

Where it fits

On-demand identity context for real business workflows.

TargetWise resolves the available context; your product or process decides what happens next.

Inbound signups

Understand the business user behind an email.

Add company context before routing, personalization or account assignment.

Account matching

Connect an email to the relevant company.

Use accepted company name and domain fields in your account workflow.

Embedded workflows

Resolve context inside your product.

Trigger an individual lookup when a customer action or record requires it.

AI-agent tools

Ground an agent task in business identity data.

Expose only the reverse-lookup capability and fields the workflow is allowed to use.

Delivery

Use reverse email lookup in software or agent workflows.

REST API

Resolve emails inside your product.

POST one business email to the TargetWise v1 reverse-email endpoint and handle the normalized response.

Read the reverse-email API docs

MCP

Connect lookup to an AI workflow.

Call targetwise_reverse_email_lookup from an authorized host with tool-level access settings.

Read the TargetWise MCP docs

Technical evaluation

Validate reverse lookup on permitted business emails.

Use the bounded evaluation on representative inputs, then confirm production access and outcome terms before integrating. Paid reverse-email pricing is not currently published.

Verify the accepted request shape
Test REST or MCP response handling
Review matched, partial and not_found branches

Workspace-limitedEvaluationDiscuss production access

Reverse email lookup FAQ

Questions before you integrate.

Clear answers about accepted inputs, professional and company fields, partial matches, REST and MCP delivery, evaluation and credit behavior.

Comparing providers? Read the B2B reverse email lookup evaluation guide

Ready to evaluate?

Test the response contract on business emails you are permitted to process.

Run an evaluation Discuss production access