search_contact_by_email

search_contact_by_email is a reverse email lookup: it turns a business email address into the contact profile behind it — name, LinkedIn profile, current title, employer, and location.

This is a paid tool — matches bill, misses don’t — and it enforces the same two-phase consent flow as contact_data_enrichment above 10 addresses.

Business domains only

Personal mailbox addresses (Gmail, iCloud, Yahoo, Outlook, Proton and other consumer providers) are rejected before the lookup runs. They are never resolved to a person and never charged for, and come back under skipped with the reason. Resolving someone’s private mailbox to a named, contactable profile is a third party’s interest, not your tenant’s, so the tool does not do it.

When to use it

• A list of webinar registrants, newsletter subscribers, or form fills where all you have is a work email address.
• CRM rows with a company email and nothing else.

Inputs

Parameter	Type	Required	Description
emails	string[]	Yes	Addresses to look up. Empty list for phase 1 and when resuming.
total_count	integer	No	Total address count. Required for the consent phase (>10).
confirmation_token	string	No	Server-issued token from phase 1. Required on every phase-2 call when >10.
continuation_token	string	No	Resume handle from a still_running response — pass with emails=[].
target_tenant_id	string	No	Super tenants only.

The consent flow

10 addresses or fewer — pass emails directly, no token needed.

More than 10:

1. Call with emails=[] and total_count=N → confirmation_required with a user_facing_message (show it verbatim) and a confirmation_token. Stop and wait for an explicit yes.
2. Send the addresses with the confirmation_token and total_count on every call.

The threshold counts the business addresses only — a batch of 11 where ten are Gmail is one lookup and needs no consent step.

Returns

• Phase 1: confirmation_required with the charge details and token.
• Phase 2 / small batch: matched_count, unmatched_count, results, and skipped when any address was out of scope.

Each matched record carries email, full_name, first_name, last_name, linkedin_url, current_title, current_company, current_company_domain, current_company_industry, current_company_headcount, and location_country / location_city / location_region.