POST /api/v1/contacts/enrich
{
"first_name": "Taylor",
"last_name": "Kim",
"company_domain": "example.com",
"include_email": true,
"include_phone": true,
"include_profile": false
}Waterfall contact enrichment for marketing operations
Enrich known leads with work emails and business phones—before you route them.
When a lead, event attendee or account contact is already in your workflow, TargetWise routes the contact fields you request through a network spanning 15+ specialist sources and returns one normalized result for your marketing logic.
One known professional per request. No audience building, CSV bulk jobs or outreach automation.
Inbound lead request
IllustrativeRequestOne known professionalName + company domain · email + phone requested
TargetWise routeOne entity per lookup
Identity inputAccepted
Work emailReturned
—Business phoneUnresolved
15+ sourcesavailable to contact-field routing
Email + phonerequest either field or both
One personper on-demand request
REST + MCPfor software and supported AI hosts
Contract-shaped example
See the exact branch your workflow receives.
This example is illustrative, but its request and response fields match the current contact-enrichment contract.
{
"object": "enrichment_result",
"operation": "contact_enrichment",
"request_id": "req_example",
"status": "partial",
"data": {
"full_name": "Taylor Kim",
"company_name": "Example",
"work_email": "taylor.kim@example.com"
},
"unresolved_fields": ["business_phone"],
"grounding": {
"retrieved_at": "2026-08-31T12:00:00.000Z",
"source_provenance": "not_available"
}
}Work email returned while business phone remained unresolved, so the result is partial. The marketing workflow can use the returned email and keep the phone field marked as unresolved.
Where it fits
Complete a record your marketing system already knows.
Place TargetWise after capture or account approval and before a step that genuinely needs more business contact data.
The contact operation accepts either a LinkedIn profile URL or name-and-company context for one professional. The request can select work email, business phone or both.
Company enrichment is a separate operation for organization-level context. TargetWise does not choose accounts, create audiences, score leads or send messages.
Marketing workflow moments
Use enrichment where a real record is waiting.
Keep retrieval, field acceptance and activation as separate steps.
Complete a captured lead
Request a missing contact field after the form or product event supplies enough identity context.
Prepare a known attendee record
Add available business contact data to an attendee already captured through an event registration.
Research an account contact
Enrich a professional already associated with a selected account without generating the buying committee.
Branch on explicit result states
Handle matched, partial and not_found as business outcomes; keep HTTP and transport errors on separate branches.
Trigger from marketing workflow code
Call the contact endpoint when one captured record reaches the defined enrichment step.
Support a marketing assistant
Allow retrieval for one known record while the host separately controls calls, writes and messages.
Reference workflow
Capture, enrich, evaluate and route.
Every branch stays connected to the original record and purpose.
Receive the record
A form, event or account workflow supplies the professional and company context.
Request the field
Choose work email, business phone or both through the contact endpoint.
Evaluate each outcome
Apply identity and field rules to returned and unresolved values.
Continue under policy
Route or review the lead using the fields available in the result.
Evaluation
Measure accepted completion—not a raw match-rate headline.
Track whether the intended professional was matched and whether the specific field needed by the workflow was returned and accepted. Report work email and business phone separately.
Segment results by market, input type and workflow stage. Include difficult identities and expected no-matches; the Free plan validates early fit, not production coverage.
- Identity-confirmed result
- Accepted work-email completion
- Accepted business-phone completion
- Partial and no-match branch completion
- Manual research time avoided
Marketing scorecard
Questions for every test record
1Was the intended professional matched?
2Was the required field returned?
3Did it pass the customer rule?
4Did the missing-data branch stop safely?
What TargetWise does not replace
Enrichment supplies data; your stack keeps the decisions.
Keep these responsibilities in the marketing systems and policies that already own them.
Account and contact selection
TargetWise does not decide which companies, people or buying committees should enter a campaign.
Deliverability and reachability checks
A returned value does not prove mailbox deliverability, phone reachability or a number type.
Scoring, routing and outreach
Customer automation decides whether to score, write, route, message or stop.
Frequently asked questions
What to know before you build.
Use TargetWise for record completion. Connect the results to audience selection, lead routing and campaign workflows.
Initial fit test
Test the marketing records your workflow actually handles.
Use the Free plan to validate identifiers, field outcomes and every application branch. Plan a larger representative sample before estimating production coverage.